On Mon, 21 Jun 2010 10:28:10 -0700, Matt Neuburg said: >On the one hand, Apple seems to warn in some documents that one should not >assume KVO-compliance unless explicitly asserted. On the other, KVO is far >more widely implemented in the built-in classes than is explicitly asserted. >Experimentation shows that NSUserDefaults is KVO-compliant, and so are lots >of properties of other objects. > >But how is the user supposed to know this? Or is the user who discovers this >supposed to ignore it?
If it's not documented, I guess it's an implementation detail that you should ignore. :( Though in many cases, it could just be that the docs are out of date. :( -- ____________________________________________________________ Sean McBride, B. Eng s...@rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ 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
