Hi! > It's not a syntax change, but it is a very, very large engine change. Yes, > it does not touch the Zend engine itself, but it adds a large amount of new > code that is close to the engine. People doing engine changes will need to > modify it too (thus it is quasi part of the engine, even if it lives in a
I'm not sure how it makes sense - people changing the engine had to modify SPL or libxml or SOAP extension, for example - so now SOAP is part of the engine? Since engine is underlying API, if you modify the engine then you may have to modify extensions, doesn't mean all extensions are part of the engine. I find this pretty strained argument. > separate directory). All existing core devs will have to study and > understand the code. All new developers have an additional piece of very > complex code to study before they can start making core changes. Again, by this logic everything is the engine - if you didn't look at how PDO works and changed the engine in a way that broke PDO - it's bad, so by that logic PDO is the engine. And so is pretty much any extension anybody cares about. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
