[Horsley Tom <Tom.Horsley@ccur.com>] RE: Bombs loading some XEmacs-compiled .elc's into NTEmacs

Jari> What do you think about adding version information? We can't "add version information" because it's already there (those are not control characters, I edited them): ;ELC^T^＠^＠^＠ ;;; compiled by steve(a)tleepslib.sk.tsukuba.ac.jp on Fri Jan 19 13:27:26 2001 ;;; from file /home/steve/Projects/XEmacs/Builds/21.2/lisp/subr.el ;;; emacs version 21.2 (beta40) "Persephone" XEmacs Lucid. ;;; bytecomp version 2.27 XEmacs; 2000-09-12. ;;; optimization is on. ;;; this file uses opcodes which do not exist in Emacs 19. What more can you ask for? The optimizer doesn't add any new codes, so having a version for it would be nice but not essential. Rather than depend on the version header, the loader or the byte-code interpreter (maybe both, for maximum flexibility) should scan for illegal byte codes and behave appropriately when they are detected. This allows a flexible response to known but unimplemented byte codes, and also allows the loader to respond reasonably to files that are simply corrupt. It probably would be nice to have an option to automatically back up to the .el, and either load it directly or byte-compile-and-load it. But this is GNU's problem, not ours. We can't fix their loader/interpreter. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."