Stas, Just to put things in perspective, if opcode caches with extended info make it into the opcode cache - it's a bad thing. So it's actually expected that debuggers and opcode caches would have to be aware of one another, but at a pretty minimal level. The load order solves it most probably because then it means Xdebug kicks in first, and wouldn't pass op arrays to O+. That's guesswork though, we'd have to ensure that and ideally also have a mechanism to enforce it.
Sent from my tablet On 28 בפבר 2013, at 22:49, Stas Malyshev <smalys...@sugarcrm.com> wrote: > Hi! > >> It works fine. You just have to load ZO before xdebug. If you load it >> the other way around bad things happen. This wrong load order currently > > Could you describe the bad things? Maybe we could have some checks in > either of them to prevent it... Of course, we could probably make ZO > just check if xdebug is loaded and react accordingly, but maybe we could > resolve it in a more elegant way... > > -- > 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
