Ian Jackson: > This isn't a matter of preference, I'm afraid. I reverted this > because the change was wrong. NULL is incorrect in that context (a > stdarg function expecting a char*), because it may be #define'd to 0.
NULL will always do, no matter if it is defined to "0" or "(void *) 0". Try this: char *p = 1; // produces compiler warning char *p = 0; // does not -- \\// Peter - http://www.softwolves.pp.se/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
