Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97954
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.174 as permitted sender)
To: Scott Arciszewski <scott@paragonie.com>,
 PHP Internals <internals@lists.php.net>
References: <CAKws9z1fAX+YBDO4Z15eaiZsUZvuNbigHaWYwvMijFxT-QsGAA@mail.gmail.com>
 <c766b4f4-5fde-abbc-65f9-9cfdec2a0b16@gmail.com>
Message-ID: <4c58f6af-13df-d1a9-5988-55bd618b1853@gmail.com>
Date: Wed, 25 Jan 2017 00:14:11 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
 Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <c766b4f4-5fde-abbc-65f9-9cfdec2a0b16@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Class Constant Finalization
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

>> Given that we can now declare a class constant as public, protected, or
>> private, can we also declare them final in 7.2?
> 
> That doesn't make much sense to me. Constant belongs to a class. I don't
> see much utility in "no class extending from this one can define
> constant with the same name". final makes sense when the alternative is
> override, and you want to exclude it. But since there's no override
> here, no point to exclude anything.

Adding to this, you kind of can simulate it with static::, as Nikita
described, but if you go as far, you probably know what you're doing and
then you should be allowed to do it. Not that I see much point in doing
it, but if you want to...

-- 
Stas Malyshev
smalyshev@gmail.com