• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Designated Initializer
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Designated Initializer


  • Subject: Re: Designated Initializer
  • From: mmalc Crawford <email@hidden>
  • Date: Sat, 30 Oct 2010 13:27:09 -0700

On Oct 30, 2010, at 12:12 pm, Dave Carrigan wrote:

> All initialized objects have at some point called super; they aren't fully initialized otherwise. In the implementation, the non-designated initializers typically chain to the designated initializer, which in turn chains to super's (usually designated) initializer. So just because a designated initializer didn't call super's designated initializer, it doesn't mean that super's designated initialer was not invoked; it was.
>
This is not the case.
You should always invoke super's designated initialiser ("or another [initializer] that ultimately invokes the designated initializer"):
	<http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/ObjectiveC/Articles/ocAllocInit.html#//apple_ref/doc/uid/TP30001163-CH22-SW1>

mmalc

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

References: 
 >Designated Initializer (From: Richard Somers <email@hidden>)
 >Re: Designated Initializer (From: Dave Carrigan <email@hidden>)

  • Prev by Date: Re: Designated Initializer
  • Next by Date: Re: Designated Initializer
  • Previous by thread: Re: Designated Initializer
  • Next by thread: Re: Designated Initializer
  • Index(es):
    • Date
    • Thread