On 13/10/2014 21:34, Marco Pivetta wrote:
The problem always existed, and it's that it is very hard to escape from an API that is dictated by the language itself. Getting gradually rid of those APIs and making them swappable pieces simply increases the degree of freedom that we get in our applications, by having less people rely on stuff like `array_map` and `array_filter` (and the funny parameter order), because PHP no longer has them under its protective wing.
The existence of a highly performant, well tested, well documented implementation of array_map in every copy of PHP is definitely a good thing - it frees the programmer to think about their actual problem, rather than such nuts and bolts. If it wasn't in the language, it would be in standard frameworks, and a design mistake in those frameworks over argument order would have created the same backwards compatibility lock-in that we have today.
It may be that there are pieces of low-level functionality which could be *added*, to make it easier to implement interesting tools for special occasions; in that case, the conversation should not be about removing existing tools which people are happily using.
-- Rowan Collins [IMSoP] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
