Re: Deprecation of func_get_args(), call_user_func_array() and related API
| From: | Rowan Collins | Date: | Mon, 13 Oct 2014 21:25:53 +0000 |
| Subject: | Re: Deprecation of func_get_args(), call_user_func_array() and related API | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-77943@lists.php.net to get a copy of this message | ||
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 likeThe 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]array_mapandarray_filter(and the funny parameter order), because PHP no longer has them under its protective wing.