Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103909
To: Peter Kokot <peterkokot@gmail.com>,
 Rowan Collins <rowan.collins@gmail.com>
Cc: Internals <internals@lists.php.net>
References: <CAFPFaM+cEa2xFDqvkLQk=Qht3KdcGUCBaCj6JcuQxqLmjnf9Pw@mail.gmail.com>
 <0243D3A4-2C15-4B31-81A8-C2E5892913F9@koalephant.com>
 <CAFPFaM+9fWQL+oyfwAKAyjohWHO47W=ibzNmpuM9qVA+6JMjig@mail.gmail.com>
 <CAFLRTJ_SmnAT2QaHqinjAQYJBiS2_LfpB47Ph-=K=8FsB+0xXw@mail.gmail.com>
 <2d8efb96-ed1f-28e4-e0fe-603a2d0f1962@gmail.com>
 <CAAfnsFVaVAAJ4Q3fCvNVABw3d5Ze9BB6+RcQqZmdcPxbRzSi0w@mail.gmail.com>
 <cf338b9b-64cf-efb9-9e9e-7e97c767ff9d@gmail.com>
 <CAAfnsFUtopcyprU+o23sCssKF+tpTD=n0zA6x0ewg7J3TKEosA@mail.gmail.com>
Message-ID: <41751cdc-8d15-591d-fd3a-996e07fff453@gmx.de>
Date: Thu, 31 Jan 2019 12:11:11 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <CAAfnsFUtopcyprU+o23sCssKF+tpTD=n0zA6x0ewg7J3TKEosA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Deprecation ideas for PHP 8
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 31.01.2019 at 08:34, Peter Kokot wrote:

> The RFC: Consistent function names [1] shows the magnitude of this. I
> don't think every function listed there needs a change so it can be
> greatly reduced. But still this can be done in several years to 10
> years or so (measuring over the thumb).
> 
> Not that it is not possible to do this, but too many people promote
> this state as not possible to change. I didn't put too much effort to
> make a list of all the changes to an extend as is nicely done in the
> RFC but maybe enough would be renaming functions and alias them
> properly from major/minor release version to version and furthermore
> deprecate the aliases, so they match the pattern suggested for PHP
> vanilla functions [2]. Not to mention really good ideas from the past
> discussions with namespacing functions and similar approaches...
> 
> But, yes... Without proper will or motivation from key people who
> could change this it will stay in the inconsistent state and we all
> accept it as is. Specially in discussions about a major release where
> BC could be done.
> 
> [1] https://wiki.php.net/rfc/consistent_function_names
> [2] https://github.com/php/php-src/blob/master/CODING_STANDARDS

In my opinion, there is no gain in renaming bcadd() to bc_add(), for
instance.  A namespaced variant BC\add() might be an improvement, but
likely it should rather be BCNumber::plus() (also overloading the +
operator).  See also the closely related discussion regarding renaming
the image functions: <https://externals.io/message/101050>.

-- 
Christoph M. Becker