On 11/29/04 3:49 PM, Clark Cox didst favor us with:
> On Mon, 29 Nov 2004 14:26:56 -0500, Laurence Harris <email@hidden> wrote:
>> On 11/29/04 2:08 PM, Eric Gorr didst favor us with:
>>
>>> At 2:01 PM -0500 11/29/04, Laurence Harris wrote:
>>>> Under no circumstances should you release the string returned by CFSTR.
>>>
>>> You can if the CFRelease is balanced by a CFRetain.
>>
>> True. In that case the string isn't released, the refcount is just
>> decremented. I find it easiest to just think of CFSTR() as a CF "Get"
>> function.
>>
>
> <pedantic>
> But it *is* released, it just isn't deallocated or destroyed.
> <http://developer.apple.com/documentation/CoreFoundation/Reference/CFTypeRef/R
> eference/FunctionGroupIndex.html#//apple_ref/doc/uid/20001203/F11071>
> </pedantic>
Sorry, I phrased it incorrectly. I'm used to thinking of releasing as
releasing the memory.
Larry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
