oops, corrupted memory again!

[KW Heuer]

In article <117 at prairie.UUCP> prairie!dan (Dan Frank) writes:
[comments on overflow-checking architecture]
>   You're probably better off with a language that compiles checks into
>the code, and an option to turn [them] off...

As I mentioned, you can do it this way in C++, but when you want to use
pointers you have to copy three words instead of one.  (Or you can use
a language like pascal, which "solves" the problem by disallowing pointer
arithmetic.)  What I was thinking of, though, was a computer with strict
architecture that could be used for development and testing; when the
program is shipped to the Real World it would presumably run on "normal"
architecture.

Karl W. Z. Heuer (ihnp4!bentley!kwh), The Walking Lint