On So, 2017-11-05 at 20:18 -0500, Michael Morris wrote: > Then, for backward compatibility, add a php.ini setting that runs > "import PHP\Legacy" at the start of each script.
We did that mistake with magic_quotes and the ze1 compatibility mode in PHP 5.0. We should learn from that and reduce number of ini settings which have impact on the script behavior, not increase this. This makes, among other things, writing portable code hard (While the environment changed, back in the days shared hosting was a bigger thing, while nowadays with containers users often have more control over their environment) *If* we do something in those areas this should always be that we provide superb options to do stuff in a "clean" (as defined in contemporary understanding) way, which makes the old way obsolete. Introducing a new set of APIs without substantial gain won't get traction (as developers have to relearn, books, tutorials, ... are suddenly outdated, libraries have to make compatibility choices, copy&paste-programming keeps legacy alive, ....) As an example: If we provide a new full set of unicode aware string manipulation, routines these might render byte-based string functions obsolete for many use-cases and offer a gain. (how else could an application handle emojis ... so this is nowadays is even relevant for English-only use cases ... 🤓) Or if we provide an image manipulation framework which supports higher level constructs than pixels and lines ... johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
