Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61289
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.170 as permitted sender)
MIME-Version: 1.0
Date: Mon, 16 Jul 2012 14:25:24 +0200
Message-ID: <CAH-PCH738OneYAv-6jNvN5qXN0SzGyOMfxCd=vZ-qAykL_WZ6A@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d042e00f738e36d04c4f18698
Subject: supporting the final keyword for properties
From: tyra3l@gmail.com (Ferenc Kovacs)

--f46d042e00f738e36d04c4f18698
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

The recent http://www.mail-archive.com/internals@lists.php.net/msg59301.htm=
l
discussion
made me wonder why did we decide not supporting the final keywords for
properties as it would provide an easy way for read-only attributes (const
would be a better choice in performance wise, but then you can only set it
in your declaration where no dynamic expression is allowed.)

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 on, 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?

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--f46d042e00f738e36d04c4f18698--