Paul M. Jones <pmjo...@pmjones.io> wrote: > Are there any members here who currently expect to vote "no",
The only reason for doing this as C code appears to be make it have read-only properties. This is a hack that would confuse a lot of developers, and instantly be added to most lists of "how PHP is bad". I really think this doesn't belong in core PHP. Tying this into core means that: - BC breaking changes could only happen on major versions. - Discussion of those changes would take up a lot of time, or more likely never happen. See all of our core extensions that are desperately in need of a maintainer to work on them. - It might be impossible (or at least annoyingly difficult) to write code that was compatible with two versions of PHP, if they used this object. As you were involved and so know, a huge amount of energy was spent designing PSR-7, and still it was definitely not a perfect design. The chances of the design of this API being even as close as PSR-7 was, seems minimal. Which means that we would be likely to regret bringing it into core. For stuff to be added to core, to overcome the burden of supporting in the future, there needs to be a strong reason to add it. Not just something that could be done. In case anyone is interested, there is a book called 'Systemantics' that's actually quite applicable to open source projects....despite being written before personal computers were really a thing: https://en.wikipedia.org/wiki/Systemantics#First_principles https://www.amazon.co.uk/Systems-Bible-Beginners-Guide-Large/dp/0961825170/ref cheers Dan Ack -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
