Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!caen!sol.ctr.columbia.edu!ira.uka.de!smurf!urlichs From: urlichs@smurf.sub.org (Matthias Urlichs) Newsgroups: comp.sys.mac.programmer Subject: Re: HLock Function List Message-ID: Date: 22 Feb 91 11:06:35 GMT References: <1991Feb20.042807.12553@ux1.cso.uiuc.edu> <3947@uakari.primate.wisc.edu> <12178@goofy.Apple.COM> Organization: University of Karlsruhe, FRG Lines: 29 In comp.sys.mac.programmer, article <12178@goofy.Apple.COM>, lsr@Apple.com (Larry Rosenstein) writes: < < I think this is being overly cautious. There's no way, for example, that < SetRect, SetPt, HLock, BlockMove (to name a few) will ever move memory. < While HLock probably won't move memory, you still can't use it at interrupt time, so it's on "the list". < 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? < InitGraf is probably a safe call to make unsafe. (Pun intended.) The one call that I have some misgivings about is SetCursor. Apart from some cute utilities rerouting it to SetCCursor for some cursor shapes (I wrote one myself...), MPW started to call WaitNextEvent in its patch. While this probably didn't break anything major, I remember people being somewhat anxious about the possibility. Personally, I don't use that list much. I keep a "safe to call" list in the back of my head, and add to this any procedures/methods in my application which won't move memory when I call them. I then forget to add these to MacApp's keep-these-segments-resident list. :-( :-( -- Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de /(o\ Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49+721+621127(0700-2330) \o)/