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

[Daniel Colascione]

On 11/24/2015 01:34 PM, Paul Eggert wrote:
> On 11/24/2015 12:49 PM, Eli Zaretskii wrote:
>> Btw, using this method the module code becomes very tedious
> 
> It's so tedious I can't imagine using it that way. Module authors
> shouldn't have to call env->non_local_exit_check (env) after every
> function call, to see whether the function actually worked. Functions
> should be able to signal an error, just as they can in the Emacs core,
> and the error should propagate through calls in a natural way.

And in a C++ wrapper interface, that can happen naturally and safely. If
you want to write C, you check for errors the C way.

signature.asc
Description: OpenPGP digital signature