Re: Setters, Getters and efficiency
Re: Setters, Getters and efficiency
- Subject: Re: Setters, Getters and efficiency
- From: Jeff LaMarche <email@hidden>
- Date: Sun, 11 Dec 2005 15:07:05 -0500
On Dec 11, 2005, at 1:39 PM, mmalcolm crawford wrote:
This is not the case. The access pattern for key-value coding is
the same regardless of the class -- accessor methods are always
tried first (for the search order, see <http://developer.apple.com/
documentation/Cocoa/Conceptual/KeyValueCoding/Concepts/
SearchImplementation.html>; for NSManagedObject, see <http://
developer.apple.com/documentation/Cocoa/Reference/CoreData_ObjC/
Classes/NSManagedObject.html#//apple_ref/occ/instm/NSManagedObject/
setValue:forKey:>).
Isn't storedValueForKey: used instead of valueForKey: when accessing
attributes of an NSManagedObject (i.e when getting data from Core
Data)? The link you sent me to was the one I had just read before
composing my e-mail, and it states that the order that is used for
storedValueForKey is similar, but not identical to valueForKey:, in
that it prefers direct access to instance variables over accessors
unlike valueForKey, which prefers accessors. Did I misunderstand, or
simply misstate?
_______________________________________________
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