Re: eval-when, eval-when-compile

mb> Because I'm excessively careful, I've done a similar exercise mb> in the past. You want to compare two elc files for mb> differences in the generated bytecode. mb> Here's my program elc-cmp (additional hacking may be mb> required): SJT> Not too much. Time to quit, though; I'll send the files tomorrow. SJT> The differences found were in (core) lisp/bytecomp.elc (I haven't SJT> checked if it is merely the patch), and (packages) SJT> gnus/gnus-start.elc, calc/calc.elc, w3/w3-display.elc, and SJT> w3/w3-parse.elc. Thanks. This is quite useful. I expected more. SJT> I will say, as an aside, that the last few months of hacking on the SJT> package build process have been a massive step backward. Several SJT> targets that used to work for me now fail. It is also certain that an SJT> attempt to start from the bare metal with CVS checkouts of xemacs and SJT> xemacs-packages will fail (several packages require an installed SJT> package hierarchy to be available), but I don't know how screwed up SJT> that is yet. This also used to work for me, with the caveat that some SJT> tweaking was required to get VM and skk to build their manuals. SJT> :-( Paging Steve Youngs... I have certain release criteria for 21.2 beta, like successful C++ compiles and clean `make check's. I would hope package releases would have similar release critieria. Martin