• 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: loop efficiency & messages
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: loop efficiency & messages


  • Subject: Re: loop efficiency & messages
  • From: Daniel DeCovnick <email@hidden>
  • Date: Wed, 23 Mar 2005 12:58:00 -0500

I'd tend to guess it's to make migrating from C++ easier. Can't think of a reason for it otherwise, since -getKey: is used for copying something into a buffer, a la NSData's -getBytes:, and to have both could be confusing. Especially if a class contained both -getKey and getKey:

-Daniel DeCovnick
danhd123 at mac dot com
Softyards Software
http://www.softyards.com/

On Mar 23, 2005, at 12:47 PM, Charilaos Skiadas wrote:

Ok, just looked at the link Mark refered to, so that answers one of my questions. Still, I would like to find out the rationale behind searching for an implementation of getKey first, and key second.

On Mar 23, 2005, at 11:39 AM, Charilaos Skiadas wrote:


On Mar 23, 2005, at 11:25 AM, Sherm Pendley wrote:

On Mar 23, 2005, at 10:33 AM, Charilaos Skiadas wrote:

I think Johnny was actually referring to the fact that KVC comes for free if you have named your accessors for the item as "setItem:" and "item", and he was referring to using the "item" name for the method, instead of the "getItem" name, which KVC would not see automatically.

That's not what the KVC docs say.

<http://developer.apple.com/documentation/Cocoa/Conceptual/ KeyValueCoding/index.html>

From that page, the first step in the search pattern used by -valueForKey: is: "Search the receiver’s class for an accessor method whose name matches the pattern -get<Key>, -<key>, or -is<Key>, in that order."

I should have done my homework first...
In that case, I don't get it. Where in the documentation does it specify that getKey should be used in the manner Charlton described? And why are we encouraged to implement key instead of getKey, but getKey is searched for first?


sherm--

Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org


Haris
Haris

_______________________________________________ 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: 
 >Re: loop efficiency & messages (From: Will Mason <email@hidden>)
 >Re: loop efficiency & messages (From: Charilaos Skiadas <email@hidden>)
 >Re: loop efficiency & messages (From: Sherm Pendley <email@hidden>)
 >Re: loop efficiency & messages (From: Charilaos Skiadas <email@hidden>)
 >Re: loop efficiency & messages (From: Charilaos Skiadas <email@hidden>)

  • Prev by Date: Re: Case insensitive autocomplete
  • Next by Date: Re: loop efficiency & messages
  • Previous by thread: Re: loop efficiency & messages
  • Next by thread: Re: loop efficiency & messages
  • Index(es):
    • Date
    • Thread