Re: ADC Core Data article
Re: ADC Core Data article
- Subject: Re: ADC Core Data article
- From: Marcel Weiher <email@hidden>
- Date: Sat, 9 Apr 2005 08:44:02 +0100
On 8 Apr 2005, at 17:34, Charlton Wilbur wrote:
Well, that's the thing -- you don't *know* whether [employee name]
is exposing an instance variable, or making a database call, or
calculating a value. The sensible implementation in most cases is
to expose an instance variable, but that's not required. And the
same thing is true of [employee valueForKey: @"name"].
Yep. But while one clearly indicates that it is asking the object to
respond to the message "name", the other asks an object for the value
for the key "name". While the object may respond to this request by
sending itself the message "name", that is an implementation detail.
It certainly doesn't *look* that way in the code.
The last time we had a similar discussion on object-oriented
orthodoxy, I demonstrated fairly clearly that Objective-C messages
and key-value coding are isomorphic ways of communicating with an
object.
Wow! I must have missed that one. How do I express [matrix
matrixTranslatedBy:2.3 y:[slider floatValue]] in KVC? Or how
about: [[array1 select] isEqual:[array2 each]];
Cheers,
Marcel
_______________________________________________
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