Hi Den søn. 3. mar. 2019 kl. 23.24 skrev Ryan Jentzsch <ryan.jentz...@gmail.com>: > > With semantic versioning b/c is allowed. For example version 8.0.0 vs 7.x.x > -- version 8.0.0 could include major breaking changes (since it is a major > version number change). This allows a language to evolve and grow with the > needs of the users. > If PHP is so `rigid` that NO B/C are allowed (regardless of major version > changes) then PHP is overtly rigid and I predict it will ultimately become > extinct.
One very important factor for breaking BC in PHP is also the gain if you are changing something so centric as the basic output constructs. I don't see changing echo/print to include a new line would ever pass due to this, however I could see (and possibly vote yes) to a new construct that did the exact same with a new line afterwards. These however are matters which should, by our process, be discussed through RFCs that weights pros/cons and the overall impact and demand. Like Johannes said; there haven't been a high enough demand for anyone to have voiced their opinion strongly, or at least not the 11 years I have been contributing myself or the two years I was an internals reader before that, that I can remember. I suggest the OP to start such a process, which can be done by registering a user on our wiki and following the instructions for write access to the RFC namespace. -- regards, Kalle Sommer Nielsen ka...@php.net -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
