Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!brl-adm!brl-smoke!brl-sem!ron
From: ron@brl-sem.ARPA (Ron Natalie <ron>)
Newsgroups: net.lang.c
Subject: Re: ANSI C
Message-ID: <414@brl-sem.ARPA>
Date: Thu, 21-Aug-86 14:07:37 EDT
Article-I.D.: brl-sem.414
Posted: Thu Aug 21 14:07:37 1986
Date-Received: Thu, 21-Aug-86 22:22:28 EDT
References: <86900009@haddock> <86900017@haddock> <971@ucbcad.BERKELEY.EDU>
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 13

In article <971@ucbcad.BERKELEY.EDU>, faustus@ucbcad.BERKELEY.EDU (Wayne A. Christopher) writes:
> If there is something of interest at location 0 then you should complain to
> whomever put it there.  It's a very good idea to make null pointer references
> cause a fault -- this catches lots of nasty bugs.  If this isn't the case
> on your machine, you can still use the tricks mentioned above.
> 
Even the PDP-11's used to put a zero on the split-I/D images at zero to
assure there wasn't anything useful at zero.  Unfortunately, people learned
to rely on this.  I suspect we might not have had as much problems if VAX's
and PDP-11's had something useless like at "setd" instruction at the bottom
of their dataspaces

-Ron (p&P6) Natalie