Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123769
Message-ID: <eb3f59cc-3ed8-461a-a3a4-f6ba10ed31e1@scriptfusion.com>
Date: Mon, 24 Jun 2024 00:10:23 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: php internals <internals@lists.php.net>
Content-Language: en-GB
Subject: [PHP-DEV] [RFC] Static class
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
From: bilge@scriptfusion.com (Bilge)

Hi Internals!

I am pleased to present my first RFC: Static class 
<https://wiki.php.net/rfc/static_class>.

This work is based on the previous discussion thread on this list of the 
same name, and hopefully captured all the relevant details, 
notwithstanding anything unanticipated that may present itself during 
the implementation. Let me know if you feel anything important has been 
missed. I am aware it omits to mention specifics about messages so 
emitted when runtime or compile-time errors occur, but I anticipate this 
can be hashed out in the PR, unless consensus indicates otherwise.

I am aware this idea is not supported by everyone, but there seemed to 
be enough positive voices for it to be worth a shot. I'd like to get a 
better idea of where people might stand when it comes down to a vote, 
now there is a formal RFC, so we know whether it's worth completing the 
implementation, although any sentiments so proffered are of course not a 
commitment to vote any particular way and nobody should feel compelled 
to speak to that unless comfortable. Looking forward to feedback!

Cheers,
Bilge