Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78607
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.107 as permitted sender)
Message-ID: <545829C5.7080409@sugarcrm.com>
Date: Mon, 03 Nov 2014 17:20:05 -0800
Organization: SugarCRM
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Derick Rethans <derick@php.net>, 
 PHP Developers Mailing List <internals@lists.php.net>
References: <alpine.DEB.2.11.1411031940310.13538@whisky.home.derickrethans.nl>
In-Reply-To: <alpine.DEB.2.11.1411031940310.13538@whisky.home.derickrethans.nl>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHPDBG scope
From: smalyshev@sugarcrm.com (Stas Malyshev)

Hi!

> - PHPDBG was originally envisioned as a "gdb" for the Zend VM, with gdb
>   like commands to debug, and step through code.

That was also my impression when the RFC was discussed.
Now, I do not object in principle on growing the scope of phpdbg. But
this needs to be done the right way if it's the php.net core part -
having an RFC that explains what exactly happens and why, getting
consensus, and only then merging.

> 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."

I don't think this as such is a bad idea, I wouldn't mind having such
thing available, I can see use cases where it would be handy.

So I think it would be useful to have some ordered RFC describing where
phpdbg wants to expand to and then we can discuss it and see if we can
arrive at something that would be ok with everybody.
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/