summaryrefslogtreecommitdiff
path: root/devdocs/elisp/writing-dynamic-modules.html
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2025-08-14 22:58:58 -0500
committerCraig Jennings <c@cjennings.net>2025-08-14 22:58:58 -0500
commit82ba818ff456bcd6d56a06226e3f27e98fbb55c3 (patch)
tree158cfc17b2f644a10f063cb546752cfaae12c97f /devdocs/elisp/writing-dynamic-modules.html
parent9278ddd4ea1a8b1a4c1edaa8894516e3f48d245b (diff)
downloaddotemacs-82ba818ff456bcd6d56a06226e3f27e98fbb55c3.tar.gz
dotemacs-82ba818ff456bcd6d56a06226e3f27e98fbb55c3.zip
removing all downloaded devdocs files
Diffstat (limited to 'devdocs/elisp/writing-dynamic-modules.html')
-rw-r--r--devdocs/elisp/writing-dynamic-modules.html35
1 files changed, 0 insertions, 35 deletions
diff --git a/devdocs/elisp/writing-dynamic-modules.html b/devdocs/elisp/writing-dynamic-modules.html
deleted file mode 100644
index b8dfcca1..00000000
--- a/devdocs/elisp/writing-dynamic-modules.html
+++ /dev/null
@@ -1,35 +0,0 @@
- <h3 class="section"> Writing Dynamically-Loaded Modules</h3> <p>This section describes the Emacs module <acronym>API</acronym> and how to use it as part of writing extension modules for Emacs. The module <acronym>API</acronym> is defined in the C programming language, therefore the description and the examples in this section assume the module is written in C. For other programming languages, you will need to use the appropriate bindings, interfaces and facilities for calling C code. Emacs C code requires a C99 or later compiler (see <a href="c-dialect">C Dialect</a>), and so the code examples in this section also follow that standard. </p> <p>Writing a module and integrating it into Emacs comprises the following tasks: </p> <ul> <li> Writing initialization code for the module. </li>
-<li> Writing one or more module functions. </li>
-<li> Communicating values and objects between Emacs and your module functions. </li>
-<li> Handling of error conditions and nonlocal exits. </li>
-</ul> <p>The following subsections describe these tasks and the <acronym>API</acronym> itself in more detail. </p> <p>Once your module is written, compile it to produce a shared library, according to the conventions of the underlying platform. Then place the shared library in a directory mentioned in <code>load-path</code> (see <a href="library-search">Library Search</a>), where Emacs will find it. </p> <p>If you wish to verify the conformance of a module to the Emacs dynamic module <acronym>API</acronym>, invoke Emacs with the <kbd>--module-assertions</kbd> option. See <a href="https://www.gnu.org/software/emacs/manual/html_node/emacs/Initial-Options.html#Initial-Options">Initial Options</a> in <cite>The GNU Emacs Manual</cite>. </p> <table class="menu" border="0" cellspacing="0"> <tr>
-<td align="left" valign="top">• <a href="module-initialization" accesskey="1">Module Initialization</a>
-</td>
-<td> </td>
-<td align="left" valign="top"> </td>
-</tr> <tr>
-<td align="left" valign="top">• <a href="module-functions" accesskey="2">Module Functions</a>
-</td>
-<td> </td>
-<td align="left" valign="top"> </td>
-</tr> <tr>
-<td align="left" valign="top">• <a href="module-values" accesskey="3">Module Values</a>
-</td>
-<td> </td>
-<td align="left" valign="top"> </td>
-</tr> <tr>
-<td align="left" valign="top">• <a href="module-misc" accesskey="4">Module Misc</a>
-</td>
-<td> </td>
-<td align="left" valign="top"> </td>
-</tr> <tr>
-<td align="left" valign="top">• <a href="module-nonlocal" accesskey="5">Module Nonlocal</a>
-</td>
-<td> </td>
-<td align="left" valign="top"> </td>
-</tr> </table><div class="_attribution">
- <p class="_attribution-p">
- Copyright &copy; 1990-1996, 1998-2022 Free Software Foundation, Inc. <br>Licensed under the GNU GPL license.<br>
- <a href="https://www.gnu.org/software/emacs/manual/html_node/elisp/Writing-Dynamic-Modules.html" class="_attribution-link">https://www.gnu.org/software/emacs/manual/html_node/elisp/Writing-Dynamic-Modules.html</a>
- </p>
-</div>