Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 8/23/84; site ucbcad.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!talcott!panda!genrad!decvax!ucbvax!ucbcad!faustus
From: faustus@ucbcad.UUCP (Wayne A. Christopher)
Newsgroups: net.unix-wizards
Subject: Re: NULL problems
Message-ID: <240@ucbcad.UUCP>
Date: Tue, 14-May-85 16:19:28 EDT
Article-I.D.: ucbcad.240
Posted: Tue May 14 16:19:28 1985
Date-Received: Thu, 16-May-85 21:23:32 EDT
References: <10550@brl-tgr.ARPA> <5369@ucla-cs.ARPA>
Distribution: net
Organization: UC Berkeley CAD Group, Berkeley, CA
Lines: 10

Can anybody think of any problems with making "NULL" a part of the C
language, specifically as a pointer to anything with a value of 0? As
has been pointed out, it is a pain to have to remember to cast it all
the time, and I tend to think of NULL as a pointer, not an integer.
Perhaps then if anybody wanted to change NULL to be some other value,
for instance if he wanted *NULL to be invalid, then the compiler could
be changed to make NULL behave like 0 in things like "while (p)" which
should mean "while (p != NULL)"...

	Wayne