On Oct 8, 2006, at 6:50 PM, Charles Yeomans wrote:
How does memory management work with CFStringRef? Presumably if I
create a CFStringRef, or let the framework do it implicitly in the
course of conversion, then the framework correctly manages the
reference count. But what if I obtain a CFStringRef by reference,
or as the return value of a function? Judging from some crashes I
can generate, it looks like a CFStringRef always calls CFRelease
when the CFStringRef reference is destroyed. If so, then this is
certainly predictable, but this seems like something that needs to
be documented.
Charles Yeomans
In fact, the release notes for 2005r4 suggests that in fact CFRelease
is always called when a CFStringRef reference is destroyed. Still,
this would be nice for this to be included in the language
reference. I've filed a feedback report.
<http://www.realsoftware.com/feedback/viewreport.php?reportid=jrecgqxk>
Charles Yeomans
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
