Shawn Walker <[EMAIL PROTECTED]> wrote:
> To play "Devil's Advocate" here, one could argue that printing "(null)" in
> certain scenarios is desireable. For example, in survey software, knowing the
> difference between a question that was left blank intentionally and a
> question that was not answered at all is important. Even databases often make
> the distinction between a field never having been set, having been set to a
> zero-length string.
If you have a printf that prints "(null)" for NULL pointers, debug statements
are simple.
If printf does not print "(null)" but causes a core dump, it is not possible
to add _simple_ debug statements to your code in many cases...
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
