Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!bu.edu!dartvax!eleazar.dartmouth.edu!llama
From: llama@eleazar.dartmouth.edu (Joe Francis)
Newsgroups: comp.sys.mac.programmer
Subject: Re: doing real work at interrupts
Keywords: driver
Message-ID: <25478@dartvax.Dartmouth.EDU>
Date: 1 Nov 90 15:48:09 GMT
References: <2303@heavens-gate.lucid.com> <1990Oct30.131140.10113@hellgate.utah.edu> <1185@skye.cs.ed.ac.uk>
Sender: news@dartvax.Dartmouth.EDU
Organization: Dartmouth College, Hanover, NH
Lines: 17


someone writes:
>> How about opening a "device driver" that doesn't actually do any
>> reading or writing to a device, but has its "dNeedTime" flag set,

In article <1185@skye.cs.ed.ac.uk> nick@lfcs.ed.ac.uk writes:>
Why bother? Just declare a static circular buffer, have the interrupt
>routine place messages into it in some format, and have the main
>application examine it somewhere in the event loop.

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?

--------------------------------------------------------------------------
"Read My Lips: No Nude Texans!" - George Bush clearing up misunderstanding