Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site exodus.UUCP
Path: utzoo!linus!security!genrad!grkermit!masscomp!clyde!burl!hou3c!hocda!houxm!mhuxl!ulysses!gamma!exodus!rdsmith
From: rdsmith@exodus.UUCP
Newsgroups: net.unix-wizards
Subject: Re: NULL vs 0
Message-ID: <126@exodus.UUCP>
Date: Fri, 20-Jan-84 09:42:26 EST
Article-I.D.: exodus.126
Posted: Fri Jan 20 09:42:26 1984
Date-Received: Sat, 21-Jan-84 07:22:31 EST
References: <345@hocda.UUCP> <2406@rabbit.UUCP>, <4808@umcp-cs.UUCP>
Organization: CSO, Inc., Murray Hill, NJ
Lines: 18

Chris Torek says:
	I have one little minor thing to say here.  I don't know about those
	68k systems that have sizeof (int) == 2, sizeof (char *) == 4, but all
	the stdio.h files I've seen say

	#define NULL 0

	(NOT #define NULL ((char *) 0)), so it won't make a bit of difference
	...

Chris is headed in the right direction with the stdio.h reference, but the
rest of the article really blows it.  Of course all of the stdio.hs you've
seen have NULL defined that way; that is the way THOSE machines represent
NULL.  The point is that << stdio.h IS THE PLACE WHERE SUCH A MACHINE
DEPENDENCY BELONGS >>, not scattered throughout user programs.  Stick to
NULL, and expect each machine to properly define it in stdio.h.

	Randy D. Smith   CSO, Inc.   HL 3L-528   (201) 564-3797