Re: RFC: phpdbg

On Thu, Nov 21, 2013 at 4:15 PM, Michael Wallner <mike@php.net> wrote: > On 21 November 2013 15:54, Joe Watkins <krakjoe@php.net> wrote: >> On 11/21/2013 02:43 PM, Michael Wallner wrote: >>> >>> On 21 November 2013 15:38, Joe Watkins <krakjoe@php.net> wrote: >>>> >>>> On 11/21/2013 02:20 PM, Nikita Popov wrote: >>> >>> >>>>> I'm probably missing some context here, maybe you could explain how >>>>> phpdbg >>>>> differs from something like xdebug? I mean, xdebug seems to be the >>>>> de-facto >>>>> debugging extension for PHP and has been for a long time, but we're not >>>>> bundling it. Why should we bundle phpdbg instead? >>>> >>>> >>>> This is not an extension, it is a SAPI module. The build system >>>> does >>>> not support external SAPI modules, the implementation requires Zend API >>>> which is not exported (or wasn't, has since been patched). >>> >>> >>> That still does not answer the question, though?! >>> >>> >> >> Yes, it does. >> >> xdebug has a reasonable route to deployment already, it, and none of it's >> users, benefit at all from xdebug being bundled. >> >> This is not the same, it can be deployed outside of the source tree but it's >> much harder, for most people, and for some impossible. >> >> I was happy writing code, getting a few functions exported and deploying to >> those people with the ability to build ... >> >> I don't much care for anything but writing the code, and will go back to >> that now ... > > Sorry, I actually only meant the first question: what's the difference > to xdebug? > I don't care yet about bundling, I don't event know what it is. Mabye read http://phpdbg.com/docs/getting-started ? :) As Joe already said, it is a SAPI, it has a debugging console, etc. It is something amazingly handy. Cheers, -- Pierre @pierrejoye | http://www.libgd.org