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: Aran Mulholland <email@hidden>
- Date: Fri, 7 Jan 2011 14:51:41 +1100
nip it in the bud, i'm doing it, it was okay but as the app i'm
working on gets more complex (and time critical) I am starting to have
issues and am now contemplating a complete audio engine rewrite.... :
(
On Fri, Jan 7, 2011 at 2:41 PM, Paul Davis <email@hidden> wrote:
> On Thu, Jan 6, 2011 at 10:35 PM, Morgan Packard
> <email@hidden> wrote:
>> Based on jhno's recent post, and some other things I've heard, I'm getting
>> increasingly nervous about the fact that I'm writing audio code in Objective
>> C. My app works fine currently, with a bunch of Objective-C audio code, but
>> I'd hate to realize, a year or two from now, that I've been using the wrong
>> tool for the job. Should I nip this in the bud and switch to using purely
>> C++? Is there any case to be made for sticking with Objective-C?
>
> there is no case to be made for using obj-c within the render callback
> of a AudioUnit or application. elsewhere there are plenty of arguments
> for and against, but within the process call tree that starts with the
> render callback, you should avoid objective C or any other
> non-statically typed language.
> _______________________________________________
> 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
>
_______________________________________________
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