XEmacs 21.2.22 "Mercedes".

[chise/xemacs-chise.git.1] / info / emodules.info

diff --git a/info/emodules.info b/info/emodules.info
index f81e90f..b04e884 100644 (file)
--- a/info/emodules.info
+++ b/info/emodules.info
@@ -1,5 +1,5 @@
-This is Info file ../info/emodules.info, produced by Makeinfo version
-1.68 from the input file emodules.texi.
+This is ../info/emodules.info, produced by makeinfo version 4.0 from
+emodules.texi.
 
    This file documents the module loading technology of XEmacs.
 
@@ -47,7 +47,7 @@ support documentation.
 * Defining Variables::          Creating new Lisp variables
 * Index::                       Concept Index
 
- -- The Detailed Node Listing --
+ --- The Detailed Node Listing ---
 
 Annatomy of a Module
 
@@ -244,7 +244,7 @@ place-holder, not an actual function name.
 `syms_of_module'
      This required function is responsible for introducing to the Lisp
      reader all functions that you have defined in your module using
-     `DEFUN()'.  Note that *only* functions are declared here, using
+     `DEFUN()'.  Note that _only_ functions are declared here, using
      the `DEFSUBR()' macro.  No variables are declared.
 
 `vars_of_module'
@@ -276,7 +276,7 @@ Required Variables
    Not only does a module need to declare the initialization functions
 mentioned above, it is also required to provide certain variables which
 the module loading code searches for in order to determine the viability
-of a module.  You are *not* required to provide these variables in your
+of a module.  You are _not_ required to provide these variables in your
 source files.  They are automatically set up in the module
 initialization file by the `ellcc' compiler.  These variables are
 discussed here simply for the sake of completeness.
@@ -820,7 +820,7 @@ initialization function using special XEmacs macros such as
 how to use these macros is to look at existing source code, or read the
 internals manual.
 
-   One *very* important difference between XEmacs variables and module
+   One _very_ important difference between XEmacs variables and module
 variables is how you use pure space.  Simply put, you *never* use pure
 space in XEmacs modules.  The pure space storage is of a limited size,
 and is initialized propperly during the dumping of XEmacs.  Because
@@ -930,23 +930,23 @@ Index
 
 \1f
 Tag Table:
-Node: Top\7f1562
-Node: Introduction\7f2908
-Node: Annatomy of a Module\7f7417
-Node: Required Header File\7f8233
-Node: Required Functions\7f10154
-Node: Required Variables\7f12403
-Node: Loading other Modules\7f15090
-Node: Using ellcc\7f17148
-Node: Compile Mode\7f18943
-Node: Initialization Mode\7f20311
-Node: Link Mode\7f25343
-Node: Other ellcc options\7f26490
-Node: Environment Variables\7f29070
-Node: Defining Functions\7f30761
-Node: Using DEFUN\7f32772
-Node: Declaring Functions\7f34483
-Node: Defining Variables\7f35826
-Node: Index\7f38071
+Node: Top\7f1536
+Node: Introduction\7f2884
+Node: Annatomy of a Module\7f7393
+Node: Required Header File\7f8209
+Node: Required Functions\7f10130
+Node: Required Variables\7f12379
+Node: Loading other Modules\7f15066
+Node: Using ellcc\7f17124
+Node: Compile Mode\7f18919
+Node: Initialization Mode\7f20287
+Node: Link Mode\7f25319
+Node: Other ellcc options\7f26466
+Node: Environment Variables\7f29046
+Node: Defining Functions\7f30737
+Node: Using DEFUN\7f32748
+Node: Declaring Functions\7f34459
+Node: Defining Variables\7f35802
+Node: Index\7f38047
 \1f
 End Tag Table