Marius Vollmer <[EMAIL PROTECTED]> writes:
> Gary Houston <[EMAIL PROTECTED]> writes:
>
> > This behaviour can be got back by explicitly calling SCM_ASYNC_TICK from
> > the handler, but I'm not sure if this was what you wanted to avoid with
> > the posix threads change:
>
> Intuitively, I would like to call SCM_ASYNC_TICK from take_signal, but
> I don't know the consequences.
They are dire and terrible. :)
Actually, the entire purpose of te asyncs is that signal handlers
should be run at a well-defined place during evaluation. So,
SCM_ASYNC_TICK should only be run at the top of the evaluator loop and
maybe a couple of further places.
What you could, and probably should, do is to call SCM_TICK in longer
loops in your simulator code.
Now I have to run and look at a rat running in a maze! I'll write t
you again soon.
/mdj
