> On 28 Oct 2014, at 07:17, Jordi Boggiano <[email protected]> wrote:
>
> I like it, except for the fact that if you add a custom getter to a property
> suddenly it becomes readonly unless you remember to add "; set" to the end of
> the block, right?
Well, no. If you choose to specify getters and setters, and only specify a
setter, of course it is read-only. It doesn’t make sense to have a getter and
no setter and yet expect a property to be writeable.
> How about this instead for readonly:
>
> public $foobar {
> get { return $this->bar * $this->foo; }; readonly
> }
>
> And if the flag isn't there, set is implicitly present.
This is really confusing and I don’t think it’s a good idea.
--
Andrea Faulds
http://ajf.me/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
