Path: utzoo!attcan!uunet!ns-mx!iowasp!deimos!ux1.cso.uiuc.edu!brutus.cs.uiuc.edu!zaphod.mps.ohio-state.edu!uwm.edu!ogicse!emory!hubcap!grimlok
From: grimlok@hubcap.clemson.edu (Mike Percy)
Newsgroups: comp.lang.c
Subject: Re: Macro help
Message-ID: <8290@hubcap.clemson.edu>
Date: 9 Mar 90 14:33:05 GMT
References: <34829@ucbvax.BERKELEY.EDU>
Organization: Clemson University, Clemson, SC
Lines: 19

Thanks for the help.  People have told me some things and I have fiddled
more until I realized that, syntacticly (sp?), trying to do something like
x = (y,z)   (assign x the value of z, after also evaluating y) is not allowed
to have y be a statement, only an expression.  Thunk!  I knew better than 
that.  So I'll be trying to figure out a better alternative.     

Again:

#define INPUT() ( {do stuff until(0);} , value I really want)

x = INPUT();

simply doesn't cut it.  Life would be much easier if { statements } had a 
value.

But wait, what if I switched to ADA?? Would I be saved from this horror?
Would life be sweet and would I make 44.3% gains on my IRAs? 

Oh yeah, one preson correctly guessed why I wanted to do what I was trying to do(COBOL is not a fun language to write a standards-checker/formatter for!)