@property - take it behind the woodshed and shoot it?

[mist]

On Thursday, 24 January 2013 at 20:44:33 UTC, eles wrote:
> On Thursday, 24 January 2013 at 20:26:50 UTC, mist wrote:
>> On Thursday, 24 January 2013 at 20:20:42 UTC, Adam Wilson 
>> wrote:
>
> I think the widest spread use case of a property is:
>
> you start with a variable as memeber of a class, you write a lot
> of assignment code, then you decide that you need to do some 
> more
> extensive processing instead of simple assignment, and all that
> without breaking existing code.
>
> so, you transform the variable into a property.
>
> of course, it could happen the other way around (converting a
> function into a property/variable).

It is a wrong use case for a property. Necessity to change data 
assignment/access to call of function with side-effect is design 
error and should be fixed with programmers experience, not 
property hacks.