Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70263
Return-Path: <krakjoe@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 46504 invoked from network); 21 Nov 2013 14:54:31 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 21 Nov 2013 14:54:31 -0000
X-Host-Fingerprint: 80.4.21.210 cpc22-asfd3-2-0-cust209.1-2.cable.virginm.net  
Received: from [80.4.21.210] ([80.4.21.210:29165] helo=localhost.localdomain)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 23/E1-36839-6AE1E825 for <mike@php.net>; Thu, 21 Nov 2013 09:54:31 -0500
To: internals@lists.php.net,Michael Wallner <mike@php.net>
Message-ID: <528E1EA3.9090906@php.net>
Date: Thu, 21 Nov 2013 14:54:27 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
References: <4E.7B.51208.63ACD825@pb1.pair.com> <CAF+90c895QCHqqdfCOjB0KXf9HYm9K90RjUv=-K7=t5kW=__iA@mail.gmail.com> <528E1AF6.9050201@php.net> <CALJZF3gWqkm1=cpEVKbhRfMSar6DT51tAgmrq3Kg7kAfB8ySRg@mail.gmail.com>
In-Reply-To: <CALJZF3gWqkm1=cpEVKbhRfMSar6DT51tAgmrq3Kg7kAfB8ySRg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Posted-By: 80.4.21.210
Subject: Re: [PHP-DEV] RFC: phpdbg
From: krakjoe@php.net (Joe Watkins)

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 ...