Many places in the code NULL is used in integer context, where plain 0 should be used. This happens to work because we #define NULL to 0, but is stylistically wrong and can cause problems for people trying to port bits of code to other environments. Fix: Appy following patch. This changes NULL to 0 most places but to '\0' in character context, to be more stylistically correct. How-To-Repeat: #define NULL ((void *)0) in various include files and recompile the world.
>> On Mon, 17 Feb 1997 10:10:59 +0100 (CET), Arne Henrik Juul >> <arnej@imf.unit.no> said: AHJ> Appy following patch. This changes NULL to 0 most places AHJ> but to '\0' in character context, to be more stylistically AHJ> correct. Why is using '\0' more stylistically correct? A pointer is a pointer, and one can always assign 0 to it. One does not assign 0L to an long* either, but simply 0.
State Changed From-To: open->closed committed, thanks!