Hi! >> The lexing and parsing processes will not be slower than actual, and the > construction of an AST is a new process. Well, as usual, new process > requires new resources. But if we look further, it will certainly be a nice > tool to perform better opcode caching, it will remove a lot of hacks, it > will allow third-part tools working on safeness, security, quality etc. to > go deeper at low-costs which is very important for PHP community, it will > facilitate future works
I don't see how it would lead to better opcode caching. As for third-party tools, I do not see why third-party tools need PHP to change the parser. If PHP's parser is not good enough for those tools, they can have their own parser. > Maybe the upfront cost of a parse goes up, but once it is parsed and the > opcodes are cached, you won't have this cost again until you change the > script. Then you have all of the benefits for every subsequent request. So far we have not seen not only any of these benefits, but any explanation of what exactly these benefits would be and any proof they would actually benefit anybody. I seriously would propose people interested in this project just take up this project and see if it's beneficial or not. Just talking about what might happen on the list would achieve nothing. > Increased cost once, benefits every time. For now it looks like quite the reverse - increased performance and stability costs for everybody, dubious benefits for a small group. -- 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
