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

[Stefan Monnier]

> I think Daniel is worried that module code will call xmalloc, and then do
> more work that signals an Elisp error or throws a C++ exception, and the
> module will then leak the xmalloced memory. There may be other concerns like
> that too, but I'm not sure what they are.

I find it hard to believe that we'd follow Daniel's recommendation
over mine.  As far as I know, he didn't give any more evidence of his
assertions of goodness of his approach than I did (OTOH, it's obvious at
the technical level that Daniel's approach can be layered on top of
mine, whereas the reverse is not true, which I think should a strong
argument in favor of following the simpler approach I advocate).


        Stefan