From: Dave L. <d....@dl...> - 2004-01-16 01:03:50
|
Martin Stjernholm <ma...@ly...> writes: > It's a symptom of lack of control facilities in the byte compiler, at > least up to and including Emacs 21.3 (I haven't yet investigated the > byte compiler changes in cvs). I can't remember what went in where, but I think the features in the development version of the compiler are sufficient for this (modulo spurious warnings about CL functions that I don't understand). I put in what I thought was necessary/sufficient from experience. > (There are apparently changes in > the cvs version of the byte compiler that make this not work as > intended since there are numerous warnings there.) That's the sort of thing I mean about working against the compiler. There have been a fair number of bugs in Gnus &c due to silencing errors which were meaningful. > I looked at Gnus a bit before I came up with cc-bytecomp. As far as I > remember it didn't address the issues above at all. I said I spoke from experience with it, and I can't see that it needs anything more than understanding and care from developers (who unfortunately don't seem to be much interested in what's shipped with Emacs). I think the thing about using the wrong path is a non-issue. In the Gnus files I had time to work on some months ago, as far as I remember I cleanly eliminated all the compiler warnings when using the then-development Emacs (without any of its ill-advised build stuff). Since XEmacs doesn't appear to have such facilities, you guard use of XEmacs stuff rather than Emacs, of course. |