> Does your class have a subclass, which also has a +initialize method, which > doesn't call [super initialize]? That might cause this sort of behavior, > because the order in which the classes load may be indeterministic.
That's unnecessary - by the time that you got around to calling [super initialize], the runtime would have already done it for you. +initialize is special in that the runtime automatically sends it to every class before it's first used, and superclasses receive it before their subclasses. From the docs: "Superclasses receive this message before their subclasses." "Since the runtime sends appropriate initialize messages automatically, you should typically not send initialize to super in your implementation." _______________________________________________ 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
