Re: property name-to-accessor munging? (was: Dot Syntax docs missing?)
Re: property name-to-accessor munging? (was: Dot Syntax docs missing?)
- Subject: Re: property name-to-accessor munging? (was: Dot Syntax docs missing?)
- From: Jean-Daniel Dupas <email@hidden>
- Date: Sun, 20 Jul 2008 16:40:59 +0200
Le 20 juil. 08 à 16:31, Clark Cox a écrit :
On Sun, Jul 20, 2008 at 4:17 AM, Jean-Daniel Dupas
<email@hidden> wrote:
Le 20 juil. 08 à 10:33, Ken Thomases a écrit :
On Jul 18, 2008, at 11:53 PM, Rick Mann wrote:
I realize after all this, it's not really the Dot Syntax I need.
I need
to know how a property name (starts with lower-case letter) is
transliterated into the getter/setter names.
The dot syntax uses the getter and setting specified for the
property in
the @property declaration. As documented[1], if you don't
explicitly supply
getter or setter names in that directive, it defaults to the
property name
for the getter and "set" plus the property name with its first
letter
capitalized plus a trailing colon for the setter.
It also has a special case for boolean where getter may be prefixed
by "is":
enabled => isEnabled / setEnabled:.
This is not true. Each (read/write) property defines one setter and
one getter, there is no special case for BOOL properties. If you want
the getter to be called "isEnabled", you have to specify that:
@property (getter = isEnabled) enabled;
You're right.
I thought that the "name <=> selector mapping" was the same for
properties and for KVC.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden