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?