Re: emacs-dynamic-module in Emacs Git?

[Ted Zlatanov]

On Mon, 01 Dec 2014 14:12:08 -0500 Stefan Monnier <address@hidden> wrote: 

>> By API I meant both directions, the module API for registration and
>> metadata, and the Emacs API that modules can use. So I still think a
>> call-only API (only in the direction of calling the module) is best for
>> now, so that .h file is unnecessary.

SM> The exported functions will need to take Lisp_Object arguments and
SM> return Lisp_Object values, so they need to be able to test&create
SM> Lisp_Objects, hence they need to make calls to Emacs's C code even for
SM> the most trivial module imaginable.

I don't think that's the only way.  Eli and I listed some alternatives.

>> I agree with the rest of your comments, except that it's not clear when
>> you'll feel that the module loading is settled enough to merge into the
>> master branch.

SM> The criteria for me is not whether the feature is ready for general use,
SM> but whether the code that needs to be merged is sufficiently clean
SM> and stable ("stable" in the sense that it probably won't need to be
SM> completely replaced by a different implementation, so future changes
SM> should be "incremental improvements").
SM> The current code can pretty much be merged as it is.

OK, I'll do it in a few hours unless someone objects.  Thanks for your review.

Ted