> Without any sort of management, you'd leak memory like > crazy in situations where neither the caller or the callee can release > the object.
A scheme where it is always the caller's job to release any object returned to it is perfectly viable, as any number of other computing platforms (such as COM on Windows) will testify. The callee simply has to retain the object before it returns it (and autorelease pools would not exist - hooray!). Cocoa is one of a kind in this regard, as far as I know. Anyway, I don't want to harp on. As you say, one has to live with it. I just happen to think it was a mistake. Seductive but dangerous. _______________________________________________ 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
