Re: Displaying an AudioUnitCarbonView in a Cocoa application?
Re: Displaying an AudioUnitCarbonView in a Cocoa application?
- Subject: Re: Displaying an AudioUnitCarbonView in a Cocoa application?
- From: Per Bull Holmen <email@hidden>
- Date: Fri, 11 Jun 2010 07:49:31 -0700 (PDT)
Paul Davis wrote:
> On Fri, Jun 11, 2010 at 1:45 AM, john smith <email@hidden> wrote:
> > So, while Cocoa is unavoidable for 64-bit, surely creating a 32-bit host
> > with no support for Carbon means you won't be able to support a lot of the
> > plug-ins out there.
My host supports Carbon now... :)
> it would be a more compelling argument if you had been able to
> convince Apple too :)
>
Wading through that awful quagmire that is Carbon, of pascal strings and calling conventions, always returning values by reference, outdated memory handling routines, a jungle of conflicting data types and structures etc., it puzzles me that so many developers still wants to hold on to it, nine years after OS X came out? Is it because they don't want to learn Objective-C? Because they want to develop new features rather than reprogram what they already have? Because of features lacking in Cocoa, or because they don't even want to update their code... Perhaps I shouldn't have posted this because it is off-topic and may start a flame war... I do understand, though, that Apple wants to move on.
If this is off-topic then moderators feel free to delete it.
Per
_______________________________________________
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