RE: #ifdef tool?

["Mcgarry, Pat" <Pat dot McGarry at spirentcom dot com>]

Hi there.  I wrote a tool that does this way back when, when I ran into some
interesting ifdef issues with regard to some ancient borland
compilers/preprocessors.

The source is attached, as is a little tiny user's document (I refuse to
call something so trivial a manual!).

It's free, blah, blah, blah.  I don't support it, blah, blah, blah.  Change
it to your heart's content, blah, blah, blah.

Regards,
Pat
---
Patrick McGarry, Director - Broadband Technology
Hekimian Division 
SPIRENT COMMUNICATIONS

"Just when you think you've won the rat race, along come faster rats."

> -----Original Message-----
> From: Michael Dorin [mailto:dorin@puma.chaski.com]
> Sent: Tuesday, July 24, 2001 6:13 PM
> To: crossgcc@sources.redhat.com
> Subject: #ifdef tool?
> 
> 
> 
> 
> Anybody know of a tool that could strip unused ifdefs right 
> from your code?
> 
> Something that could look at your include path and your -D's 
> and generate
> a source file, with comments, with all the undefined code removed?
> 
> Could you do this with the cpp?
> 
> If have a collection of code with lots of #ifdefs.  I would 
> really like
> to be able easily see what I am compiling.  
> 
> Thanks for any advice.
> 
> -Mike 
> 
> 
> 
> ------
> Want more information?  See the CrossGCC FAQ, 
> http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to 
> crossgcc-unsubscribe@sourceware.cygnus.com
>

DE-IFDEF.C

deifdef_v20.doc

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