On 06/24/2010 12:39 PM, Steve Schveighoffer wrote:
What I'm seeing in the field after faithfully using @property for a
while fits my worst predictions:
1. Code is sprinkled with @property so there's more syntactic noise
to introduce and to deal with;
This is a non-argument. Whatever is decided would certainly have to
be "parsed" whether it was a comment saying "this is a property" or
applying @property.
I forgot to mention: "... more syntactic noise for little benefit to
show for it..."
2. Whenever I define some function I need to make an arbitrary
decision whether that will be a @property or not. Reasonable people
could ask me why I chose whichever way I chose. (Most recent
example: save() for forward ranges.) Arbitrary decisions are bad.
In the same *exact* way, reasonable people can also question how you
name functions
More of a bad thing is worse.
Andrei
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
