Re: RFC: phpdbg
| From: | Joe Watkins | Date: | Thu, 21 Nov 2013 14:54:27 +0000 |
| Subject: | Re: RFC: phpdbg | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-70263@lists.php.net to get a copy of this message | ||
On 11/21/2013 02:43 PM, Michael Wallner wrote:
On 21 November 2013 15:38, Joe Watkins <krakjoe@php.net> wrote: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 ...On 11/21/2013 02:20 PM, Nikita Popov wrote:That still does not answer the question, though?!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 doesnot support external SAPI modules, the implementation requires Zend API which is not exported (or wasn't, has since been patched).