Dirk Herrmann <[EMAIL PROTECTED]> writes:
> I don't understand what you mean here. All that I do is to catch errors
> with scm_internal_catch and collect the error flags in a list. Do I have
> to fiddle around with stacks when using scm_internal_catch? If so, what
> is the purpose of the function scm_internal_stack_catch? While it may
> very well be that I miss something here, your suggestion seems like a
> workaround for a problem that should be solved in a different way.
You're right.
Sorry, I'm so busy right now and try to steal time in-between other
things, so I've got this bad habit to answer before giving things
enough that (for example, I should read the environment proposal
before trying to answer your questions ;-).
It *is* a problem that the currently saved error stack has side
effects on all subsequent error reporting.
We need to somehow make sure that this doesn't happen.
You're right that you shouldn't need to bother about such side-effects
in your example.
I'll think about this later.
