Mercurial > hg > xemacs-beta

comparison src/eval.c @ 1960:f4702ef3fd36

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2004-03-20 13:05:53 by adrian] xemacs-21.5: typo fixes for src/eval.c -------------------- ChangeLog entries follow: -------------------- src/ChangeLog addition: 2004-03-20 Adrian Aichner <adrian@xemacs.org> * eval.c: Typo fixes.
author adrian
date Sat, 20 Mar 2004 13:05:56 +0000
parents 31d5f86eb303
children e9aa19426bc9
comparison
equal deleted inserted replaced
1959:b10161763edf 1960:f4702ef3fd36
54 time. 54 time.
55 55
56 The only exception is the alloc.c module, which implements the 56 The only exception is the alloc.c module, which implements the
57 framework upon which this module (eval.c) works. alloc.c works 57 framework upon which this module (eval.c) works. alloc.c works
58 with creating the actual Lisp objects themselves and garbage 58 with creating the actual Lisp objects themselves and garbage
59 collecting them as necessary, preseting a nice, high-level 59 collecting them as necessary, presenting a nice, high-level
60 interface for object creation, deletion, access, and modification. 60 interface for object creation, deletion, access, and modification.
61 61
62 The only other exception that could be cited is the event-handling 62 The only other exception that could be cited is the event-handling
63 module in event-stream.c. From its perspective, it is also the 63 module in event-stream.c. From its perspective, it is also the
64 heart of XEmacs, and controls exactly what gets done at what time. 64 heart of XEmacs, and controls exactly what gets done at what time.
71 the truth, because anywhere within the event-stream module, you are 71 the truth, because anywhere within the event-stream module, you are
72 still somewhere in a Lisp backtrace, and event-loops are begun by 72 still somewhere in a Lisp backtrace, and event-loops are begun by
73 functions such as `command-loop-1', a Lisp function. 73 functions such as `command-loop-1', a Lisp function.
74 74
75 As the Lisp engine is doing its thing, it maintains the state of 75 As the Lisp engine is doing its thing, it maintains the state of
76 the engine primarily in five list-like items, with are: 76 the engine primarily in five list-like items, which are:
77 77
78 -- the backtrace list 78 -- the backtrace list
79 -- the catchtag list 79 -- the catchtag list
80 -- the condition-handler list 80 -- the condition-handler list
81 -- the specbind list 81 -- the specbind list