No. Hell no. The last thing PHP needs is an ill thought out string of function name changes to further pollute the global name space. Further, merely changing the names isn't going to do anything.
What would help is a massive clean and redo for PHP 8 in the same vein as Actionscript 2 to 3 had a massive cleanup. Namespaces give us the means to do it along with the import keyword - but it would be painful to write the code and I don't think anyone is willing to do it. The strategy would be to put all existing global namespace functions into a new namespace: PHP\Legacy Then add an import keyword. Similar to use, import pulls the designated namespace into the current namespace. Then, for backward compatibility, add a php.ini setting that runs "import PHP\Legacy" at the start of each script. Then create the new functions, separated and organized by namespace. For example. PHP\String\split. And while doing this, decide once and for all whether it's haystack, needle or needle, haystack damn it. On Sun, Nov 5, 2017 at 4:36 PM, Johannes Schlüter <johan...@schlueters.de> wrote: > On So, 2017-11-05 at 14:51 +0100, Peter Kokot wrote: > > Hello all, > > > > correct me if I'm wrong, but wouldn't be a good practice to follow > > the > > currently set coding standards? > > https://github.com/php/php-src/blob/master/CODING_STANDARDS > > > That is good for new code. But breaking 20 years of history for only > that reason is questionable. > > johannes > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
