News for hackers. Stuff that matters.
Re:How recursion got into programming: a comedy of errors by rubiquity on Wednesday July 23, 2014 @11:00AM (#8074689)
I guess. But if I make the mistake of infinitely recursing I find out the next time I run my program. If I'm writing my own loops and make an off by one error it could go uncaught potentially forever.
Re:How recursion got into programming: a comedy of errors by pekk on Wednesday July 23, 2014 @12:24PM (#8075193)
You don't necessarily find out the next time you run your program. A stack overflow can go uncaught potentially forever.
Re:How recursion got into programming: a comedy of errors by PaulHoule on Wednesday July 23, 2014 @12:48PM (#8075354)
One of my favorite PHP gotchas is to accidentally write a function that calls itself infinitely, and then have the interpreter die without a warning message.
Re:How recursion got into programming: a comedy of errors by mtdewcmu on Thursday July 24, 2014 @12:09AM (#8078178)
If a program is only doing a simple calculation and it's still running an hour later, you should probably suspect an infinite loop and not wait for it to stop.
Re:How recursion got into programming: a comedy of errors by Rusky on Wednesday July 23, 2014 @02:13PM (#8075937)
So use iterators? Sometimes loops are just the clearer way to express something.