Xref: utzoo comp.unix.questions:13274 comp.std.c:1152 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!helios.ee.lbl.gov!ucsd!sdcsvax!ucsdhub!hp-sdd!ncr-sd!greg From: greg@ncr-sd.SanDiego.NCR.COM (Greg Noel) Newsgroups: comp.unix.questions,comp.std.c Subject: Re: How can I find out cc or cpp symbols? Keywords: cpp, cc, macros Message-ID: <1339@ncr-sd.SanDiego.NCR.COM> Date: 5 May 89 05:07:01 GMT References: <1954@trantor.harris-atd.com> <10084@smoke.BRL.MIL> Reply-To: Greg.Noel@SanDiego.NCR.COM (Greg Noel) Organization: NCR Corporation, Rancho Bernardo Lines: 13 In article <1954@trantor.harris-atd.com> bbadger@x102c.harris-atd.com (Bernie Badger Jr.) writes: >Is there a way to find out what macros are defined? It's particularly hard >to predict which names will be _predefined_. ... 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. This would give you the option to look at them, provide a replacement (useful for cross-compilations), or generally do anything you wanted with them. Doug, was this ever suggested? -- -- Greg Noel, NCR Rancho Bernardo Greg.Noel@SanDiego.NCR.COM or greg@ncr-sd