Xref: utzoo comp.unix.questions:13135 comp.std.c:1111
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!usc!csun!csuna!abcscnge
From: abcscnge@csuna.csun.edu (Scott "The Pseudo-Hacker" Neugroschl)
Newsgroups: comp.unix.questions,comp.std.c
Subject: Re: How can I find out cc or cpp symbols?
Keywords: cpp, cc, macros
Message-ID: <1938@csuna.csun.edu>
Date: 29 Apr 89 20:27:14 GMT
References: <1954@trantor.harris-atd.com>
Reply-To: abcscnge@csuna.csun.edu (Scott Neugroschl)
Distribution: na
Organization: CSU Northridge
Lines: 35

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 am also interested in finding out about what are the "manifest defines" of
a CC implementation.  I write code for 5 different platforms, and would
like it to be semi-portable (e.g. 

#if vax || M_8086
	read(fd,&data,nbytes);
	swab(&data,&data,nbytes);	/* swap for byte swapped machine */
#endif

	System				Manifest Defines
	------------------		---------------------
	SCO Xenix SysV/286		(M_8086 or some such)
	AT&T 3B15			(don't know)
	VAX/Ultrix			(vax)
	Motorola System V/68		(m68k????)
	ZEUS (Zilog Unix Sys III)	(z8000)

Each of these has their own manifest defines, but they are not well
documented (if at all).  IMHO, the man page for cc(1) or cpp(1) should
specify what that particular preprocessor implementation pre-defines.
I like the suggestion for #dump "file".  Did anyone suggest this to
the X3J11 committee?




-- 
Scott "The Pseudo-Hacker" Neugroschl
UUCP:  ...!sm.unisys.com!csun!csuna.csun.edu!abcscnge
-- unless explicitly stated above, this article not for use by rec.humor.funny
-- Disclaimers?  We don't need no stinking disclaimers!!!