Re: PHPDBG nonsense (Was: Re: [PHP-CVS] com php-src: Made phpdbg compatible with new engine: ...)
| From: | Julien Pauli | Date: | Wed, 29 Oct 2014 11:55:25 +0000 |
| Subject: | Re: PHPDBG nonsense (Was: Re: [PHP-CVS] com php-src: Made phpdbg compatible with new engine: ...) | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-78443@lists.php.net to get a copy of this message | ||
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