ack "(a)*", $arg; }
if I single step through an expression
like this
s @x = x1('blabla')
s
s
...
(up to the end of function x1)
I never see the returned result. Neither in the debugger output,
nor in the variable @x. That is, when I do afterwards
x [EMAIL PROTECTED]
the array is empty.?!?!?
(ok, I just see, it is not empty, if @x has been used before,
what a weird behaviour, what is going on??? :-)
Greetings,
Heiko
ves
the scope of the subroutine. It looks to me as if the
evaluation of the action is done at the wrong place
(as $arg is not in scope anymore after 'return').
Can this be written into a test?
Thanks, Heiko
simple.pl:
==
use strict; use warnings;
greet('He
print "found\n";
How could that be done?
I could imagine $DB::single can be set to 3 for this 'accelerated'
stepping.
May I reserve the capital N for that command?
Thanks,
Heiko
--
"Spiros Denaxas" wrote:
> On Fri, Aug 29, 2008 at 3:53 PM, Richard Foley
> <[EMAIL PROTECTED]> wrote:
> > Hi Heiko,
> >
> >> I could imagine $DB::single can be set to 3 for this 'accelerated'
> >> stepping.
> > >
> &g
Richard Foley wrote:
> On Friday 29 August 2008 19:28:08 Heiko Eifeldt wrote:
> >
> > To Richard:
> > Afterwards I realized, $DB::single is to be used as a bitmask.
> > So it would be 8 instead of 3, since 4 is already taken.
> >
> Details, details ;-)
>
to mention, yes I agree.
My patch changed only 'n' like you wrote.
Heiko
--
27;sort of' incomplete
because it shortcutted only code blocks of explicitly declared
subroutines.
New Plan
So I would like to make a patch now, that will have 'n' short cut for
ANY code block, not only subroutines. And that should be done without a
regexp.
Help is of course very much appreciated!!
What do you think?
Geetings,
Heiko
step to the next statement (code1)
> rather than leap over to code4. I'm not sure what the solution is,
> but as you can see from the various comments, it's never quite as
> simple as it might seem at first. Possibly because it's Perl,
> there's just SMWTDI (so many ways to do it), that these kind of edge
> cases can become quite problematic.
Agreed.
Heiko
