Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121357
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Wed, 18 Oct 2023 02:31:28 +0900
Message-ID: <AD961CC7-9B27-43DA-9760-2D4C9A3B81F3@sakiot.com>
References: <b8fabda9-cd9f-46a7-a8d6-9de0e30f4910@daniil.it>
Cc: internals@lists.php.net
In-Reply-To: <b8fabda9-cd9f-46a7-a8d6-9de0e30f4910@daniil.it>
To: Daniil Gentili <daniil@daniil.it>
Subject: Re: [PHP-DEV] Final anonymous classes
From: saki@sakiot.com (Saki Takamachi)

Hi, Daniil

> Personally, I would have instead preferred the much cleaner approach of ma=
king *all* anonymous classes final by default, (preferrably) without offerin=
g the option to make them non-final.
>=20
> However, I understand that this might be a little bit too restrictive for s=
omething that may have some valid usecases, even if extending anonymous clas=
ses currently requires some hack-ish workarounds with class_alias.
>=20
>=20
> All in all, as per the title, I'd just like to add support for final anony=
mous classes (new final class {}), without changing any existing semantics.

I think the default can be made final. This is because it is difficult to co=
nsider such complex "hack" operations as "features supported by the language=
." This is even considered a bug of some kind.

If more "realistic" code examples were available, the conclusion would be di=
fferent.

At least, as far as I can currently understand, I don't think there is any n=
eed to consider backward compatibility with such "hacks".

Regards.

Saki=