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.

#ifndef YYSTYPE
#define YYSTYPE int
#endif
#define	STRING	257
#define	SETUP_TIMESTAMP	258
#define	SETUP_VERSION	259
#define	VERSION	260
#define	INSTALL	261
#define	SOURCE	262
#define	SDESC	263
#define	LDESC	264
#define	TYPE	265
#define	T_PREV	266
#define	T_CURR	267
#define	T_TEST	268
#define	T_UNKNOWN	269


extern YYSTYPE yylval;