Ar an chéad lá de mí Lúnasa, scríobh Vin Shelton: invalid_byte_code_error _is_ an alternate return path from the routine in question, and it was that I was worried about. Hmm--the same reasoning applies to leaking memory as a result of invalid_byte_code_error being called before xfree(), but more so, since the only people likely to specify invalid byte code to the interpreter are either working on the interpreter or have just loaded a GNU Emacs byte-compiled file. -- Santa Maradona, priez pour moi!