Newsgroups: comp.lang.c
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!news.cs.indiana.edu!nstn.ns.ca!uupsi!grebyn!ckp
From: ckp@grebyn.com (Checkpoint Technologies)
Subject: Re: Zero/nil/NULL/NUL/0/...
Message-ID: <1991Apr20.134839.11052@grebyn.com>
Organization: Grebyn Timesharing
References: <GNAT.91Apr20183721@kauri.kauri.vuw.ac.nz>
Date: Sat, 20 Apr 1991 13:48:39 GMT

In article <GNAT.91Apr20183721@kauri.kauri.vuw.ac.nz> gnat@kauri.vuw.ac.nz (Nathan Torkington) writes:
>I have read the FAQ and this doesn't seem to be what I'm after.  What I
>am looking for is an explicit list of things which 0 (zero decimal, zero
>octal, zero hexadecimal, etc) stand for.  So far I have :
>  -> The number zero (in any base)
>  -> The unused pointer (in some machines)
       Er, really a pointer which is not pointing to anything.  This
       should be true of all machines. (Go read the FAQ again.)
>  -> The null character (ASCII, etc)
>  -> End of file (EOF)
       Actually this is untrue.  0 can be a valid file character, so EOF
       must not be 0; typically EOF is -1.
>  -> Not true (FALSE)

Offhand, I can't think of any other "meanings" C gives to 0.
-- 
First comes the logo: C H E C K P O I N T  T E C H N O L O G I E S      / /  
                                                ckp@grebyn.com      \\ / /    
Then, the disclaimer:  All expressed opinions are, indeed, opinions. \  / o
Now for the witty part:    I'm pink, therefore, I'm spam!             \/
