Re: Leaking Memory
Re: Leaking Memory
- Subject: Re: Leaking Memory
- From: Robert Goldsmith <email@hidden>
- Date: Fri, 24 Jan 2003 02:33:07 +0000
>
> I saw nothing wrong with the simplification as a starting point to
>
> grasp memory management.
>
>
On the contrary, there was a fundamental inaccuracy in two statements
Fundamentally, we are all nothing more than probability wave functions,
it looks very likely that the universe has 22 dimensions and time is a
figment of our imagination. This does not stop us pretending we exist,
feeling the universe is something that is happening elsewhere and time
is the most important thing there is. It all helps us live our lives
without getting stressed. Until a time when "autorelease -- deallocates
an object when you don't need it anymore" just doesn't cut it any more,
it will do :)
Of course, the next question (and one not made very clear by any of the
many documents I have read) is exactly -when- autoreleased items are
cleared. for instance, if I am in a method and have created a local
instance of an NSMutableArray using the arrayWithCapacity call, is it
released when I exit the method or is it placed in the global (well,
thread-wide) auto-release pool. On the other hand, if I autorelease an
instance I received from else-where in the same method, when does it
get release - at the end of the method or when the autorelease pool is
released. Does the AppKit look after multiple pools which change when
and how often objects are actually released? Can releases stretch
across threads (global pool cleaning, maybe) etc.
Robert
---
GnuPG public key:
http://www.Far-Blue.co.uk/RSGoldsmith.asc
[demime 0.98b removed an attachment of type application/pgp-signature which had a name of PGP.sig]
_______________________________________________
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.