Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!sdd.hp.com!caen!uwm.edu!bionet!agate!e260-1g.berkeley.edu!c60b-1eq From: c60b-1eq@e260-1g.berkeley.edu (Noam Mendelson) Newsgroups: comp.lang.c Subject: Re: Zero/nil/NULL/NUL/0/... Message-ID: <1991Apr20.191404.26830@agate.berkeley.edu> Date: 20 Apr 91 19:14:04 GMT References: Sender: root@agate.berkeley.edu (Charlie Root) Organization: University of California, Berkeley Lines: 27 In article 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) ^^^^^^^^^^^^^^^^^^ Unused pointers are not automatically initialized to NULL. > -> The null character (ASCII, etc) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ On most but not all machines. > -> End of file (EOF) ^^^^^^^^^^^^^^^^^ No, EOF is implementation-dependent but is usually == -1. > -> Not true (FALSE) If you look through your's machines header files, you'll find quite a lot of things which are #def'ed to zero. So what? -- +==========================================================================+ | Noam Mendelson ..!ucbvax!web!c60b-1eq | "I haven't lost my mind, | | c60b-1eq@web.Berkeley.EDU | it's backed up on tape | | University of California at Berkeley | somewhere." |