Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!think.com!mck-csc! From: pete@csc-sun.mckinsey.com (Peter Gaston) Newsgroups: comp.sys.mac.programmer Subject: Re: doing real work at interrupts Message-ID: Date: 9 Nov 90 17:36:54 GMT References: <1990Oct30.131140.10113@hellgate.utah.edu> <1185@skye.cs.ed.ac.uk> <25478@dartvax.Dartmouth.EDU> <3a53g2.]53@smurf.sub.org> Sender: @mck-csc.mckinsey.com Organization: McKinsey & Co., Inc., Cambridge, MA Lines: 17 In-reply-to: urlichs@smurf.sub.org's message of Fri, 02 Nov 90 13:32:24 GMT In comp.sys.mac.programmer, article <25478@dartvax.Dartmouth.EDU>, llama@eleazar.dartmouth.edu (Joe Francis) writes: < An even simpler (in my opinion) solution is for the interrupt handler to < post events to the app. PostEvent() and PPostEvent() are not on the < "forbidden interupt time ToolBox calls" list. Can anyone confirm they are < indeed safe in this situation? < Do y'all remember when we were cautioned about not depending upon AppleTalk completion information coming from the event queue? Right, the event queue could overflow. In general not a great idea. pete gaston mckinsey & co.