Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78443
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.52 as permitted sender)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
In-Reply-To: <5450284B.1060601@gmail.com>
References: <php-mail-d1dee1060d0e519b421e241f31037078549681831@git.php.net>
 <alpine.DEB.2.11.1410242103530.4012@whisky.home.derickrethans.nl>
 <1414217636.2624.89.camel@localhost.localdomain> <alpine.DEB.2.11.1410261047380.4012@whisky.home.derickrethans.nl>
 <BLU436-SMTP249111049DD6549BD1ABC5DE2910@phx.gbl> <slrnm4t05a.775.dsp@dsp.local>
 <CAMUwpuTCO3zb6ijttTudiF-CqL=3TOQ2O_ssHKUB-1iAe7HBYA@mail.gmail.com> <5450284B.1060601@gmail.com>
Date: Wed, 29 Oct 2014 12:55:25 +0100
Message-ID: <CAMUwpuQJn6KkYVQiu-O5PTsyF0dd6YnSxsZYGJj+qx2uR5HMBQ@mail.gmail.com>
To: Stas Malyshev <smalyshev@gmail.com>
Cc: David Soria Parra <dsp@php.net>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] PHPDBG nonsense (Was: Re: [PHP-CVS] com php-src: Made
 phpdbg compatible with new engine: ...)
From: jpauli@php.net (Julien Pauli)

On Wed, Oct 29, 2014 at 12:35 AM, Stas Malyshev <smalyshev@gmail.com> wrote:
> Hi!
>
>> phpdbg is under php.net ; every decision about phpdbg should then be
>> debatted with all the team, and new ideas, such as a protocol, RFC'ed,
>> whoever are the maintainers of the code. It's like that for every
>> piece of code, of every extension. This is PHP process. If you dont
>> want to
> Do I understand it right that after all we've being discussing here
> about not putting big new stuff into PHP without discussion, we've got
> new stuff in phpdbg now merged not only to master but into the stable
> branch of 5.6? Am I missing something here?

If you are talking about the phpdbg new debugging protocol : this is right.

I think it clearly lacks discussion, RFC, concensus here, particularly
regarding the choice of the protocol.

We must absolutely use something open and efficient.
Using a closed protocol, that only one editor would be able to
implement ; is just a no-go ; for example.


Julien.P