> From: Aleksander Morgado <[email protected]> > Date: Thu, 25 Mar 2010 11:17:56 +0100 > > Sorry for the long email :-) > > > Is there any good reason to generate the PDF_DEBUG_* and PDF_ASSERT_* > > macros in the public pdf.h header? > > > > Yes. Currently these macros are available to the library user and are > > documented in the reference manual. The rationale is to ease the > > debugging of problems while using the library. > > > > Humm.. Not really sure if that's so useful. Whenever the library is > distributed out there, it won't be compiled with the configure options > which enable those macros, so PDF_DEBUG_* macros for example will do > nothing. We don't even use them in our unit tests, I believe. >
Hi Aleks, BTW, shouldn't we get used to write code with PDF_DEBUG ? The day we start with beta testing, we're gonna be writing tons of them to find a bug. We could start now instead. :-) cheers, -gerel
