Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83 ; site lvbull.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!houxm!houxz!vax135!cornell!uw-beaver!tektronix!hplabs!sdcrdcf!sdcsvax!akgua!mcnc!decvax!mcvax!vmucnam!lvbull!pete
From: pete@lvbull.UUCP (Pete Delaney - Rockey Mountain UNIX Consultants)
Newsgroups: net.unix-wizards,net.lang.c
Subject: Re: Using NULL as an illegal pointer
Message-ID: <273@lvbull.UUCP>
Date: Thu, 5-Jul-84 03:08:20 EDT
Article-I.D.: lvbull.273
Posted: Thu Jul  5 03:08:20 1984
Date-Received: Mon, 9-Jul-84 01:03:56 EDT
References: <1273@sri-arpa.UUCP> <4011@utzoo.UUCP> <311@harvard.ARPA>, <7713@umcp-cs.UUCP>
Organization: BULL, Louveciennes, France
Lines: 10

Don't forget us word addressing folks, we have pointers that change length
as a function of environment(stack vs arg) and type (int vs char).  We use
two types of NULL pointers:

#define NULL		(char *)0	/* Default: worst case BASE + INDEX */
#define NULL_PTR	(int *)0	/* NOT Pointer to char */

All that kernel trapping code that assumes environment independence of pointers
is also fun to deal with.  Wish (Honeywell) Bull would switch to BYTE addressing.
					Pete Delaney