Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site hadron.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!harvard!seismo!rlgvax!hadron!jsdy From: jsdy@hadron.UUCP (Joseph S. D. Yao) Newsgroups: net.lang.c Subject: Re: if (p) ... Message-ID: <52@hadron.UUCP> Date: Sat, 2-Nov-85 17:50:18 EST Article-I.D.: hadron.52 Posted: Sat Nov 2 17:50:18 1985 Date-Received: Mon, 4-Nov-85 03:16:14 EST References: <2098@brl-tgr.ARPA> <916@celtics.UUCP> <2910@sun.uucp> Reply-To: jsdy@hadron.UUCP (Joseph S. D. Yao) Organization: Hadron, Inc., Fairfax, VA Lines: 22 Summary: 0 is not NULL, but converts to NULL. In article <2910@sun.uucp> guy@sun.uucp (Guy Harris) writes: >The definition of the C language requires that NULL be ZERO (how many times >do people have to be told this?). ... I really hate contradicting Guy, especially when I don't have my references at hand. But my memory tells me that 0 should convert to the NULL pointer, not necessarily be it. Guy's hand compilation a few lines earlier shows how: >2) the statement > if (p) foo(); >should have compiled into something like > compare_immediate p, #07777/0 # seg 7777, loc 0 > beq around > subroutine_call foo >around: This is recent in my accessible memory because this issue has been DISCUSSED TO DEATH n times already. Please do not respond. -- Joe Yao hadron!jsdy@seismo.{CSS.GOV,ARPA,UUCP}