Path: utzoo!attcan!uunet!zephyr.ens.tek.com!uw-beaver!milton!dali.cs.montana.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!usc!rutgers!faatcrl!jprad
From: jprad@faatcrl.UUCP (Jack Radigan)
Newsgroups: comp.sys.amiga.tech
Subject: Re: JRComm, VLT, Handshake
Message-ID: <466@faatcrl.UUCP>
Date: 28 Oct 90 17:42:57 GMT
References: <1990Oct11.235942.2141@caen.engin.umich.edu> <9811@uhccux.uhcc.Hawaii.Edu> <15328@cbmvax.commodore.com> <458@faatcrl.UUCP> <15418@cbmvax.commodore.com>
Distribution: na
Organization: FAA Technical Center, Atlantic City NJ
Lines: 18

andy@cbmvax.commodore.com (Andy Finkel) writes:

>If your program breaks when location 0 is non NULL this means
>you have an unitialized pointer somewhere in your program, and
>are using memory you did not allocate (ie location 0)

  Uh, according to K&R, NULL is a valid assignment for a pointer, so
how is it unitialized?

  Where I got bit is in a pathname building routine that I wrote which
did a strlen() without explicitly checking for NULL first, it now does.

  But, my question is the NULL pointer itself, if NULL is a valid constant,
then the location NULL should contain nothing either, right?

  If I somehow missed something so embarrassingly basic, how come I can't
find it in K&R, which is supposed to be the last word in 'C'?

  -jack-