Xref: utzoo comp.unix.questions:13297 comp.std.c:1156 Path: utzoo!utgpu!watmath!jagardner From: jagardner@watmath.waterloo.edu (Jim Gardner) Newsgroups: comp.unix.questions,comp.std.c Subject: Re: How can I find out cc or cpp symbols? Keywords: cpp, cc, macros Message-ID: <25890@watmath.waterloo.edu> Date: 6 May 89 00:41:47 GMT References: <1954@trantor.harris-atd.com> <10084@smoke.BRL.MIL> <1339@ncr-sd.SanDiego.NCR.COM> <10214@smoke.BRL.MIL> Reply-To: jagardner@watmath.waterloo.edu (Jim Gardner) Organization: U. of Waterloo, Ontario Lines: 18 In article <10214@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes: >In article <1339@ncr-sd.SanDiego.NCR.COM> Greg.Noel@SanDiego.NCR.COM (Greg Noel) writes: >>I've wondered why the ANSI committee didn't simply mandate that there be a >>header file, say , that was implicitly #included, and that contained >>all the machine-specific, system-specific, and vendor-specific names. [...] > >Not in that form, that I recall, but there were a variety of suggestions >for ways to "standardize" such parameterization of the environment. > [...] Also, I don't recall that ANSI has specified that the standard headers even have to be files: they could be built in to the compiler. Even if they are files, they don't have to be text files that you can easily replace. (in effect) could be something that is built by the compiler at compile time, defining things differently depending on how the compiler was invoked, and maybe on things that it can determine about its environment. David Tanguay