Re: Why is CoreAudio C++ not Objective-C?
Re: Why is CoreAudio C++ not Objective-C?
- Subject: Re: Why is CoreAudio C++ not Objective-C?
- From: Paul Slocum <email@hidden>
- Date: Wed, 20 Oct 2010 12:50:50 -0400
Word!!!
On Wed, Oct 20, 2010 at 1:07 AM, Ross Bencina
<email@hidden> wrote:
> Brian Willoughby wrote:
>>
>> In contrast, the problem with CoreAudio - and particularly AudioUnits -
>> is that a bug in a single line of sample code in the AU classes gets copied
>> by every developer who releases an AU, and that bug must be fixed
>> separately by each developer (some of whom may have gone out of business)
>> after it has been discovered. There's also a lot of duplicated source code
>> compiled into CoreAudio applications built on C++.
>
> This can hardly be blamed on C++ -- there are ways to achieve what you
> describe about DriverKit in C++ -- the real problem is that Apple require
> people to incorporate their sample code at all rather than maintain a
> clearly documented specification and leave developers to write their own
> code. CoreAudio "sample code" contains details that should be hidden on the
> other side of the API divide... this is just poor design. Sadly Apple have
> chosen to substitute sample code in place of specification and
> documentation.
>
> I could go on, but I won't.
>
> Ross.
>
>
> _______________________________________________
> 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