> Am 03.11.2014 um 22:03 schrieb Derick Rethans <der...@php.net>: > > Hi, > > This is based on an email conversation between Joe Watkins and me. I > asked him > what the original scope of phpdbg was, and I've summarized his reply > here: > > - PHPDBG was originally envisioned as a "gdb" for the Zend VM, with gdb > like commands to debug, and step through code. > - Support for breaking on an opline, something that no userland PHP > users would need. > - Support for breaking on lines, was an additional step later. > - For PHP programmers, which spend most of their time at the console. > - Not "intended to cover PHP's primary domain of HTTP requests“.
That was the initial purpose of phpdbg, correct. But now it has outgrown of itself, I think. But also, to begin something, you need concrete goals. In this case that was nice tiny debugger for cli PHP users and devs. Very true. > Then later, they "documented a way that you could use it to emulate an > HTTP request, by setting those superglobals and executing your index.php > - your code doesn't know the difference between a real request, and a > cli-like script with the same super globals set." > > And Joe indicates, that with that addition, the "flood gates opened". He > also said that he "would still like to remain in that narrow scope, > phpdbg is still useful in it's current (pre xml stuff) form." and that > it was never meant to "usurp xdebug", as "that is not where we were > aiming, and it's an extremely unrealistic thing to even want.“ It wasn’t with that addition the "flood gates opened". This addition came alongside with the initial xml protocol development (though in a separate branch), because I thought, if users are going to debug web apps, they most likely will need that. And true, we aren’t trying to usurp xdebug, it was planned to coexist. Nothing like competition, but it was asked that we make it debuggable by an IDE. The xml protocol stuff just was a consequence of that request, to make it possible. > And I very much agree that the above bullet points, is what phpdbg's > scope should be. Also, why do we want an arbitrarily narrowed scope? > Joe, if I got this wrong, then please say so :-) > > cheers, > Derick Regards, Bob -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
