That could be done. Is there a #if-like statement to only do this if
TRUE=1 and FALSE=0? I wouldn't want TRUE and FALSE being set to
something else, lest bad things happen...
On 5 Apr 2005 at 14:12, Ben wrote:
> I'm making a NEB module that will rely on glib, which defines TRUE and
> FALSE. Nagios also defines TRUE and FALSE in include/common.h.
>
> Predictably, the compiler is unhappy when I try to compile my NEB.
>
> Ethan, do you have a problem wrapping your TRUE/FALSE defines in an
> #ifndef TRUE test?
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real
> users. Discover which products truly live up to the hype. Start
> reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________ Nagios-devel mailing
> list [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>
>
Ethan Galstad,
Nagios Developer
---
Email: [email protected]
Website: http://www.nagios.org
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]