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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
