Re: Interrupt-level callbacks
Re: Interrupt-level callbacks
- Subject: Re: Interrupt-level callbacks
- From: j o a r <email@hidden>
- Date: Thu, 3 Jun 2004 07:34:14 +0200
Just like with signal handling I would assume that using Cocoa in any
shape and form at interrupt time is NOT OK. You have to use only
functions and frameworks that are clearly labeled as being safe to use
at interrupt time. This is as far as I know. Also read this:
<
http://developer.apple.com/technotes/tn/tn1104.html>
j o a r
On 2004-06-02, at 22.55, John Ashley Burgoyne wrote:
>
I am writing an application based on the cross-platform PortAudio
>
library (www.portaudio.com) to do some real-time audio processing.
>
PortAudio handles the audio I/O through a callback (which on OS X is
>
implemented with the AudioToolbox and CoreAudio). The PortAudio
>
documentation states:
>
>
"Your callback function is often called by an interrupt, or low level
>
process so you should not do any complex system activities like
>
allocating memory, or reading or writing files, or printf(). Just
>
crunch numbers and generate audio signals. What is safe or not safe
>
will vary from platform to platform."
>
>
Some postings in the list archives suggest that it is unsafe to use
>
Objective-C in any way at the interrupt level. Other places, e.g.,
>
>
http://www.stepwise.com/Articles/Technical/2001-03-20.01.html
>
>
suggest that it is safe and that the only problems are the usual ones
>
caused by multiple threads. Does anybody know which is the case?
[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.