• 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: Bindings clarification: +setKeys:triggerChangeNotificationsForDependentKey: doesn't affect subclasses?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bindings clarification: +setKeys:triggerChangeNotificationsForDependentKey: doesn't affect subclasses?


  • Subject: Re: Bindings clarification: +setKeys:triggerChangeNotificationsForDependentKey: doesn't affect subclasses?
  • From: Jim Hamilton <email@hidden>
  • Date: Thu, 28 Jul 2005 19:13:43 -0400


On Jul 28, 2005, at 5:01 PM, SA Dev wrote:

As Jim pointed out off-list, the docs state that subclasses specifically should *not* call super's +initialize. This is indeed strange. So does this mean that subclasses of NSObject shouldn't call super or *any* subclasses shouldn't call super? If the former, then any good documentation on someone's class should say whether or not super +initialize should be called which implies it's up to you to read it. If that's the case, then a disambiguation should be posted in the docs.

This one now has me stumped too (I haven't run into it myself and many of my classes register dependent keys). Thanks for the puzzle, Jim! :-)


Here's the answer:

<http://developer.apple.com/documentation/Cocoa/Reference/Foundation/ ObjC_classic/Classes/NSObject.html#//apple_ref/doc/uid/20000050- initialize>

Jim H
--
Jim Hamilton

email@hidden
email@hidden

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Bindings clarification: +setKeys:triggerChangeNotificationsForDependentKey: doesn't affect subclasses?
      • From: Jim Correia <email@hidden>
References: 
 >Bindings clarification: +setKeys:triggerChangeNotificationsForDependentKey: doesn't affect subclasses? (From: Jim Correia <email@hidden>)
 >Re: Bindings clarification: +setKeys:triggerChangeNotificationsForDependentKey: doesn't affect subclasses? (From: SA Dev <email@hidden>)
 >Re: Bindings clarification: +setKeys:triggerChangeNotificationsForDependentKey: doesn't affect subclasses? (From: Jim Correia <email@hidden>)
 >Re: Bindings clarification: +setKeys:triggerChangeNotificationsForDependentKey: doesn't affect subclasses? (From: SA Dev <email@hidden>)
 >Re: Bindings clarification: +setKeys:triggerChangeNotificationsForDependentKey: doesn't affect subclasses? (From: SA Dev <email@hidden>)

  • Prev by Date: Re: Core Data performance (was: Newbie Help understanding Core Data)
  • Next by Date: Using Bindings for an Inspector
  • Previous by thread: Re: Bindings clarification: +setKeys:triggerChangeNotificationsForDependentKey: doesn't affect subclasses?
  • Next by thread: Re: Bindings clarification: +setKeys:triggerChangeNotificationsForDependentKey: doesn't affect subclasses?
  • Index(es):
    • Date
    • Thread