Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114889
Date: Tue, 15 Jun 2021 16:46:34 +0200
To: internals@lists.php.net
Message-ID: <20210615164634.5f3c77e7@mcmic-probook.opensides.be>
In-Reply-To: <CAF+90c9MFwjpgmJ97JzmfA57XOdDVCS96P_SoVkBNrLEORVozg@mail.gmail.com>
References: <CAF+90c9crhPpSMcTx-ozGo0LGjNuBU43e8fiK_=PJMU6iTHNmw@mail.gmail.com>
	<CAF+90c9MFwjpgmJ97JzmfA57XOdDVCS96P_SoVkBNrLEORVozg@mail.gmail.com>
Organization: FusionDirectory
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Re: [RFC] Deprecations for PHP 8.1
From: come.chilliet@fusiondirectory.org (=?UTF-8?B?Q8O0bWU=?= Chilliet)

Hello,

Le Tue, 15 Jun 2021 12:53:47 +0200,
Nikita Popov <nikita.ppv@gmail.com> a =C3=A9crit :
> Feedback on the proposed deprecations is appreciated. Personally, the two
> I'm unsure about are "get_class(), get_parent_class() and
> get_called_class() without argument" which are mostly stylistic in nature,
> and "strftime() and gmtstrftime()", where the non-portability issues are
> possibly not so bad that a disruption of existing users is worthwhile.

I use get_called_class() a lot, which is way clearer than static::class as =
the
 name describe what it does.
I think I am not the only one as I find occurences of it in several project=
s I
 have in my vendor/ folder, like rector and codesniffer (not the latest ver=
sion
 through, maybe they changed it).

Forcing people to use static::class will make them have a better
 understanding/instinct of what static:: does, but is that worth forcing a
 change on a working code for something less descriptive, I=E2=80=99m not c=
onvinced.

C=C3=B4me