Skip navigation.
 
mlRe: Memory management with CF Objects
FROM : Jim Correia
DATE : Fri Jan 03 15:44:02 2003

On Friday, January 3, 2003, at 06:35  PM, Rosyna wrote:

> ATSGetFontName gives you a new CFStringRef that you *must* release. It 
> does not start with CF so it does not follow the CF rule. You have to 
> guess with these cases most of the time..


Rather than guessing, you could always check the documentation. If it 
says (which in this case it does 
<http://developer.apple.com/techpubs/macosx/Carbon/text/ATSTypes/ATS/
atsfontsref_Reference/function_group_3.html#//apple_ref/c/func/
ATSFontGetName
> it is 100% more reliable than any guess you make.)

It would be better if the API names made clear the ownership, but if 
they do not doesn't leave us stranded in guess-land.

Jim


Related mailsAuthorDate
mlMemory management with CF Objects Armin Briegel Jan 3, 04:50
mlRe: Memory management with CF Objects Finlay Dobbie Jan 3, 04:59
mlRe: Memory management with CF Objects Rosyna Jan 3, 15:36
mlRe: Memory management with CF Objects Jim Correia Jan 3, 15:44
mlRe: Memory management with CF Objects Rosyna Jan 3, 20:52