comparison man/internals/internals.texi @ 2069:97a3d9ad40e2

[xemacs-hg @ 2004-05-10 07:18:54 by stephent] tweak internals.texi <87vfj43g4j.fsf_-_@tleepslib.sk.tsukuba.ac.jp>
author stephent
date Mon, 10 May 2004 07:18:58 +0000
parents 2ba4f06a264d
children c91543697b09
comparison
equal deleted inserted replaced
2068:7dc50bbd7a39 2069:97a3d9ad40e2
2510 devices and platforms. Commonly, but not always, such objects are 2510 devices and platforms. Commonly, but not always, such objects are
2511 ``wrapped'' and exported to Lisp as Lisp objects. Usually they use 2511 ``wrapped'' and exported to Lisp as Lisp objects. Usually they use
2512 the internal structures developed for Lisp objects (the @samp{lrecord} 2512 the internal structures developed for Lisp objects (the @samp{lrecord}
2513 structure) in order to take advantage of Lisp memory management. 2513 structure) in order to take advantage of Lisp memory management.
2514 Unfortunately, XEmacs was originally written in C, so these techniques 2514 Unfortunately, XEmacs was originally written in C, so these techniques
2515 are based on heavy use of C macros. Since XEmacs has been rewritten in 2515 are based on heavy use of C macros.
2516 ``Clean C,'' @emph{i.e.}, it compiles under both C and C++, it should be
2517 possible to migrate to C++. It is hoped this documentation will help
2518 encourage this process.
2519 2516
2520 @c You can't use @var{} for type below, because case is important. 2517 @c You can't use @var{} for type below, because case is important.
2521 A module defining a class is likely to use most of the following 2518 A module defining a class is likely to use most of the following
2522 declarations and macros. In the following, the notation @samp{<type>} 2519 declarations and macros. In the following, the notation @samp{<type>}
2523 will stand for the full name of the class, and will be capitalized in 2520 will stand for the full name of the class, and will be capitalized in