Re: CF Types and AU
Re: CF Types and AU
- Subject: Re: CF Types and AU
- From: Bill Stewart <email@hidden>
- Date: Tue, 5 Aug 2003 01:14:16 -0700
Brian
On Monday, August 4, 2003, at 08:11 PM, Brian Willoughby wrote:
Wow. This seems awful. Not only is it inconsistent, but it goes
against the
principles of CoreFoundation reference counting. Looking at the
documentation,
CoreFoundation is intended as a C language interface to the opaque
objects in
Cocoa. As such, they follow the same rules as Cocoa objects for
retention. In
other words, you should only call release on objects that you create
manually,
copy, or retain. Even the class factory methods are autoreleased,
such that
the caller does not need to worry about release.
Core Foundation is a set of C API... (It is actually in open source).
As a C API it has no concept of auto-releasing pools, or any of the
other abstractions of Cocoa's object model (and to my mind the
auto-releasing pools of Cocoa have their own problems, as do gc models,
as do dangling pointers, etc....). Both Cocoa and Carbon rely
extensively on CF's functionality (so you have this whole layering
around the wrong way)
Bill
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
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.