Re: Dynamic modules: emacs-module.c and signaling errors

[Eli Zaretskii]

> From: Stefan Monnier <address@hidden>
> Cc: address@hidden
> Date: Thu, 26 Nov 2015 14:28:34 -0500
> 
> > What happens now is that modules can call Lisp only via env->funcall,
> > which _will_ catch the signal.  When the signal is caught, its data is
> > recorded.  All the other API calls made by the module function on
> > whose watch the signal happened will do nothing, and eventually the
> > module function will return to module-call, which will re-throw the
> > signal with exactly the same data.
> > Why is that a problem?
> 
> Because this loses the connection between the signal and its origin.

Not really, it doesn't.  You get the same Lisp error you'd get in
Emacs proper.

> Because it imposes a cost which we may not want to pay.

What cost is that?

> The current "funcall" should be renamed to "safe_funcall", and a new
> "funcall" should be provided which does not catch signals.

I still think we should be pragmatic about that, not radical.  If the
cake can be had and eaten, too, why not?