Hi!
> which shows the dreaded zend_optimizerplus.inherited_hack which mimics
> APC's autofilter hack. I'd love to get rid of this particular bit of
> confusion/code complexity on the integration.
Ohh, this one. IIRC that has to do with conditional definition of
classes and the fact that script may be compiled in one environment but
loaded in another, which may create difference in class tables,
especially combined with early binding for inherited classes. Getting
rid of it is not that easy until people stop writing code like:
if($foo) return;
class Foo extends Bar {}
which would work differently depending on if Bar is defined or not.
> XDebug together with an opcode cache is always a shaky thing and not
> something we should be too concerned about. You would never want to run
> both in production. It would be good if they didn't clobber each other
> for dev environment purposes, but I am sure we can figure that out.
Yeah, it is a good idea for debugger to turn off any caching when
activated. I think given proper .ini switches it can be easily arranged.
--
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
