On 04/11/14 09:37, Joe Watkins wrote:
> On Tue, 2014-11-04 at 09:19 +, Lester Caine wrote:
>> On 04/11/14 06:00, Joe Watkins wrote:
>>> I'm not saying we should not extend the features of phpdbg, but, we
>>> should do it knowing what it actually is, knowing that it is
>>> fundamentally differen
On Tue, 2014-11-04 at 09:19 +, Lester Caine wrote:
> On 04/11/14 06:00, Joe Watkins wrote:
> > I'm not saying we should not extend the features of phpdbg, but, we
> > should do it knowing what it actually is, knowing that it is
> > fundamentally different to xdebug.
>
> Having just hit another
On 04/11/14 06:00, Joe Watkins wrote:
> I'm not saying we should not extend the features of phpdbg, but, we
> should do it knowing what it actually is, knowing that it is
> fundamentally different to xdebug.
Having just hit another 'white screen' problem on a site I'm trying to
update, I do wonder
On Mon, 2014-11-03 at 21:03 +, Derick Rethans wrote:
> 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, w
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'
Hi,
Derick wrote:
> I asked him what the original scope of phpdbg was,...
> And I very much agree that the above bullet points,
The original scope of a project and what it should be in the future
are not related always related. Please don't pretend that they're the
same thing.
Derick wrote:
> I'
> Am 03.11.2014 um 22:03 schrieb Derick Rethans :
>
> 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
Hi,
Why should phpdbg scope be limited, and not extended? As far as I know,
xdebug is nowhere like an official php project, so overlap shouldn't be an
issue.
I'm not saying phpdbg has to be extended, but I'm wondering why it should
be limited.
Regards,
On Mon, Nov 3, 2014 at 10:03 PM, Derick Re
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 b
