(C3-272A): Unify U-0002F98F; relate to M-30681.

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

diff --git a/info/internals.info-1 b/info/internals.info-1
index 20db3d2..b357f91 100644 (file)
--- a/info/internals.info-1
+++ b/info/internals.info-1
@@ -1,4 +1,4 @@
-This is ../info/internals.info, produced by makeinfo version 4.0 from
+This is ../info/internals.info, produced by makeinfo version 4.0b from

 internals/internals.texi.
 
 INFO-DIR-SECTION XEmacs Editor
 internals/internals.texi.
 
 INFO-DIR-SECTION XEmacs Editor

@@ -70,10 +70,12 @@ File: internals.info,  Node: Top,  Next: A History of Emacs,  Prev: (dir),  Up:
 * Specifiers::
 * Menus::
 * Subprocesses::
 * Specifiers::
 * Menus::
 * Subprocesses::

-* Interface to X Windows::
+* Interface to the X Window System::

 * Index::
 
 
 * Index::
 
 

+--- The Detailed Node Listing ---
+

 A History of Emacs
 
 * Through Version 18::          Unification prevails.
 A History of Emacs
 
 * Through Version 18::          Unification prevails.

@@ -123,7 +125,6 @@ Allocation of Objects in XEmacs Lisp
 * Allocation from Frob Blocks::
 * lrecords::
 * Low-level allocation::
 * Allocation from Frob Blocks::
 * lrecords::
 * Low-level allocation::

-* Pure Space::

 * Cons::
 * Vector::
 * Bit Vector::
 * Cons::
 * Vector::
 * Bit Vector::

@@ -822,13 +823,13 @@ different from C):
 
    Unfortunately, there is no perfect language.  Static typing allows a
 compiler to catch programmer errors and produce more efficient code, but
 
    Unfortunately, there is no perfect language.  Static typing allows a
 compiler to catch programmer errors and produce more efficient code, but

-makes programming more tedious and less fun.  For the forseeable future,
-an Ideal Editing and Programming Environment (and that is what XEmacs
-aspires to) will be programmable in multiple languages: high level ones
-like Lisp for user customization and prototyping, and lower level ones
-for infrastructure and industrial strength applications.  If I had my
-way, XEmacs would be friendly towards the Python, Scheme, C++, ML,
-etc... communities.  But there are serious technical difficulties to
+makes programming more tedious and less fun.  For the foreseeable
+future, an Ideal Editing and Programming Environment (and that is what
+XEmacs aspires to) will be programmable in multiple languages: high
+level ones like Lisp for user customization and prototyping, and lower
+level ones for infrastructure and industrial strength applications.  If
+I had my way, XEmacs would be friendly towards the Python, Scheme, C++,
+ML, etc... communities.  But there are serious technical difficulties to

 achieving that goal.
 
    The word "application" in the previous paragraph was used
 achieving that goal.
 
    The word "application" in the previous paragraph was used

@@ -1068,7 +1069,7 @@ function by setting its name as the value of the Lisp variable
 
    When the Lisp initialization code is done, the C code enters the
 event loop, and stays there for the duration of the XEmacs process.
 
    When the Lisp initialization code is done, the C code enters the
 event loop, and stays there for the duration of the XEmacs process.

-The code for the event loop is contained in `keyboard.c', and is called
+The code for the event loop is contained in `cmdloop.c', and is called

 `Fcommand_loop_1()'.  Note that this event loop could very well be
 written in Lisp, and in fact a Lisp version exists; but apparently,
 doing this makes XEmacs run noticeably slower.
 `Fcommand_loop_1()'.  Note that this event loop could very well be
 written in Lisp, and in fact a Lisp version exists; but apparently,
 doing this makes XEmacs run noticeably slower.