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

[Eli Zaretskii]

> From: Stefan Monnier <address@hidden>
> Cc: address@hidden
> Date: Thu, 26 Nov 2015 11:36:00 -0500
> 
> The issue at stake is when module code calls an Emacs function that
> signals an error.  In the basic API this signal should not be caught by
> the module API (i.e. Emacs's Fsignal code will happily longjmp out of
> the modules code when applicable), unless explicitly requested via
> something like env->safe_funcall.

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?