Re: Do I really need to steer clear of Objective-C when providing data for RemoteIO?
Re: Do I really need to steer clear of Objective-C when providing data for RemoteIO?
- Subject: Re: Do I really need to steer clear of Objective-C when providing data for RemoteIO?
- From: tahome izwah <email@hidden>
- Date: Fri, 7 Jan 2011 18:59:53 +0100
That is relatively easy to avoid - sorry for posting the link again
but this has been previously discussed in quite some depth:
http://lists.apple.com/archives/cocoa-dev/2006/feb/msg01735.html
HTH
--th
2011/1/7 Paul Davis <email@hidden>:
> On Fri, Jan 7, 2011 at 11:58 AM, Gregory Wieber <email@hidden> wrote:
>> You want your render callback code to be as efficient as possible, and that
>> means that the overhead of calling objective-c messages can come into play.
>> That said, objective-c messages are not always going to be your bottleneck,
>> because it's easy to do something else in your code that's 10x's worse than
>> using a few simple objective-c messages. But if you're unsure of the gritty
>> details, then just avoid them altogether.
>
> the issue is not the "inefficiency" of objective C versus anything
> else. its that the objective C runtime can block.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden