Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118061
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
In-Reply-To: <CAH19jWitAAqEdBrqX3ZjGnw+Nfd_8C=qzqPyxnOM13EtgZhBvA@mail.gmail.com>
Date: Wed, 22 Jun 2022 20:12:14 +0200
Cc: internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <2FB748CF-A93A-4F1F-BA8B-22D100A472D7@gmail.com>
References: <CAH19jWitAAqEdBrqX3ZjGnw+Nfd_8C=qzqPyxnOM13EtgZhBvA@mail.gmail.com>
To: shinji igarashi <sji@sj-i.dev>
Subject: Re: [PHP-DEV] [RFC] [Under Discussion] Constants in traits
From: claude.pache@gmail.com (Claude Pache)



> Le 21 juin 2022 =C3=A0 23:33, shinji igarashi <sji@sj-i.dev> a =C3=A9cri=
t :
>=20
> Hello everyone!
>=20
> I'd like to start a discussion on an RFC to allow defining constants =
in traits.
> https://wiki.php.net/rfc/constants_in_traits
>=20
> I'm looking forward to your feedback, including corrections on English =
wordings.
>=20
> Thanks!
>=20
> --
> Shinji Igarashi
>=20


Hi,

Some time ago, I migrated part of some class implementation into a =
trait, and I was surprised that it resulted in a syntax error, because =
constants were not supported in traits. In my case, I could trivially =
resolve the issue by morphing the (private) constant into a static =
property (semantically less correct, but pragmatically simpler); but I =
was feeling that it is yet one more inconsistency of PHP: Why on earth =
are static properties supported, but not constants?

So, this is a welcome addition (or, rather, a welcome correction of an =
oversight).

=E2=80=94Claude