Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!cit-vax!news
From: news@cit-vax.UUCP
Newsgroups: comp.arch
Subject: Re: catering to bad code
Message-ID: <1880@cit-vax.Caltech.Edu>
Date: Fri, 27-Feb-87 15:24:23 EST
Article-I.D.: cit-vax.1880
Posted: Fri Feb 27 15:24:23 1987
Date-Received: Sun, 1-Mar-87 11:08:16 EST
References: <14833@amdcad.UUCP> <6620001@hpcea.HP.COM>
Reply-To: jon@oddhack.UUCP (Jon Leech)
Organization: California Institute of Technology
Lines: 20

Organization : California Institute of Technology
Keywords: 
From: jon@oddhack.Caltech.Edu (Jon Leech)
Path: oddhack!jon

In article <6620001@hpcea.HP.COM> wunder@hpcea.HP.COM (Walter Underwood) writes:
>The HP-UX C compilers have flags that allow you to force traps on null
>pointer derefs, or to force accepting a null pointer deref (you get a 0
>at that location).  The default behavior depends upon the actual
>implementation.
>
>Providing both choices to the user is obviously the best idea.
	True enough. A pity HP doesn't do it.
	The HP 9000/300 C compiler has these flags; unfortunately, they
are no-ops. NULL is always mapped whether you want it or not. I think
they only work on series 500 machines. 

    -- Jon Leech (jon@csvax.caltech.edu || ...seismo!cit-vax!jon)
    Caltech Computer Science Graphics Group
    __@/