Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!efi!tim
From: tim@efi.com (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Why does the System not lock my INITs ?
Message-ID: <1990Aug11.000523.7407@efi.com>
Date: 11 Aug 90 00:05:23 GMT
References: <157@neptune.inf.ethz.ch> <43741@apple.Apple.COM> <1195.26c1b5c3@waikato.ac.nz>
Organization: Electronics For Imaging, Inc.
Lines: 14

In article <1195.26c1b5c3@waikato.ac.nz> ccc_ldo@waikato.ac.nz
(Lawrence D'Oliveiro, Waikato University) writes:
>As to why the system doesn't lock INITs before executing them:
>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.

Why should the system bother to unlock a resource from an INIT file?
The resource will go away when the file is closed anyway.  If INIT 31
just locked INITs on entry and didn't unlock them when they return,
everything would be fine.