in reply to Is deep recursion bad?

This probably indicates an infinite recur­sion, unless you're writing strange benchmark pro­grams, in which case it indicates something else.
However, there are plenty problems out there that can be solved most effectively using recursion. There might be other ways, but recursion could be better (quicksort, anyone?).

ezekiel - it seems your application is one of those cases.

Try placing

no warnings 'recursion';
within the same scope as that code (use a naked block if you have/need to), provided you're sure that you wish to silence those warnings (more complete example in readmore).

Cheers.

BazB.

Update: Added useful(-ish) example.

use strict; use warnings; # turn on all warnings sub recurse { no warnings 'recursion'; # turn off recursion warnings # in this block _only_ # do recursive processing return $something; } # all warnings back on, since you are outside of the # scope where no warnings 'recursion' was set.


If the information in this post is inaccurate, or just plain wrong, don't just downvote - please post explaining what's wrong.
That way everyone learns.