Mercurial > hg > xemacs-beta
changeset 1960:f4702ef3fd36
[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 | b10161763edf |
| children | aca6e69964bf |
| files | src/ChangeLog src/eval.c |
| diffstat | 2 files changed, 6 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- a/src/ChangeLog Sat Mar 20 12:51:25 2004 +0000 +++ b/src/ChangeLog Sat Mar 20 13:05:56 2004 +0000 @@ -1,3 +1,7 @@ +2004-03-20 Adrian Aichner <adrian@xemacs.org> + + * eval.c: Typo fixes. + 2004-03-16 Jerry James <james@xemacs.org> * alloc.c: Make gc_currently_forbidden readable in other files.
--- a/src/eval.c Sat Mar 20 12:51:25 2004 +0000 +++ b/src/eval.c Sat Mar 20 13:05:56 2004 +0000 @@ -56,7 +56,7 @@ The only exception is the alloc.c module, which implements the framework upon which this module (eval.c) works. alloc.c works with creating the actual Lisp objects themselves and garbage - collecting them as necessary, preseting a nice, high-level + collecting them as necessary, presenting a nice, high-level interface for object creation, deletion, access, and modification. The only other exception that could be cited is the event-handling @@ -73,7 +73,7 @@ functions such as `command-loop-1', a Lisp function. As the Lisp engine is doing its thing, it maintains the state of - the engine primarily in five list-like items, with are: + the engine primarily in five list-like items, which are: -- the backtrace list -- the catchtag list