Re:How recursion got into programming: a comedy of errors
by rubiquity on Wednesday July 23, 2014 @09:55AM
(#8074350)
Yes, but humans mess up loops far more frequently than compilers do. If we follow your argument recursively, we would all end up writing assembly language again, wouldn't we? :)
[ Parent
| on HN ]
Re:How recursion got into programming: a comedy of errors
by coldtea on Wednesday July 23, 2014 @10:42AM
(#8074602)
Is that meant as an argument against loops and pro recursion?
Because humans also screw recursion all the time.
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.