Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121721
Date: Mon, 20 Nov 2023 07:52:36 +0000
To: internals@lists.php.net
User-Agent: K-9 Mail for Android
In-Reply-To: <79d675e3-95b4-40bb-baf4-3e1c998f5390@online-presence.ca>
References: <79d675e3-95b4-40bb-baf4-3e1c998f5390@online-presence.ca>
Message-ID: <B6359F06-6864-4DE8-84CE-2558520E3B18@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC Proposal - static modifier for classes
From: rowan.collins@gmail.com (Rowan Tommins)

On 19 November 2023 21:28:08 GMT, Lanre Waju <lanre@online-presence=2Eca> w=
rote:
>Hi, similar to the abstract and readonly modifiers to classes (similar in=
 syntax only), I propose a class level "static" modifier that ensures:


Hi Lanre,

There was a proposal for this several years ago which was declined at the =
voting stage: https://wiki=2Ephp=2Enet/rfc/abstract_final_class

That doesn't mean we can't look again, but any new proposal would need to =
at least address the reasons the previous one was declined=2E I believe the=
se are the relevant discussion threads: https://externals=2Eio/message/7921=
1 https://externals=2Eio/message/79338 https://externals=2Eio/message/79601

My memory is that one of the main points against was that a class with onl=
y static methods is just a namespace, and you can already put functions dir=
ectly in a namespace=2E The only issue being that we don't have good autolo=
ading support for such functions, and that's a whole different problem=2E=
=2E=2E

Regards,

--=20
Rowan Tommins
[IMSoP]