Path: utzoo!attcan!uunet!mcsun!cernvax!chx400!ethz!neptune!b!mneerach
From: mneerach@b.inf.ethz.ch (Matthias Ulrich Neeracher)
Newsgroups: comp.sys.mac.programmer
Subject: Why does the System not lock my INITs ?
Summary: Don't ask what your System can do for you...
Message-ID: <157@neptune.inf.ethz.ch>
Date: 2 Aug 90 12:03:31 GMT
Sender: news@neptune.inf.ethz.ch
Reply-To: mneerach@b.inf.ethz.ch (Matthias Ulrich Neeracher)
Organization: Departement Informatik, ETH, Zurich
Lines: 15

This week I tried to write an INIT (I did some before). Every time I tested
it, it crashed. Stepping through my debugger, I found out that my INIT was
unlocked and on return from a trap had been moved away. No problem... I just 
set the lock bit on the INIT resource and everything worked as expected.

Still, I'm curious: After all, the System locks most resources before
calling them: CODE, WDEF, MDEF, CDEF, snth and probably even cdev resources.
Why are INIT's not locked by INIT31 ?

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