Re: eval-when, eval-when-compile

mb> Here's my program elc-cmp (additional hacking may be mb> required): me> The differences found were in (core) lisp/bytecomp.elc (I me> haven't checked if it is merely the patch), and (packages) me> gnus/gnus-start.elc, calc/calc.elc, w3/w3-display.elc, and me> w3/w3-parse.elc. SJT> The calc/calc.elc turns out to be a false alarm; calc kept a build SJT> time-stamp in a form Martin's script didn't catch. SJT> A tarball containing the five files (including calc) that showed SJT> differences in .el, .elc pre-Martin-patch, and .elc post-Martin-patch SJT> forms is available at SJT> http://turnbull.sk.tsukuba.ac.jp/Tools/XEmacs/bytecomp-diffs.tar.gz I've looked at these, and they show that unfortunately, this patch is not yet ready for prime time. I should have mentioned that you should have also diffed all the byte-compiler warnings pre and post. They will show significant differences. One problem is that (eval-when-compile (defvar foo)) (defun bar () foo) should not give a warning. It does. I'm looking at the byte-code diffs - they seems to be harmless, based on whether source or bytecode is inlined - only a very very small possible performance difference. Martin