🚀 go-pugleaf

<oog>

	I too spent many happy years working on a system that ALWAYS verified
pointers and array bounds ... Burroughs large systems (B6700 et al), they
have such a crude memory management (to be fair they were designed in the late
60s early 70s, and have a stack architecture) that the system integrity depends
on the fact the NOONE can make machine code with out using a special trusted
program called a "compiler" (ie only a "compiler" can set a file's type to
code file). It takes the super-user to mark a code file as being a "compiler"
code file. Needless to say no-body really misses not being able to turn off
range checking, except for the Fortran types who get programs from elsewhere ...

		Paul Campbell
		..!ucbvax!unisoft!paul