Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114901
Message-ID: <84082B11-9A6D-4059-A68A-2A2F4B4B497B@newclarity.net>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_FA3F8B14-BE60-46C5-9B4F-DEC8A4B110E8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Date: Tue, 15 Jun 2021 23:59:08 -0400
In-Reply-To: <CAF+90c9MFwjpgmJ97JzmfA57XOdDVCS96P_SoVkBNrLEORVozg@mail.gmail.com>
Cc: PHP internals <internals@lists.php.net>
To: Nikita Popov <nikita.ppv@gmail.com>
References: <CAF+90c9crhPpSMcTx-ozGo0LGjNuBU43e8fiK_=PJMU6iTHNmw@mail.gmail.com>
 <CAF+90c9MFwjpgmJ97JzmfA57XOdDVCS96P_SoVkBNrLEORVozg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Deprecations for PHP 8.1
From: mike@newclarity.net (Mike Schinkel)

--Apple-Mail=_FA3F8B14-BE60-46C5-9B4F-DEC8A4B110E8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> On Jun 15, 2021, at 6:53 AM, Nikita Popov <nikita.ppv@gmail.com> =
wrote:
>=20
> As we're moving closer to feature freeze, I'd like to close down this =
RFC
> to further additions, and move towards voting.
>=20
> 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 just opened one client project and searched and found 52 usages for =
get_called_class(), no usages for the other two.  Just one project.

This was a WordPress project which means many plugins from any different =
developers.

Would deprecating get_called_class() w/o a parameter be important enough =
to cause so much BC breakage?

-Mike=

--Apple-Mail=_FA3F8B14-BE60-46C5-9B4F-DEC8A4B110E8--