----- Original Message -----
> From: Robert Jacques <[email protected]>
> To: Discuss the phobos library for D <[email protected]>
> Cc:
> Sent: Sunday, April 24, 2011 12:03 PM
> Subject: Re: [phobos] Time to get ready for the next release
>
> On Sun, 24 Apr 2011 07:33:30 -0400, Jacob Carlborg <[email protected]> wrote:
>> If writeln = "foo"; doesn't compile but printf =
> "foo"; does then I would consider it not fixed. The way I would want
> @property to behave is disallow bar = "foo"; for functions not marked
> with @property. But still allow functions not marked with @property to be
> callable without parentheses.
>
> Also, this and another post have given me an idea: what if non-@property
> methods
> could be assigned to if and only if a valid 'getter' also existed. This
> would still 'fix' writeln = "foo" but be a less restrictive
> than an outright ban.
It was an idea that Andrei brought up (before @property syntax was introduced),
but I don't think it can be properly enforced:
int select(int timeout = 0); // both "getter" and "setter"
-Steve
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
