On Aug 28 11:21, Neil Jerram wrote:
A common requirement is to be able to show as much useful context as
possible when a Scheme program hits an error. The most immediate
information about an error is the kind of error that it is - such as
division by zero - and any parameters that the code
Volkan YAZICI [EMAIL PROTECTED] writes:
I've another situation that doesn't get executed inside a `catch' block.
For instance, I need to make some variable definitions just before
executing related code via scm_c_with_throw_handler(). The problem is,
in these definitions when an error occurs
[EMAIL PROTECTED] (Ludovic Courtès) writes:
Indeed, this exception model is not very convenient. In some cases,
it's even hardly usable, as examplified by the `test-suite/lib.scm'
hacks (use of regexps to parse exception messages and determine their
meaning...).
IMO this isn't so bad.
Kevin Ryde [EMAIL PROTECTED] writes:
I had trouble understanding the different dynamic environments
specified for that srfi-34 guard. It looked worryingly like there
could be jumps out of the originating continuation and then back in if
there's a re-throw, which could be pretty slow with
