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

[dickey]

> 
> >  
> > Strange: 
> > Turning trace off at compile-time transforms all instances of 
> > CTRACE(...) 
> >   to  
> > if (0) fprintf(...) 
> >  
> > But the string literals in the CTRACE calls still wind up in the binaries  
> > for me.  (Tried this with both Sun's cc and gcc).  This is like 30k worth  
> > of string literal over the whole lynx source.  It's very disturbing. 
> >  
> Can you change things to say 
>  
> #if 0 
> fprintf(...) 

not exactly.  we went over this a few months ago.  as KW notes, turning
on optimization would probably accomplish the desired effect.  otherwise,
we'll have to rephrase all of the CTRACE macros.  (I'd rather concentrate
on finishing off the dangling stuff for 2.8.2 than change 1400 lines of code)

> instead?  That will get rid of the strings you are trying to get rid of. 
> Of course, IMO once someone has compiled out info like ctrace, it should 
> a) no longer be permitted to be called lynx and b) no longer be acceptable 
> to send problem reports to the list... 
> --  
> Larry W. Virden                 <URL: mailto:address@hidden> 
> <URL: http://www.purl.org/NET/lvirden/> <*> O- "No one is what he seems." 
> Unless explicitly stated to the contrary, nothing in this posting should  
> be construed as representing my employer's opinions. 


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey