SY> I'm having a problem with byte-compiling func-menu.el. The defmacro of fume-bomb-proof needs to be eval-when'd. (eval-and-compile (defmacro fume-bomb-proof ...)) should do it if I've got my eval-whens straight. -- 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."

SY> Hi Gang, SY> I'm having a problem with byte-compiling func-menu.el. SY> M-x byte-compile-file under normal circumstances works fine, but under SY> xemacs -vanilla I get: SY> ,---- SY> | While compiling toplevel forms: SY> | !! Symbol's function definition is void ((fume-bomb-proof)) SY> `---- This happens under 21.2, but not 21.1. This is a BUG in XEmacs 21.2! Do not modify func-menu.el! Probably my fault, with the recent changes to the byte-compiler. I will investigate. Martin

SY> * "Martin" == Martin Buchholz <martin(a)xemacs.org&gt; writes: >>SY> Hi Gang, SY> I'm having a problem with byte-compiling func-menu.el. SY> M-x byte-compile-file under normal circumstances works fine, but under SY> xemacs -vanilla I get: SY> ,---- SY> | While compiling toplevel forms: SY> | !! Symbol's function definition is void ((fume-bomb-proof)) SY> `---- Martin> This happens under 21.2, but not 21.1. Martin> This is a BUG in XEmacs 21.2! Do not modify func-menu.el! Martin> Probably my fault, with the recent changes to the byte-compiler. SY> Oops, missed your message by about 1 minute. :-( I've just committed SY> the change to func-menu.el. SY> Will a (eval-and-compile ...) cause problems for 21.1 people? Should SY> I revert the patch or is it safe to leave in? (eval-and-compile ...) is safe and may in fact be the solution I will settle on (i.e. not fixing the byte compiler, despite the change in behavior). Fixing the byte compiler might be too difficult to be worth it. So short term, it's the right thing to do. Martin