Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61297
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAH-PCH738OneYAv-6jNvN5qXN0SzGyOMfxCd=vZ-qAykL_WZ6A@mail.gmail.com>
References: <CAH-PCH738OneYAv-6jNvN5qXN0SzGyOMfxCd=vZ-qAykL_WZ6A@mail.gmail.com>
Date: Mon, 16 Jul 2012 15:42:19 +0200
Message-ID: <CAEZPtU5y-psp11wUM-hPtUPyjNo7wYCjnHCraTPBET4yc-sL+w@mail.gmail.com>
To: Ferenc Kovacs <tyra3l@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] supporting the final keyword for properties
From: pierre.php@gmail.com (Pierre Joye)

hi,

On Mon, Jul 16, 2012 at 2:25 PM, Ferenc Kovacs <tyra3l@gmail.com> wrote:

> The recent http://www.mail-archive.com/internals@lists.php.net/msg59301.html
> 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.)

Final and readonly are too totally different concepts.

Read only properties can be implemented by doing something using the
nice getter/setter RFC
(https://wiki.php.net/rfc/propertygetsetsyntax-as-implemented).


Cheers,
-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org