>>46
What about sticking your backtrace into a ring buffer?
>I have a vague recollection of what you're talking about, I remember deciding that for such a contrived case you are better off implementing your code flow explicitly. I could reconsider if you give me the chance, by providing a link.
I was referring to Guy Steele's take on the "Understanding Data Abstraction, Revisited" paper. His example was contrived to fit in a blog post and was about implementing sets in an OO fashion. The example was there to point out that if you do it in an OO manner, then you will build up a large stack because most languages don't optimise tail calls. If you do not optimise them, you have to break the abstraction.
http://projectfortress.sun.com/Projects/Community/blog/ObjectOrientedTailRecursion