On 03/07/2013 09:01 AM, Anthony Ferrara wrote: > So my proposal is to slow down for a minute and not call this RFC > accepted or not until we can come to some consensus as to if it > classifies as a language change or not... Better to clarify for the > health of the project than to plow through and risk causing further > strife...
And how do you propose we do that? Vote on it? Will that vote need 2/3 as well? I think most of us accepted that language-level changes meant syntax changes. Things that add new features to the language itself. For example, interned strings in 5.4 was a major change as well and it broke a bunch of things. I don't think we even bothered with an RFC for it much less a vote since it was a really worthwhile performance improvement which didn't affect the language at all other than the fact that it broke a bunch of things, but once we worked out the bugs and opcode caches eventually figured out how to support it, it became invisible to the user. I don't see how adding an opcode cache is any different. In fact adding this opcode cache will have less of an effect than interned strings did since it doesn't touch the internals of the engine anywhere near as much. -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
