Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78416
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <544F4321.8040302@seld.be>
References: <6E04B9BE-854E-4112-8C74-7D90BD8BFE95@ajf.me>
	<544D48A3.6070905@gmail.com>
	<572FEBD1-99A8-4788-83F9-D99E470FB16D@ajf.me>
	<544F4321.8040302@seld.be>
Date: Tue, 28 Oct 2014 14:23:06 +0700
Message-ID: <CAEZPtU57PvEnHokYikMuYYnJVs=1GhLfQmiUh=eAhQT77644tA@mail.gmail.com>
To: Jordi Boggiano <j.boggiano@seld.be>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Readonly Properties
From: pierre.php@gmail.com (Pierre Joye)

On Tue, Oct 28, 2014 at 2:17 PM, Jordi Boggiano <j.boggiano@seld.be> wrote:
> On 27/10/2014 20:27, Andrea Faulds wrote:
>>
>> Tentative syntax. But this way, the visibility stays on the left. I thin=
k
>> that=E2=80=99s good for readability. If you omit the second specifier, t=
hen the
>> first one applies to getting and setting, as now. If you include it, the
>> first one applies to getting, the second one to setting.
>>
>> It=E2=80=99d also be compatible with properties, too:
>>
>>      public/private $foobar {
>>          get { return $this->bar * $this->foo; }
>>          set($value) { $this->bar =3D $value / $this->foo; }
>>      }
>>
>> It doesn=E2=80=99t prevent truly read-only properties, either:
>>
>>      public $foobar {
>>          get { return $this->bar * $this->foo; }
>>      }
>>
>> Does this sound like a good idea? A similar idea came up in the
>> discussions 8 years ago on readonly.
>
>
> I like it, except for the fact that if you add a custom getter to a prope=
rty
> suddenly it becomes readonly unless you remember to add "; set" to the en=
d
> of the block, right?
>
> 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.
>
> That'd mean you also can keep "public readonly $foobar;" as a shorthand f=
or
> readonly properties without custom getter.

I like this idea.

Also confirmed what I was trying to say: While we can have many RFCs
covering the properties properties and behavior, having one covering
the needs in one go will allow us to be more consistent and developer
friendly.


--=20
Pierre

@pierrejoye | http://www.libgd.org