Thanks for your fast answer!
On 18 Aug 2000, Mikael Djurfeldt wrote:
> Dirk Herrmann <[EMAIL PROTECTED]> writes:
>
> > scm_misc_error
> > (name,
> > "Observers of `~A' have signalled the following errors: ~S",
> > scm_cons2 (env, ordered_errors, SCM_UNDEFINED));
> ^^^^^^^^^^^^^
> (I assume that should be SCM_EOL.)
Right.
> Maybe the code should be changed so that the name passed by throw
> should override the stack frame info.
Since I don't see the whole picture about stacks, I can only talk from my
current perspective, which suggests `Yes' :-)
> Actually, thinking about it, this is an unintended use of the error
> reporting mechanism.
>
> It's not good to keep the copy of the stack from the last error.
>
> While the fix I suggested in the previous message probably should be
> implemented, you should also clear the stack by setting the
> the-last-stack fluid (scm_the_last_stack_fluid) to #f.
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.
Thank you very much again,
Dirk
