Hi! > (A) The op-code optimization should be integrated into the core compiler > and enabled through a GC(compiler_option) to be available to *any* > opcode cache -- or to the application designer (by exposing these > options through an INI directive.
Most optimizations would not give perceivable benefit unless the optimized code is run many times. So enabling it without opcode cache would not produce very big benefit. But yes, in theory these code parts can live separately and they don't actually need each other. > that support it). A Zend opcode cache belongs firmly in the Zend world > and shouldn't be a PHP extension. I must say I don't understand this conclusion. > I also note some interesting difference in approaches between O+ and > APC, say for example: > > 1) in the handling of the ZEND_INCLUDE_OR_EVAL instruction where APC > patches the op handler and O+ does peephole opcode examination. Both > these workarounds could be avoided by tidying up the scope of work in > the instruction code. Could you explain this a bit more? -- 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
