Re: lynx-dev [PATCH][dev22] Fix --disable-trace, #includes

[Klaus Weide]

On Fri, 16 Apr 1999, John Bley wrote:

> * Fix --disable-trace, chop more unneeded #includes (John Bley)

Could you explain why --disable-trace needed fixing?  It seems to
me you change doesn't really change anything - you now just test
for NO_LYNX_TRACE directly rather than indirectly (through DEBUG),
or am I missing something?


> Strange:
> Turning trace off at compile-time transforms all instances of
> CTRACE(...)
>   to 
> if (0) fprintf(...)

Are you really compiling with -O[>=2] and without -g?

  ---

For curiosity's sake, how do you determine which #includes are
unneeded?  If you don't test for all possible combinations of 
flags and macros that might control conditional compilation, how
can you be sure an #include is really unnecessary?  Or do you
examine everything by hand?


 Klaus