Best thing to do about the top-level nib "exception" to the rule is to
use NSWindowController or NSViewController to do your nib loading.
These classes properly take responsibility for top-level objects of
the nibs they load and then all you have to do is manage the lifetime
of the controller object as you normally would.
And, as long as we're on the topic... who can name the only other
exceptional case for the "release only if you alloc,new, copy or
retain" rule? (It's pretty old-school...)
Mike Ferris
_______________________________________________
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 [EMAIL PROTECTED]
