On So, 2019-03-03 at 05:53 -0800, Steven Penny wrote: > On Sun, 03 Mar 2019 06:49:25, Joe Watkins wrote: > > > > Jokes aside, this is so trivially achievable in userland that there > > is no > > justification whatever for an internal function or functions, or > > constructs, or opcodes. > if thats the case we better go ahead and remove these in favor of > "base_convert": > > - bindec > - decbin > - dechex > - decoct > - hexdec > - octdec > > as they are so trivially achievable in userland that there is no > justification > whatever for an internal function or functions, or constructs, or > opcodes.
There is a difference between adding and removing features. Also there is development and learnings from the past. In the past we added more or less any function. Over time this lead to different issues (like breaking user code, always having request for new variants, inconsistencies, ...) so we got more restrictive over time. Also PHP got faster, which allows more functions without notable overhead to be written in PHP instead of part of the implementation. This has the benefit that more people can write and maintain those, as well debugging is simpler. Also the environment improved. Things like composer and packagist as well as improved autoloading allow simpler distribution and usage of userspace libraries. Sometimes we might add some small helper routines, but that's a cost/benefit analysis and since the "auto new line" hasn't been requested often (I can't remember any such request from last 15+ years, doesn't man there was, but certainly not recurring) this doesn't seem to be a thing PHP users miss a lot. johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
