Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!texbell!rutgers!elbereth.rutgers.edu!bschwart From: bschwart@elbereth.rutgers.edu (dare-gale skylark) Newsgroups: comp.lang.misc Subject: Re: Header files Message-ID: Date: 6 Oct 89 23:56:21 GMT References: <24955@louie.udel.EDU> <2427@odeon.ahse.cdc.com> Reply-To: bschwart@elbereth.rutgers.edu (dare-gale skylark) Organization: The Society for Anachronistic Poetry Lines: 24 In article <2427@odeon.ahse.cdc.com> bga@odeon.ahse.cdc.com (Bruce Albrecht) writes: >I will probably have several people tell me I'm wrong about this, but >#include is a directive for the c pre-processor and not part of the language >itself. The implication of this, therefore, is that if you have a preprocessor >for your favorite language, you can do this with any language that supports >separately compiled modules. (a) The new C standard will make '#include' part of the language definition. (b) This does not prevent a crafty person from running his sources through cpp (or m4 or another macroprocessor) before compiling. There isn't even a compatibility problem, because you hand out the macroprocessed sources instead of the originals. The authors of sendmail configuration files figured out a long time ago that you can use a macroprocessor outside of C programming. -- Barry Schwartz, Chief SAPsucker bbs@cdspr.rutgers.edu Grad Student, Dept. of Elec. and Comp. Engg. bschwart@elbereth.rutgers.edu Rutgers University College of Engg. bbs@hankel.rutgers.edu Piscataway, NJ 08854 U.S.A. rutgers!cdspr!bbs