Roland,
Check this out:
http://cocoawithlove.com/2008/03/cocoa-application-startup.html
The code should arguably live in a +initialize method.
davez
On Feb 24, 2011, at 6:41 AM, Roland King wrote:
> I burned myself today with a pattern I've been using for ages. I have lots of
> UIView subclasses which could be initialized with initWithFrame: or
> initWithCoder: so I have one -(void)internalInit method which I call from
> both of them to do the real work. Of course eventually I went and subclassed
> one of my own classes and the call to internalInit inside the init method of
> the superclass was routed to the subclass one (which then got called again of
> course when the subclass called it), result, badly initialized superclass,
> leaky subclass.
>
> ok in objective-C init just isn't special so I shouldn't have expected it to
> call the local init. Is there a way I could have forced the call to be
> interpreted at the superclass level, or should I change my 'internalInit' to
> 'internalInit<myClassNameHere>' to stop this happening?
> _______________________________________________
>
> Cocoa-dev mailing list ([email protected])
>
> 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/zarzycki%40apple.com
>
> This email sent to [email protected]
_______________________________________________
Cocoa-dev mailing list ([email protected])
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]
