Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!stanford.edu!neon.Stanford.EDU!kaufman
From: kaufman@neon.Stanford.EDU (Marc T. Kaufman)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Re-opening my resource file.
Message-ID: <1991Mar20.013646.4538@neon.Stanford.EDU>
Date: 20 Mar 91 01:36:46 GMT
References: <1991Mar19.002406.23347@ux1.cso.uiuc.edu> <FRANCIS.91Mar19172528@arthur.zaphod.uchicago.edu>
Organization: Computer Science Department, Stanford University, Ca , USA
Lines: 19

In article <FRANCIS.91Mar19172528@arthur.zaphod.uchicago.edu> francis@arthur.zaphod.uchicago.edu (Francis Stracke) writes:
>In article <1991Mar19.002406.23347@ux1.cso.uiuc.edu> resnick@cogsci.uiuc.edu (Pete Resnick) writes:

>   re-open? I can store the filename and vRefNum or DirID into the code
>   itself, but this seems like a pain, let alone the fact that some bozo

>Let alone the fact that it'll break if Apple ever gets around to
>protecting code segments.  :-)

Not likely, unless and until Apple gets around to providing a second heap
for code.  The memory manager can't tell code from other resources, after all.
Even code resources have to be loaded, moved high, locked, and possibly have
addresses adjusted (what? write to a code resource?).

I think the best we can ever expect is that applications can be protected
from one another with VM, not that code segments within an app can be
protected.

Marc Kaufman (kaufman@Neon.stanford.edu)