[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: module documentation draft
From: |
Basil L. Contovounesios |
Subject: |
Re: module documentation draft |
Date: |
Sun, 14 Oct 2018 16:47:25 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
Eli Zaretskii <address@hidden> writes:
> I've finally got to writing up this stuff, please take a look at the
> ELisp manual's node "Writing Dynamic Modules" on the latest emacs-26
> branch. Comments are welcome.
It all made sense to me, FWIW. I only noticed one potential
improvement:
diff --git a/doc/lispref/internals.texi b/doc/lispref/internals.texi
index 311eb6b262..c1d855fc2d 100644
--- a/doc/lispref/internals.texi
+++ b/doc/lispref/internals.texi
@@ -1190,7 +1190,7 @@ Module Functions
Lisp function object from it using @code{make_function}. This is
normally done in the module initialization function (@pxref{module
initialization function}), after verifying the @acronym{API}
-compatibility, and uses the pointer to @code{make_function} provided
+compatibility, and using the pointer to @code{make_function} provided
in the environment (recall that the pointer to the environment is
returned by @code{get_environment}).
> I'd like to take this opportunity to thank Philipp for his document
> (https://phst.github.io/emacs-modules), which I used as inspiration
> and as a reference against which to check my text. Thanks!
Thanks to both of you for the great work!
--
Basil