functional programming
Aahz Maruch
aahz at netcom.com
Wed Feb 23 01:01:34 EST 2000
In article <000801bf7daa$80dde000$51a0143f at tim>,
Tim Peters <tim_one at email.msn.com> wrote:
>
>2.5. One great thing that shakes bugs out of Python code is that it
> raises an exception whenever it has a reasonable doubt about the
> code you told it execute, and a key part of making that *usable*
> is Python's never-lies complete stack trace. If A calls B tails
> calls C tail calls D blows up, I damn sure don't want a traceback
> claiming that A called D directly. I want to get a traceback object
> with the full chain intact, and I want to crawl up that chain to
> examine the state of the locals in B and C at the time they made
> their calls. Optimize intermediate frames away, and tracebacks
> would become much harder to decipher.
Say! Couldn't you use continuations to store those intermediate frames
in case you ever throw an exception?
Bet-you-can't-tell-if-I'm-joking-ly y'rs
--
--- Aahz (Copyright 2000 by aahz at netcom.com)
Androgynous poly kinky vanilla queer het <*> http://www.rahul.net/aahz/
Hugs and backrubs -- I break Rule 6
Love does not conquer all. Humans are extremely flexible, usually more
flexible than we're willing to admit. But some flexibility comes at a
cost, and sometimes that cost is more than we can bear.
More information about the Python-list
mailing list