Re: PHPDBG nonsense (Was: Re: [PHP-CVS] com php-src: Made phpdbg compatible with new engine: ...)

From: Date: Tue, 28 Oct 2014 14:18:17 +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 9  Groups: php.internals 
Request: Send a blank email to internals+get-78429@lists.php.net to get a copy of this message
On Sun, Oct 26, 2014 at 8:11 AM, Sebastian Bergmann <sebastian@php.net> wrote: > Am 25.10.2014 um 20:20 schrieb Stas Malyshev: > > somewhat relaxed rules there, but even then introducing new debugging > > protocol into PHP core seems to be something that warrants some > > notification. > > That would have been my next question. I think it does not only > warrant notification but adherence to the RFC process. > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > As far as I can tell there are a couple of SAPIs(to be honest everything except cli/cgi/fpm/embed and apache*) and even some exts(like mysql*, pgsql, date, pcre, etc.) where there are dedicated maintainers who seemingly can introduce new features without discussing it on the list or following through the rfc process. I'm not saying that this is a bad thing(on the contrary, I think that most of the times this happens because the maintainer is the best suited for making those decisions), but I think it would be nice if we could clarify that what exact procedures do we want to be followed for exts/SAPIs inside the php-src tree. -- Ferenc Kovács @Tyr43l - http://tyrael.hu

« previous php.internals (#78429) next »