in reply to About the opcodes of Perl

how can the executor still chain them together?

Magic :)

But seriously, where do you see cLOGOP->op_next in PP(pp_unstack)?

Do you what what is NORMAL?

Unraveling the execution path sounds like a job for a debugger :)

Replies are listed 'Best First'.
Re^2: About the opcodes of Perl
by PerlOnTheWay (Monk) on Sep 02, 2011 at 09:39 UTC

    Hah,I missed that...

    I also found that RETURN alone does something similar: 

    #define RETURN        return (PUTBACK, NORMAL)

    [download]

    Why perl uses so many different ways to do the same thing?

    The version I download is 5.14.1,which may not be the newest.

[reply]
[d/l]
[select]
      huh, none of 
      RETURNOP(cLOGOP->op_other);
RETURNOP(cLOGOP->op_next);
RETURN;
return NORMAL;

      [download]
      don't do the same thing. The fourth could probably use a more consistent name, but they other three are rather consistent. I don't see the complain.
[reply]
[d/l]

      Why perl uses so many different ways to do the same thing?

      :)

      1) I don't know that it does 2) p5p might know 3) code evolves 4) different strokes 5) similar is not same, they're different 6) olly olly oxen free

[reply]

In Section Seekers of Perl Wisdom