"Numerical Recipes in C" is nonportable code

[Bob Larson]

In article <1450 at ficc.uu.net> peter at ficc.uu.net (Peter da Silva) writes:
>In article <13454 at mimsy.UUCP>, chris at mimsy.UUCP (Chris Torek) writes:
>> In article <1429 at ficc.uu.net> peter at ficc.uu.net (Peter da Silva) writes:
>> -What's to stop you from doing the following:
>> -	Generate code in an array.
>> -	Jump to the beginning of the array. *

Decent memory protection.  (There are those of us who believe that
executable and writable memory should be mutually exclusive.  (with a
provision to change from one to the other.))

>So what's to stop me from writing out a load module and subverting
>the protection mechanism, as I noted in my (deleted) footnote?

The same type of protection mechinism that makes it impossible
(or hopefully at least difficult) to alter other users files.
Writing out executalbe files may be considered a priviliged
function reserved to compilers.

(Please note I am not saying that I think that compilers are the proper
place to enforce system security, just that portably written code shouldn't
have undue hardship running on such a machine.)
-- 
Bob Larson	Arpa: Blarson at Ecla.Usc.Edu	blarson at skat.usc.edu
Uucp: {sdcrdcf,cit-vax}!oberon!skat!blarson
Prime mailing list:	info-prime-request%ais1 at ecla.usc.edu
			oberon!ais1!info-prime-request