On Jun 15, 2013, at 1:32 PM, Gordon Apple wrote: > I still think the compiler should be smart enough to block this > without having to put a on-shot blocking flag in awakeFromNib, which I have > now done.
My question would be, why are you using awakeFromNib specifically in the first place? I really do find that it's not the right place to do things. IMO an instance should not expect to be loaded from a nib (which means it shouldn't use awakeFromNib), and any File's Owner which is loading a nib can perform its duties after loading the nib rather than in its own awakeFromNib. When both of those things are true, there are better places to do setup work and avoids the whole mess of trying to manage flags for which awakeFromNib call is mapped to which nib load. -- Seth Willits _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
