• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Who is releasing my CFAllocator?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Who is releasing my CFAllocator?


  • Subject: Re: Who is releasing my CFAllocator?
  • From: Nat! <email@hidden>
  • Date: Wed, 31 Jul 2002 20:46:04 +0200

Am Mittwoch den, 31. Juli 2002, um 03:55, schrieb Ali Ozer:

If I create my own CFAllocator, it might be unavoidable that some objects are created off it. Now these objects might be retained so it's probably outside my scope to determine, when to get rid of the CFAllocator. There is a "retain"/"release" call back... Should my CFAllocator look for a release count of zero and release itself or is this done my CoreFoundation automatically ?

CF will retain/release the allocator it's been given when it allocates a CF object using an allocator. This is not true for arbitrary memory allocated with an allocator though.
Ali

Yeah OK, but I don't see how this answers my question. Or is this saying, that once I created an allocator and let CF use it, that I should NOT deallocate it ?

Ciao
Nat!

Jedenfalls sind zehn Fehlstarts hintereinander [E. Fuchs]
ein sehr interessanter Beweis
fuer unsere Theorie
von der natuerlichen Ueberlegenheit des Dezimalsystems
_______________________________________________
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.

References: 
 >Re: Who is releasing my CFAllocator? (From: Ali Ozer <email@hidden>)

  • Prev by Date: Re: Acid Test For MVC Design?
  • Next by Date: Cursor
  • Previous by thread: Re: Who is releasing my CFAllocator?
  • Next by thread: Accessor methods and (auto)release <Memory trail>
  • Index(es):
    • Date
    • Thread