It shouldn't kill any PECL extensions, most certainly not Xdebug. Ideally I'd like to get Xdebug compatibility for 5.5 - but even if we can't make it - there's truth to the assertion you wouldn't want them both at the same time.
Either way - in the long run O+ and Xdebug will *definitely* work together, and in the short run, you can choose one or the other. Also, I think Rasmus said the combo works for him if he loads O+ first and Xdebug later, so it may not be completely broken at all. Fwiw, the code it takes to have Zend Debugger work alongside O+ isn't very complicated and therefore I'm not at all worried that we'll have a hard time supporting Xdebug. As the RFC states - that may require some minor engine changes. Sent from my tablet On 28 בפבר 2013, at 21:34, Anthony Ferrara <ircmax...@gmail.com> wrote: Zeev, No syntax changes, so regular majority as far as I can tell. However, it does nuke several existing PECL extensions (some fatally). For example, XDebug has no compatibility with ZendOptimizer+ right now (at least that I could find, feel free to correct me if I'm wrong here). And some could argue that shipping with a modification that breaks known and widely relied upon (if only for development) extensions would fit into this category. Since it changes the *functionality* that extensions experience (specifically engine extensions), it should be considered an engine change... The API doesn't change at the syntax level, but the contract definitely does (preconditions, post conditions and invariants)... Anthony
