Re: Detecting endless recursion?

>> It's not at all a troll. The tail-call optimization does make
>> debugging more difficult -- please review the post again. Further,
>> removing the optimization can cause programs that need it to fail, and


The only difficulty I can see is that the call stack doesn't show
tail-calls.


But optimized recursive tail-calls are equivalent to loops. I've never
seen a debugger that gave me a trace back through loop iterations
either.


In a language like scheme, this isn't just an otimization -- it's the
law. Knowing that, I write my loops as recursion. I wouldn't want to
see the call stack include tail-recursive calls -- there'd be too many
of them and they'd tell me too little.


I suppose I really want a reverse execution facility for debugging.


--
mac the naïf

Return to the comp.compilers page.
Search the comp.compilers archives again.