X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;f=info%2Finternals.info-1;h=b357f91c2367b215746b415abe706c076b73c0fb;hb=c461477e9d1c45206851e095d1398498d09d040c;hp=c385b18115352c342696b0da99bb3ebce6fff510;hpb=c8aa261a7bf3eb1389d2e018be1d715f73cacd66;p=chise%2Fxemacs-chise.git diff --git a/info/internals.info-1 b/info/internals.info-1 index c385b18..b357f91 100644 --- 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 @@ -54,6 +54,7 @@ File: internals.info, Node: Top, Next: A History of Emacs, Prev: (dir), Up: * Rules When Writing New C Code:: * A Summary of the Various XEmacs Modules:: * Allocation of Objects in XEmacs Lisp:: +* Dumping:: * Events and the Event Loop:: * Evaluation; Stack Frames; Bindings:: * Symbols and Variables:: @@ -69,20 +70,18 @@ File: internals.info, Node: Top, Next: A History of Emacs, Prev: (dir), Up: * Specifiers:: * Menus:: * Subprocesses:: -* Interface to X Windows:: -* Index:: Index including concepts, functions, variables, - and other terms. +* Interface to the X Window System:: +* Index:: - --- The Detailed Node Listing --- -Here are other nodes that are inferiors of those already listed, -mentioned here so you can get to them in one step: +--- The Detailed Node Listing --- A History of Emacs * Through Version 18:: Unification prevails. * Lucid Emacs:: One version 19 Emacs. * GNU Emacs 19:: The other version 19 Emacs. +* GNU Emacs 20:: The other version 20 Emacs. * XEmacs:: The continuation of Lucid Emacs. Rules When Writing New C Code @@ -90,8 +89,17 @@ Rules When Writing New C Code * General Coding Rules:: * Writing Lisp Primitives:: * Adding Global Lisp Variables:: +* Coding for Mule:: * Techniques for XEmacs Developers:: +Coding for Mule + +* Character-Related Data Types:: +* Working With Character and Byte Positions:: +* Conversion to and from External Data:: +* General Guidelines for Writing Mule-Aware Code:: +* An Example of Mule-Aware Code:: + A Summary of the Various XEmacs Modules * Low-Level Modules:: @@ -117,7 +125,6 @@ Allocation of Objects in XEmacs Lisp * Allocation from Frob Blocks:: * lrecords:: * Low-level allocation:: -* Pure Space:: * Cons:: * Vector:: * Bit Vector:: @@ -126,6 +133,32 @@ Allocation of Objects in XEmacs Lisp * String:: * Compiled Function:: +Garbage Collection - Step by Step + +* Invocation:: +* garbage_collect_1:: +* mark_object:: +* gc_sweep:: +* sweep_lcrecords_1:: +* compact_string_chars:: +* sweep_strings:: +* sweep_bit_vectors_1:: + +Dumping + +* Overview:: +* Data descriptions:: +* Dumping phase:: +* Reloading phase:: + +Dumping phase + +* Object inventory:: +* Address allocation:: +* The header:: +* Data dumping:: +* Pointers dumping:: + Events and the Event Loop * Introduction to Events:: @@ -164,6 +197,7 @@ MULE Character Sets and Encodings * Character Sets:: * Encodings:: * Internal Mule Encodings:: +* CCL:: Encodings @@ -175,20 +209,25 @@ Internal Mule Encodings * Internal String Encoding:: * Internal Character Encoding:: -The Lisp Reader and Compiler - Lstreams +* Creating an Lstream:: Creating an lstream object. +* Lstream Types:: Different sorts of things that are streamed. +* Lstream Functions:: Functions for working with lstreams. +* Lstream Methods:: Creating new lstream types. + Consoles; Devices; Frames; Windows * Introduction to Consoles; Devices; Frames; Windows:: * Point:: * Window Hierarchy:: +* The Window Object:: The Redisplay Mechanism * Critical Redisplay Sections:: * Line Start Cache:: +* Redisplay Piece by Piece:: Extents @@ -196,21 +235,9 @@ Extents * Extent Ordering:: How extents are ordered internally. * Format of the Extent Info:: The extent information in a buffer or string. * Zero-Length Extents:: A weird special case. -* Mathematics of Extent Ordering:: A rigorous foundation. +* Mathematics of Extent Ordering:: A rigorous foundation. * Extent Fragments:: Cached information useful for redisplay. -Faces - -Glyphs - -Specifiers - -Menus - -Subprocesses - -Interface to X Windows -  File: internals.info, Node: A History of Emacs, Next: XEmacs From the Outside, Prev: Top, Up: Top @@ -243,7 +270,7 @@ language developed at MIT that underlies Emacs.) * XEmacs:: The continuation of Lucid Emacs.  -File: internals.info, Node: Through Version 18, Next: Lucid Emacs, Up: A History of Emacs +File: internals.info, Node: Through Version 18, Next: Lucid Emacs, Prev: A History of Emacs, Up: A History of Emacs Through Version 18 ================== @@ -796,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 -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 @@ -1042,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. -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.