Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67583
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <06F1F2BA-A054-4B62-AD06-90B621995ADD@strojny.net>
References: <CAH-PCH738OneYAv-6jNvN5qXN0SzGyOMfxCd=vZ-qAykL_WZ6A@mail.gmail.com>
	<CAH-PCH7AUBq3RXTDYFMuf=dGgBRhP=Z0csG=Sjf=A=-O-XWYCA@mail.gmail.com>
	<06F1F2BA-A054-4B62-AD06-90B621995ADD@strojny.net>
Date: Tue, 28 May 2013 11:50:23 +0200
Message-ID: <CAH-PCH5UVS6JY+8qY0KDG5jL4rdW_xf1CjDcjL8+rqyvric7ow@mail.gmail.com>
To: Lars Strojny <lars@strojny.net>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bdc1874ade4ae04ddc431b2
Subject: Re: [PHP-DEV] supporting the final keyword for properties
From: tyra3l@gmail.com (Ferenc Kovacs)

--047d7bdc1874ade4ae04ddc431b2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, May 28, 2013 at 10:58 AM, Lars Strojny <lars@strojny.net> wrote:

> Hi Ferenc,
>
> Am 28.05.2013 um 08:15 schrieb Ferenc Kovacs <tyra3l@gmail.com>:
> [...]
> >> I would like it to work the same way as it does in java(
> >> http://docs.oracle.com/javase/specs/jls/se7/html/jls-4.html#jls-4.12.4=
)
> >> eg. you can set the initial value either in the declaration or later o=
n,
> >> but after it is set, you can't change it, trying to do that would
> create a
> >> recoverable fatal error (or throwing an exception which extends
> >> RuntimeException).
> >>
> >> What do you think? Would this be viable? Is there any still-present
> reason
> >> why we shouldn't support that?
> [...]
> > the accessors rfc got rejected, so I'm bringing this up again.
>
> It=E2=80=99s a good idea in general but what about having it for variable=
s as
> well? Could open interesting possibilities for an optimizer.
>
> final $foo =3D "str";
> $foo =3D "bar"; // bails out
>
> cu,
> Lars


I think that this proposal only makes sense in a class context.
For your example we already have a solution: constants.
Unfortunately class constants has more limitation, as you can't assign
expressions to them, and using global(namespaced) constants which will be
only used in that class breaks the encapsulation part of OOP, as your
constants are "leaking" out.
One solution would be to allow the class consts to accept expressions, but
for that the simple solution would slow down the class constanst for
everybody.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--047d7bdc1874ade4ae04ddc431b2--