Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97951
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.49 as permitted sender)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAKws9z1fAX+YBDO4Z15eaiZsUZvuNbigHaWYwvMijFxT-QsGAA@mail.gmail.com>
Date: Wed, 25 Jan 2017 10:30:06 +0300
Cc: PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <7B68DE87-4622-4209-A0B6-6AFDFBC3AC38@gmail.com>
References: <CAKws9z1fAX+YBDO4Z15eaiZsUZvuNbigHaWYwvMijFxT-QsGAA@mail.gmail.com>
To: Scott Arciszewski <scott@paragonie.com>
Subject: Re: [PHP-DEV] Class Constant Finalization
From: inefedor@gmail.com (Nikita Nefedov)



> On 25 Jan 2017, at 09:48, Scott Arciszewski <scott@paragonie.com> wrote:
>=20
> All,
>=20
> Given that we can now declare a class constant as public, protected, or
> private, can we also declare them final in 7.2?
>=20
> https://3v4l.org/rJG0V
>=20
> Ideally, this code would error on line 18 rather than 15.
>=20
> Scott Arciszewski
> Chief Development Officer
> Paragon Initiative Enterprises <https://paragonie.com>

In my book, ideally, there would be no class constant inheritance as inherit=
ed constants don't really make sense when they are known at compile time. Pe=
ople often use this feature in order to get things like this to work:

    class LibLevelClass {
        const FOO =3D "default";
        public function doSomething() {
            echo "the value of FOO is: " . static::FOO;
        }
    }

    class ExtensionClass {
        const FOO =3D "custom";
    }

But this approach is error prone due to untyped nature of constants (one cou=
ld override the constant with an array value). In the end this inheritance i=
s always unnecessary.