Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!crdgw1!crdos1!davidsen
From: davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr)
Newsgroups: comp.lang.c
Subject: Re: Concatenating with a compile-time definition in "ANSI" CPP
Message-ID: <1231@crdos1.crd.ge.COM>
Date: 18 Oct 89 18:04:34 GMT
References: <470004@gore.com> <29351@watmath.waterloo.edu> <17975@pasteur.Berkeley.EDU>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: GE Corp R&D Center
Lines: 20

In article <17975@pasteur.Berkeley.EDU>, hunt@ernie.Berkeley.EDU (Jim Hunt) writes:

|  Question, what do ansi compilers do with that?  They don't HAVE
|  to have a pre-processor, but who doesn't, and if there is a PP,
|  which eliminates /*comments*/, what token does it put in to
|  identify where comments were?  

  Comments are replace with one blank. I think consecutive whitespace is
stripped, too, but my standard isn't handy.

#define foo(a,b) a/**/b

doesn't work for concat in an ANSI compiler for just this reason, but
your suggestion that it works on pcc is correct (in most cases). A
conditional definition of the macro will probably help.
-- 
bill davidsen	(davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen)
"The world is filled with fools. They blindly follow their so-called
'reason' in the face of the church and common sense. Any fool can see
that the world is flat!" - anon