> You can achieve same if replace goto with return

I know, but you designed this strange example.

> And by the way, just in case if you pretend that it's always best to work that way,

The point is about ease of design not speed.

But being obliged to call a routine which does evals for each single recursion level can hardly be faster then jumping back level by level.

with_return is neither easier to code nor faster.

> > For instance, when designing a recursion to search a graph it's sometimes desirable to stop immediately after the goal is reached.

Indeed I gave a real world example of searching a labyrinth.

You gave us strange code without motivation!

For me, the point about "multi returns" is to be able to use a simple algorithm that searches a complete graph, which can be easily changed with a minimum of code to have a fast exit.

Thats what goto does w/o overhead of a strange module.

edit

> And this is cheat again.

I used plain perl to solve tasks you "designed", producing the same output faster and with less code.

Who's cheating?

Cheers Rolf

( addicted to the Perl Programming Language)

In reply to Re^14: Continuations in Perl - Returning to an arbitrary level up the call stack by LanX
in thread Continuations in Perl - Returning to an arbitrary level up the call stack by unlinker

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.