• 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: Óscar Morales Vivó <email@hidden>
  • Date: Thu, 28 Jul 2005 17:15:52 -0400

For whatever is worth, I have it filed as bug # 4193300.

But if it's hurting you file it too. The more the merrier. And I guess you could reference my bug number so they can more easily file it as a duplicate (they do keep count of how many people file the same bug to prioritize so your gesture won't have been in vain ;o).

On Jul 28, 2005, at 17:01 , 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! :-)



On Jul 28, 2005, at 4:37 PM, SA Dev wrote:


Ah - I do apologize, I see exactly what you're saying. You have *my* vote for filing an enhancement request. Many other methods specifically say subclasses must call super.


_______________________________________________ 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


_______________________________________________ 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
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 - Newbie] Creating Reports
  • Next by Date: Re: Formatters in IB
  • 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