Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78427
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.216 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
In-Reply-To: <544F4321.8040302@seld.be>
Date: Tue, 28 Oct 2014 14:08:10 +0000
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <E87E48F1-5D79-4C6A-9368-C0A3CA35501F@ajf.me>
References: <6E04B9BE-854E-4112-8C74-7D90BD8BFE95@ajf.me> <544D48A3.6070905@gmail.com> <572FEBD1-99A8-4788-83F9-D99E470FB16D@ajf.me> <544F4321.8040302@seld.be>
To: Jordi Boggiano <j.boggiano@seld.be>
Subject: Re: [PHP-DEV] [RFC] Readonly Properties
From: ajf@ajf.me (Andrea Faulds)


> On 28 Oct 2014, at 07:17, Jordi Boggiano <j.boggiano@seld.be> wrote:
>=20
> 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=E2=80=99t make sense to =
have a getter and no setter and yet expect a property to be writeable.

> How about this instead for readonly:
>=20
>      public $foobar {
>          get { return $this->bar * $this->foo; }; readonly
>      }
>=20
> And if the flag isn't there, set is implicitly present.

This is really confusing and I don=E2=80=99t think it=E2=80=99s a good =
idea.=20
--
Andrea Faulds
http://ajf.me/