Accessors, byLine, input ranges

[Steven Schveighoffer]

On Fri, 29 Jan 2010 11:17:04 -0500, Andrei Alexandrescu  
<SeeWebsiteForEmail at erdani.org> wrote:

> Steven Schveighoffer wrote:
>> On Fri, 29 Jan 2010 10:40:23 -0500, Andrei Alexandrescu  
>> <SeeWebsiteForEmail at erdani.org> wrote:
>>
>>> Michel Fortin wrote:
>>>> On 2010-01-29 08:18:46 -0500, "Steven Schveighoffer"  
>>>> <schveiguy at yahoo.com> said:
>>>>
>>>>> Hey, it's that dead horse again, let's beat it!
>>>>>
>>>>> Andrei and I and several others discussed this ad infinitum.  You  
>>>>> will  never convince Andrei that his design is wrong :)
>>>>  Andrei is the one who complained that it's difficult to know whether  
>>>> 'byLine' is a property in the first place. I'm just explaining why it  
>>>> is, and what should be done.
>>>>  I'm starting to think Anrei likes ambiguous semantics.  :-)
>>>
>>> I'll tell you what I'd have liked: a landslide of responses to my  
>>> question revealing my mistaken ways and clarifying without a shade of  
>>> a doubt that byLine should be a @property. Or not. (I don't even care  
>>> which.)
>>  It's been mentioned before that tough decisions need to be made in  
>> many areas of programming.  Deciding what is a property and what is not  
>> is no different.
>
> Except it has no reward associated with it.

Clarity.  Disambiguation.  All the rewards that come from other naming  
conventions.  Sorry you don't see it that way.

-Steve