On Wed, Oct 29, 2014 at 12:35 AM, Stas Malyshev <smalys...@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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
