Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!mcsun!cernvax!chx400!ethz!neptune!a!mneerach
From: mneerach@a.inf.ethz.ch (Matthias Ulrich Neeracher)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Why does the System not lock my INITs ?
Message-ID: <1006@neptune.inf.ethz.ch>
Date: 9 Aug 90 15:12:21 GMT
References: <157@neptune.inf.ethz.ch> <43741@apple.Apple.COM> <1195.26c1b5c3@waikato.ac.nz>
Sender: news@neptune.inf.ethz.ch
Reply-To: mneerach@a.inf.ethz.ch (Matthias Ulrich Neeracher)
Organization: Departement Informatik, ETH, Zurich
Lines: 20

In article <1195.26c1b5c3@waikato.ac.nz> ccc_ldo@waikato.ac.nz (Lawrence D'Oliveiro, Waikato University) writes:
>What happens if the INIT wants to stay in memory after execution?
>Some people may load resident code by creating a new non-resource block
>and copying the code to there, but others could just do a DetachResource
>on the INIT, and leave it locked. There's no good way that I can think
>of that the system can allow for the possibility of a DetachResource
>call while handling the locking/unlocking of the INIT code itself.

I disagree.

All the System would have to do is to LOCK the resource and to close the
file after having called all the INITs. Detached blocks will stay around,
resources will get released.

Matthias

-----
Matthias Neeracher                                   mneerach@c.inf.ethz.ch
  "I wouldn't recommend sex, drugs or insanity for everyone, 
   but they've always worked for me" -- Hunter S. Thompson