DIP25 draft available for destruction

[Robert]

The solution to this problem has been posted already many times, simply
allow fields to be marked with @property too, having the compiler lower
it to a private field with trivial setter/getter method.

As I already mentioned, I don't really see the point of properties at
all, if they are not interchangeable with fields. We could as well use
setXXX/getXXX as in Java.

On Wed, 2013-02-06 at 22:06 -0800, Walter Bright wrote:
> Properties are always going to be subsets of fields. For example,
> 
>      @property int foo() { return 3; }
> 
> is never going to work with trying to get the address of 3. Trying to
> make it 
> work would be a quixotic quest of dubious utility. I.e. I disagree
> that it is a 
> serious impairment.