At 03:11 PM 5/2/2001 -0700, Dave Storrs wrote:
>On Tue, 1 May 2001, Dan Sugalski wrote:
>
> > Right. What I'm thinking would be a good place to get to is a list of the
> > functionality that the debugger needs to provide or have available to it
> > from the interpreter, rather than the actual in
On Tue, 1 May 2001, Dan Sugalski wrote:
> Right. What I'm thinking would be a good place to get to is a list of the
> functionality that the debugger needs to provide or have available to it
> from the interpreter, rather than the actual interface to the user. (Which
> is important, but a se
At 12:01 PM 4/27/2001 -0700, Dave Storrs wrote:
>On Fri, 27 Apr 2001, Dan Sugalski wrote:
> > At this stage, it might be better to go through and pull out the concepts
> > and capabilities we need, rather than get into the details of user
> > interface. Knowing, for example, that we need to provid
One additional item I thought I had in my yestermessage but apparently
forgot: don't forget the regex minilanguage. Debugging it should be
an integral part.
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Co
Great, thanks very much.
Dave
On Fri, 27 Apr 2001, Jarkko Hietaniemi wrote:
> > > see it.) The debugger must be able to see two scopes at the same time:
> > > its own and the debuggee's.
> >
> > Could you expand on this?
>
> http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2001-02
> > see it.) The debugger must be able to see two scopes at the same time:
> > its own and the debuggee's.
>
> Could you expand on this?
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2001-02/msg01613.html
for example.
--
$jhi++; # http://www.iki.fi/jhi/
# There is th
On Fri, 27 Apr 2001, Dan Sugalski wrote:
> Thanks much for putting this together. I do appreciate it.
You are most welcome. I enjoyed it, and I'm looking forward to
updating it (though I'm hoping there will be a little more feedback,
particularly concerning the new suggestions).
>
On Thu, 26 Apr 2001, Jarkko Hietaniemi wrote:
>
> You list the particular commands as 'existing functionality'. I think
> this is a mistake, even if you didn't mean it that way, if it was just
> an artifact of your presentation format. I know that breaking
> debugging habits that have been i
Thanks much for putting this together. I do appreciate it.
At this stage, it might be better to go through and pull out the concepts
and capabilities we need, rather than get into the details of user
interface. Knowing, for example, that we need to provide help is more
important at this stage
You list the particular commands as 'existing functionality'. I think
this is a mistake, even if you didn't mean it that way, if it was just
an artifact of your presentation format. I know that breaking
debugging habits that have been ingrained in at the spinal level may
be hard to break, but t
=head1 The Perl6 Debugger
=head2 Perl-level Debugging
=head3 Existing Functionality
The following is a list of the functionality in the existing Perl5
debugger; this functionality should, of course, be maintained for
backwards compatibility.
=over 4
=item T
Stack trace.
=item
11 matches
Mail list logo
