Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pasteur!ucbvax!decwrl!sun!pitstop!sundc!seismo!uunet!ccicpg!turnkey!sandy
From: sandy@turnkey.TCC.COM (Sanford 'Sandy' Zelkovitz)
Newsgroups: comp.lang.c
Subject: Re: uustatus - realtime uustat for HDB uucp (w/findpath)
Summary: Look at the code!
Keywords: NULL zero 0 C Microsoft
Message-ID: <5473@turnkey.TCC.COM>
Date: 31 Jan 89 00:17:27 GMT
References: <1167@unisec.usi.com> <5312@turnkey.TCC.COM> <1989Jan30.013936.11995@gpu.utcs.toronto.edu>
Organization: Turnkey Computer Consultants, Costa Mesa, Ca.
Lines: 22

In article <1989Jan30.013936.11995@gpu.utcs.toronto.edu>, woods@gpu.utcs.toronto.edu (Greg Woods) writes:
> In article <5312@turnkey.TCC.COM> sandy@turnkey.TCC.COM (Sanford 'Sandy' Zelkovitz) writes:
> 
> The reason your compiler gives you a warning message, is because NULL
> has been erroneously defined as something other than just plain zero.  I
> most definitely will not go into the reasons why, but it should suffice
> to say that "#define NULL 0" is the only correct definition.  [Anyone
> who would like some evidence, please send me some mail.]
> 
	[rest left out intensionally]

If you look at the code that was modified before writing a manual on stdio.h,
you would have noticed that it was made compatible with both Unix and Xenix!
Nobody is arguing with you that SCO/Microsoft incorrectly defined NULL
as (char *)0; however, programs which really mean zero and not a NULL pointer
can easily be modified to 0 and therefore be compatible with both worlds!

-- 
Sanford <sandy> Zelkovitz               XBBS   714-898-8634
UUCP: ....att!hermix!alphacm!sandy      ....trwrb!ucla-an!alphacm!sandy
      ....uunet!turnkey!alphacm!sandy   ....ucbvax!ucivax!icnvax!alphacm!sandy
DATA: 714-898-8634                      VOICE: 714-894-7898