Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!snorkelwacker.mit.edu!shelby!agate!twinkies.berkeley.edu!lippin
From: lippin@twinkies.berkeley.edu (The Apathist)
Newsgroups: comp.sys.mac.programmer
Subject: Re: HLock Function List
Message-ID: <1991Feb22.021825.3414@agate.berkeley.edu>
Date: 22 Feb 91 02:18:25 GMT
References: <1991Feb20.042807.12553@ux1.cso.uiuc.edu> <3947@uakari.primate.wisc.edu> <12178@goofy.Apple.COM>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Reply-To: lippin@math.berkeley.edu
Organization: Authorized Service, Incorporated
Lines: 27

In <3947@uakari.primate.wisc.edu>, bin@primate.wisc.edu (Brain in
Neutral) writes:

>> It's safest to consider the list to be "all ToolBox calls", because
>> although not every call *today* has the potential to cause memory to
>> be moved, the list continues to expand over time.  A function that's
>> safe today might not be safe tomorrow.

In <12178@goofy.Apple.COM>, lsr@Apple.com (Larry Rosenstein) replies:

> Someone once mentioned that InitGraf used to be off the list, but now
> is on the list.  Sure enough, it's not mentioned in volume 1 but is
> mentioned in volume 5.  But are there other calls that were made
> unsafe?

SysBeep was also memory-safe once, long ago.

Nevertheless, one still shouldn't consider the list to contain all
toolbox calls, for the simple reason that it's not practical.  None of
the calls on the list can be used at interrupt time, and interrupt
tasks need *something* to work with.

					--Tom Lippincott
					  lippin@math.berkeley.edu

	"Thank you for observing all safety precautions."
					--Dark Star