Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!sdd.hp.com!wuarchive!udel!princeton!njsmu!mccc!pjh From: pjh@mccc.edu (Pete Holsberg) Newsgroups: comp.lang.c Subject: Re: Zero/nil/NULL/NUL/0/... Message-ID: <1991Apr23.184317.12230@mccc.edu> Date: 23 Apr 91 18:43:17 GMT References: <1991Apr20.134839.11052@grebyn.com> Organization: The College On The Other Side Of Route One Lines: 25 In article <1991Apr20.134839.11052@grebyn.com> ckp@grebyn.com (Checkpoint Technologies) writes: =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) = 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. How about "These two strings are the same"? Pete -- Prof. Peter J. Holsberg Mercer County Community College Voice: 609-586-4800 Engineering Technology, Computers and Math UUCP:...!princeton!mccc!pjh 1200 Old Trenton Road, Trenton, NJ 08690 Internet: pjh@mccc.edu Trenton Computer Festival -- 4/20-21/91