I don't think so. Releasing objects merely decreases their retain
count. It's up to the Obj-C runtime system to figure out in what order
to actually free the memory allocated for those objects. In other
words, we are not the ones deciding how and when to deallocate memory
allocated for objects. We merely indicate to the runtime system that
we're no longer interested in a given object at a given point in the
program runtime execution flow. What happens to the object after that
is not up to us.
On Jun 2, 2009, at 2:46 AM, Chunk 1978 wrote:
does it matter which order objects are released at the end of a
method? example:
...
at the end i'm finished with archiver, data and fourLines, but does it
matter in this case which one i release first?
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
