Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!pasteur!cory.Berkeley.EDU!johnm
From: johnm@cory.Berkeley.EDU (John D. Mitchell)
Newsgroups: comp.lang.c
Subject: Re: cond. op. on ='s LHS
Message-ID: <11129@pasteur.Berkeley.EDU>
Date: 14 Feb 91 17:11:55 GMT
References: <4155@cernvax.cern.ch> <11073@pasteur.Berkeley.EDU> <15184@smoke.brl.mil> <16754@crdgw1.crd.ge.com>
Sender: news@pasteur.Berkeley.EDU
Reply-To: johnm@cory.Berkeley.EDU
Lines: 13

In article <16754@crdgw1.crd.ge.com> volpe@camelback.crd.ge.com (Christopher R Volpe) writes:
[....]
>Yes, it's ugly, but it's conceivable that someone might have a good
>reason for defining a macro to do this, so that the macro may be used
>in an expression context.              

Aahhh!  But context *is* everything.

One reason to use macros is to hide this sort of cryptic code behind
a nice facade.  Oh well... if only C had...  :-)

----	John D. Mitchell
	johnm@cory.Berkeley.EDU