Mercurial > hg > xemacs-beta

comparison src/ChangeLog @ 5241:d579d76f3dcc

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Be more careful about side-effects from Lisp code, #'reduce src/ChangeLog addition: 2010-07-24 Aidan Kehoe <kehoea@parhasard.net> * lisp.h (PARSE_KEYWORDS): Always accept a nil :allow-other-keys keyword argument, as described in the ALLOW-OTHER-KEYS-NIL Common Lisp issue writeup, and as necessary for Paul Dietz' tests for #'reduce. * fns.c (mapping_interaction_error): New. (Freduce): Call mapping_interaction_error when KEY or FUNCTION have modified a string SEQUENCE such that the byte length of the string has changed, or such that the current cursor pointer doesn't point to the beginning of a character. Cf. the MAPPING-DESTRUCTIVE-INTERACTION Common Lisp issue writeup. When traversing a list, GCPRO the part of it we still have to traverse, to avoid any crashes if FUNCTION or KEY amputate it behind us and force a garbage collection. tests/ChangeLog addition: 2010-07-24 Aidan Kehoe <kehoea@parhasard.net> * automated/lisp-tests.el: Test a couple of things #'reduce was just made more careful about.
author Aidan Kehoe <kehoea@parhasard.net>
date Sat, 24 Jul 2010 15:56:57 +0100
parents fca0cf0971de
children 808131ba4a57
comparison
equal deleted inserted replaced
5240:fca0cf0971de 5241:d579d76f3dcc
1 2010-07-24 Aidan Kehoe <kehoea@parhasard.net>
2
3 * lisp.h (PARSE_KEYWORDS):
4 Always accept a nil :allow-other-keys keyword argument, as
5 described in the ALLOW-OTHER-KEYS-NIL Common Lisp issue writeup,
6 and as necessary for Paul Dietz' tests for #'reduce.
7
8 * fns.c (mapping_interaction_error): New.
9 (Freduce): Call mapping_interaction_error when KEY or FUNCTION
10 have modified a string SEQUENCE such that the byte length of the
11 string has changed, or such that the current cursor pointer
12 doesn't point to the beginning of a character.
13 Cf. the MAPPING-DESTRUCTIVE-INTERACTION Common Lisp issue
14 writeup.
15 When traversing a list, GCPRO the part of it we still have to
16 traverse, to avoid any crashes if FUNCTION or KEY amputate it
17 behind us and force a garbage collection.
18
1 2010-06-05 Marcus Crestani <crestani@informatik.uni-tuebingen.de> 19 2010-06-05 Marcus Crestani <crestani@informatik.uni-tuebingen.de>
2 20
3 * gc.c: 21 * gc.c:
4 * mc-alloc.c: 22 * mc-alloc.c:
5 Document the new allocator and the new garbage collector. 23 Document the new allocator and the new garbage collector.