#ifdef tool?

David Korn dkorn@pixelpower.com
Wed Jul 25 06:23:00 GMT 2001

>-----Original Message-----
>From: Joel Coltoff [ mailto:joel@wmi.com ]
>Sent: 25 July 2001 13:35

>On Tue, 24 Jul 2001, Michael Dorin wrote:
>> Anybody know of a tool that could strip unused ifdefs right 
>from your code?
>As has been suggested you could use gcc -E. [snip]

  The preprocessor isn't as useful as all that, it will also process all
the ifdefs you want left in, replace all your carefully #defined macros
with the obscure magic numbers you invented them to replace, bodily 
insert the contents of all the header files at the site of the #include,
scatter the whole thing with #line directives that would make it hard to
figure out the actual line in the preprocessed file where a reported error
was actually placed, etc. etc etc!  Basically it's no use for this kind
of job. 

  Fortunately Pat has come up with a better answer for you while I was busy
typing this reply!

"Computer games don't affect kids; I mean if Pac-Man affected us as kids,
we'd all be running around in darkened rooms, munching magic pills and
listening to repetitive electronic music."
    - Kristian Wilson, Nintendo, Inc, 1989.

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.


Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

More information about the crossgcc mailing list