Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!caip!lll-crg!lll-lcc!qantel!ihnp4!inuxc!pur-ee!uiucdcs!uiucdcsb!robison
From: robison@uiucdcsb.CS.UIUC.EDU
Newsgroups: net.lang.c++
Subject: Re: oops, corrupted memory again!
Message-ID: <154000001@uiucdcsb>
Date: Mon, 28-Apr-86 23:42:00 EDT
Article-I.D.: uiucdcsb.154000001
Posted: Mon Apr 28 23:42:00 1986
Date-Received: Sat, 3-May-86 00:48:28 EDT
References: <4495@cbrma.UUCP>
Lines: 13
Nf-ID: #R:cbrma.UUCP:4495:uiucdcsb:154000001:000:544
Nf-From: uiucdcsb.CS.UIUC.EDU!robison    Apr 28 22:42:00 1986


> Now, if only somebody would invent an architecture where all objects,
> including dynamicly allocated objects, are isolated in memory, then any
> subscript error would cause an immediate memory fault ....
> ... otherwise it sounds like a great machine to do your debugging on.
>

Its been around at least two decades.  The Burroughs stack machines (6700 ...
A15) have this feature.  The hardware always checks subscripts before indexing.
In fact indexing is not an addressing mode on these machines, but rather an
instruction itself.

- Arch