Recursion along with memo-ization allows clean, readable, maintainable code. Recursion has it's place in the tool-box of any professional programmer worthy of the name (and pay).

The fact that you can pose a problem large enough to cause your recursion depth to go to the point that you exhaust your computer's resources is an indicator that you need a better computer.

Or perhaps you are confusing recursion with 'fork-bomb'.

Do you have a power plug?

You ever wrote any piece of code using recursion?

Or some perl script running flawless except "Hello World!" or something else that you copied from somewhere?

But perhaps i'm totally wrong - here is that excellent template given to you liberally by 1nickt:

#!/usr/bin/perl

# sundialsvc4 code goes here

__END__
[download]

Fill in your stuff and show some working code (no pseudo code please).

Else please stop giving advice for anything you lack competence.

Please note: You have been told this hundred times before.

Karl

Though I did have to hold the power button down 5 seconds, same as pulling the plug!

Fifteen and counting. The reason is neatly summed up by one of the AnonymousMonkies above: Never use recursion is terrible, incurious advice. Even Don't use recursion for this problem is awful absent context, and unwelcome absent a demonstrated alternative.

I did like the Bathysphere anecdote, which was new to me, and took it in the spirit of "add a limit, if you're worried about recursion depth." I admit it may not have been Sun's intent! And I'm fine with everyone voting their conscience.

S-Dial2English output:

Don't use recursion.

AUTO RESPONSE:

Like in Haskell's default looping mechanism and Swift's for-each loops behind the scenes and in Perl as described in MJD's HOP and ad infinitum for every modern programming language.