Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124099
Message-ID: <26091fb5-3783-4099-bc8c-3bdc138e33b3@bastelstu.be>
Date: Sun, 30 Jun 2024 16:31:19 +0200
Precedence: bulk
MIME-Version: 1.0
Subject: Re: [PHP-DEV] [RFC] Static class
To: Bilge <bilge@scriptfusion.com>, Ayesh Karunaratne <ayesh@php.watch>
Cc: php internals <internals@lists.php.net>
References: <eb3f59cc-3ed8-461a-a3a4-f6ba10ed31e1@scriptfusion.com>
 <CANLbj-qvn-BFfN8hEQRciUuT_qCiiPfyqc=YiL1Pw5+Oy-Ad4Q@mail.gmail.com>
 <834e3a0f-19c2-4665-bd8e-c05c61e48231@scriptfusion.com>
Content-Language: en-US
In-Reply-To: <834e3a0f-19c2-4665-bd8e-c05c61e48231@scriptfusion.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

On 6/29/24 17:56, Bilge wrote:
>>    - Why is it a class-level flag and not an attribute (similar to the `#[Override]` attribute in PHP 8.3) ?
> I believe Tim already answered this, and I understood his reasoning to
> be that keywords are used when they modify behaviour in a way that is
> meaningful for the consumer of that class. Or to put it another way,
> attributes are purely informational. For me personally, introducing an

You understood that correctly.

The forward compatibility argument brought forward by the other 
participants is not really useful either, because consider the following:

     #[StaticClass]
     class Foo {
         public static function myFunc() { }
     }

     class Bar extends Foo {
         public function myNonStaticFunc() { }
     }

This would work fine in PHP 8.3, but break when upgrading to PHP 8.4! By 
using a keyword it is guaranteed that the code only runs on PHP versions 
that will reliably enforce all the constraints, preventing this gotcha 
during a PHP version upgrade.

Best regards
Tim Düsterhus