Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106031 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 28866 invoked from network); 22 Jun 2019 18:55:36 -0000 Received: from unknown (HELO mailsrv1.hostingfactory.nl) (185.78.96.68) by pb1.pair.com with SMTP; 22 Jun 2019 18:55:36 -0000 Received: from localhost (localhost [127.0.0.1]) by mailsrv1.hostingfactory.nl (Postfix) with ESMTP id 6A499104298D; Sat, 22 Jun 2019 18:10:48 +0200 (CEST) Received: from mailsrv1.hostingfactory.nl ([127.0.0.1]) by localhost (mailsrv1.hostingfactory.nl [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 2LBWDot8buL9; Sat, 22 Jun 2019 18:10:47 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailsrv1.hostingfactory.nl (Postfix) with ESMTP id 9815810435EA; Sat, 22 Jun 2019 18:10:47 +0200 (CEST) X-Virus-Scanned: amavisd-new at mailsrv1.hostingfactory.nl Received: from mailsrv1.hostingfactory.nl ([127.0.0.1]) by localhost (mailsrv1.hostingfactory.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 41f1qYZShDHv; Sat, 22 Jun 2019 18:10:47 +0200 (CEST) Received: from mailsrv1.hostingfactory.nl (mailsrv1.hostingfactory.nl [185.78.96.68]) by mailsrv1.hostingfactory.nl (Postfix) with ESMTP id 64704104298D; Sat, 22 Jun 2019 18:10:47 +0200 (CEST) Date: Sat, 22 Jun 2019 18:10:47 +0200 (CEST) To: Andrey Andreev Cc: Kalle Sommer Nielsen , internals , nikita ppv Message-ID: <628542280.3156953.1561219847287.JavaMail.zimbra@pieterhordijk.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [185.78.96.68] X-Mailer: Zimbra 8.8.12_GA_3807 (ZimbraWebClient - FF67 (Win)/8.8.12_GA_3794) Thread-Topic: Deprecations for 7.4 Thread-Index: 7cKbKwPQM1UUkQTu1h/YMHfnCpXwSw== Subject: Re: [PHP-DEV] [RFC] Deprecations for 7.4 From: info@pieterhordijk.com (Pieter Hordijk) > Also, it's unclear to me why get_called_class() should be deprecated. > While the rest of the listed deprecations have either motivation > written for them or are self-evidently legacy functionalities that > nobody should be using today, this one seems to be just a case of > "let's not have more than one way of doing things" and I'm not really > a fan of that. I agree with above. When looking through the list of deprecations this one jumps out for me as being an outlier too. Maybe it should just be removed from the RFC? Pieter