Re: CoreFoundation and CFDate functions - question on memory de-allocation
Re: CoreFoundation and CFDate functions - question on memory de-allocation
- Subject: Re: CoreFoundation and CFDate functions - question on memory de-allocation
- From: j o a r <email@hidden>
- Date: Thu, 8 Jan 2004 09:52:52 +0100
On 2004-01-08, at 09.39, Kent Behrends wrote:
>
> Are you doing this with CF-functions for performance reasons?
>
No - Just using C not Obj-C :)
So, what are you doing on Cocoa-dev? Oh, well... :)
>
> In the example below I would assume that you have to free the
>
> aCFDate, dateFormatter1 and dateStr variables - basically those that
>
> are created using "*Create*" methods. Read the CF documentation if
>
> you are uncertain, and use memory monitoring tools to verify that you
>
> got it right.
>
Ya - some of the routines say the programmer is responsible of
>
releasing the allocated memory. I just haven't found an example
>
showing a CFDate being released...
I'm no authority on the CF frameworks, but I would assume that you
would notice fairly quickly if you freed something that shouldn't be
freed.
I also hope that they are consistent in their use of the "Create"
function name component - I would guess that this is the case.
j o a r
[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.