Re: AudioFile.h and FSRef??
Re: AudioFile.h and FSRef??
- Subject: Re: AudioFile.h and FSRef??
- From: email@hidden
- Date: Thu, 19 Sep 2002 14:19:06 +0100
Hi Stephen,
Thanks for the reply!
It's not that I'm trying to stay away from the functionality of Carbon,
but of the API (for a variety of reasons). I've always much preferred
objects over plain C, and C++ never sat right - it always felt like a
hack (not that it is). When I started using obj-c and in conjunction
with Cocoa just last year, I realized what I was really wanting :)
Also, I don't like mixing things in a large degree - languages, and
especially programming styles. And to have to use these AudioFile APIs
(without the conversions nicely provided by Kurt) would require a
reasonable amount of plain C code with Carbon calls - changing the
overall coding logic consistency and making things more confusing.
Naturally, I gravitated to Michael Thornburgh's great MTCoreAudio
implementation :)
-- John
You're trying hard to stay away from Carbon but if you're using Cocoa
you're already failing and you may not know it. :-)
Cocoa sits on top of the same services as Carbon
(ApplicationServices/CoreServices/etc.) and thus has automatic access
to things like the FSRef-based file manager APIs. It's already linked
in and loaded so it's no skin off your nose to use them. In addition,
the Cocoa event model is driven by the Carbon Event system so really
the two are quite intermingled. Given that, avoiding one or the other
is kind of silly -- use the best features of both worlds and you'll
really be better off. In fact, Jaguar goes a long way in letting you
mix Cocoa and Carbon things as much as you want.
The CoreAudio team (of which I am _not_ a part so don't confuse what I
say with official team statements) still does significant work on 9
for QuickTime so it's fairly natural for them to use APIs that exist
on 9 and X. Besides, the FSRef APIs are pretty feature rich and might
have more features than you think -- give 'em a look and maybe they
won't seem so evil. In case you don't know, one of the coolest
features of FSRefs is that the user can move a file on you while
you're working on it and you won't know the difference. Try that with
a path-based API!
stephen
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.