Re: Carbon is C++?
Re: Carbon is C++?
- Subject: Re: Carbon is C++?
- From: Erik Buck <email@hidden>
- Date: Sun, 28 Feb 2010 22:24:49 -0500
I disagree. I have written very low latency device drivers in Objective-C. Why do you think Objective-C has too much "latency" for audio? When properly used, Objective-C programs are no more likely to be preempted than any other kind of program. Message dispatch generally has constant time and is only 2.5 times the cost of a C function call. There aren't many function calls or messages sent in audio processing anyway. Signal processing routines tend to be long loops. Objective-C _IS_ C which means it is likely usable in any situation where C is usable.
On Feb 28, 2010, at 8:23 PM, Kyle Sluder wrote:
> On Sun, Feb 28, 2010 at 1:33 PM, Paul Bruneau
> <email@hidden> wrote:
>> Or if you want to do a bunch of audio stuff in the iPhone, then you can enjoy the experience of learning C++ even though all you want to do is obj-c. Depressing.
>
> Nothing in Core Audio requires you to use C++, but all of the stuff in
> PublicUtility is C++. You could implement an audio unit in straight C
> if you wanted.
>
> ObjC would never be a good idea for audio because it involves far too
> much latency. Audio demands realtime performance, which a dynamic
> language like ObjC simply cannot give you.
>
> --Kyle Sluder
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden