Re: [Xen-devel] debugging frustration

[Mark Williamson <Mark.Williamson@xxxxxxxxxxxx>]

> Also, is there a reason that not having DEBUG in turns dprintf into do
> {} while(0) instead of just turning into ""

It makes the macro behave more like a proper statement.  e.g.  If we try to 
do:

if ( 1 == 2 debug_print("foo!") )
{

}

It won't compile, even if debugging is switched off.  If we just did "#define 
debug_print(...)" then this would compile and we'd only notice the error when 
debugging was switched on.

That's a quite contrived example but basically it keeps the developers 
honest ;-)

Cheers,
Mark


-------------------------------------------------------
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel