Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!apple!vsi1!wyse!mips!prls!pyramid!lll-winken!tekbspa!optilink!cramer
From: cramer@optilink.UUCP (Clayton Cramer)
Newsgroups: comp.lang.c
Subject: Re: use of NULL
Keywords: NULL zero 0 C Microsoft
Message-ID: <965@optilink.UUCP>
Date: 17 Feb 89 00:44:26 GMT
References: <1167@unisec.usi.com. <5312@turnkey.TCC.COM. <9582@smoke.BRL.MIL.
Organization: Optilink Corporation, Petaluma, CA
Lines: 21

In article <9582@smoke.BRL.MIL., gwyn@smoke.BRL.MIL (Doug Gwyn ) writes:
. In article <1340@uwbull.uwbln.UUCP. ckl@uwbln.UUCP (Christoph Kuenkel) writes:
. .Why at all should I ever use NULL anywhere?
. 
. Some think that use of a mnemonic makes the code more intelligible.
. If C were being designed now, I would recommend that "nil" be made
. a language keyword.
. 
. .its much more obvious to write 0,  when I mean zero,  ((char *) 0) when
. .I mean a zero character pointer, etc. etc.
. 
. Using 0 instead of NULL is perfectly acceptable.

No it isn't.  Segmented architecture machines will have problems with
that in large model.  Microsoft defines NULL as 0L, not 0, in large
model.  Pushing an int 0 instead of a long 0 will screw you royally
on the PC.
-- 
Clayton E. Cramer
{pyramid,pixar,tekbspa}!optilink!cramer
Disclaimer?  You must be kidding!  No company would hold opinions like mine!