Article View: comp.sys.next.programmer
Article #1251Can C preprocessor handle #include "fooa" "foob"
From: Ernest Prabhakar
Date: Thu, 20 Aug 1992 23:53
Date: Thu, 20 Aug 1992 23:53
20 lines
1438 bytes
1438 bytes
There is a funky trick which works under the 3.0 NeXT preprocessor, but not under GNU 2.1 or 2.2. It is: #include "string1" "string2" which resolves to: #inclue "string1string2" Which is then referenced for the include file. Now, I'm not savvy enough to understand exactly what the ANSI C preprocessor is supposed to guarantee. Does stringification take place before includes? Then GNU is broken. Is it the other way around? Then NeXT's preprocessor supplies (and thus NeXT include files rely upon) non-standard behavior. Could someone perhaps shed some light on this for me? - Ernie P. -- Ernest N. Prabhakar Caltech High Energy Physics Member, League for Programming Freedom (league@prep.ai.mit.edu) CaJUN President NeXTMail:ernest@pundit.cithep.caltech.edu "...and ourselves, your servants for Jesus sake." - II Cor 4:5b #import <std/disclaimer.h>
Technical Details
Message-ID:
<1992Aug20.235325.18290@cco.caltech.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!nntp-server.caltech.edu!newsShow Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.programmer Path: arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!nntp-server.caltech.edu!news From: ernest@pundit.cithep.caltech.edu (Ernest Prabhakar) Subject: Can C preprocessor handle #include "fooa" "foob" Message-ID: <1992Aug20.235325.18290@cco.caltech.edu> Sender: news@cco.caltech.edu Nntp-Posting-Host: pundit.cithep.caltech.edu Reply-To: ernest@pundit.cithep.caltech.edu (Ernest Prabhakar) Organization: California Institute of Technology, Pasadena Date: Thu, 20 Aug 1992 23:53:25 GMT Lines: 20