Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uwm.edu!csd4.csd.uwm.edu!markh
From: markh@csd4.csd.uwm.edu (Mark William Hopkins)
Newsgroups: comp.lang.c
Subject: Re: When do you use "if ( a = b )"?
Message-ID: <10654@uwm.edu>
Date: 1 Apr 91 02:25:12 GMT
References: <15617@smoke.brl.mil> <1991Mar29.195622.321@worf.harvard.edu> <1991Mar30.155003.5775@cc.helsinki.fi>
Sender: news@uwm.edu
Organization: University of Wisconsin - Milwaukee
Lines: 17

In article <1991Mar29.195622.321@worf.harvard.edu>, dmm@cfa.harvard.edu (David Meleedy) writes:
> in fact, if it really gets under your skin, you can take the source code,
> use a good editor to replace every EQU string with ==, and then delete the
> define statement at the top.  In fact you could do that will all but the

In article <1991Mar30.155003.5775@cc.helsinki.fi> wirzenius@cc.helsinki.fi (Lars Wirzenius) writes:
>Of course you could, except if might not work, as EQU might mean
>something else inside a string, for instance. You can't even use the
>preprocessor, since that would expand everything else as well. 

Come on people.  You're discussing a non-essential problem.  If you don't like
somebody else's macros, then just filter it out with the macro preprocessor on
your system.  If you don't have one write it yourself.  Scanners and
preprocessors are trivial to write.

I use my own scanner-based program to alter variable names and macros in other
peoples' source all the time.  It's nothing.