[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Change in bytecomp.el breaks Gnus
From: |
Miles Bader |
Subject: |
Re: Change in bytecomp.el breaks Gnus |
Date: |
Mon, 15 Nov 2004 18:38:50 -0500 |
User-agent: |
Mutt/1.3.28i |
On Mon, Nov 15, 2004 at 06:28:58PM -0500, Stefan Monnier wrote:
> > Couldn't such macros be wrapped in `eval-when-compile' (I forgot the exact
> > name, but ...)?
>
> Some are wrapped. Some could be. But those like the setf methods generated
> by `defstruct' can't.
Hmmm. Well, I'd say just rewrite defstruct to not use cl functions (I'm sure
cl fans will bitch about how horrible that is, but cl is a part of emacs, it
should cater to Emacs' idiosyncrasies where possible).
Anyway, wouldn't such wrapping address at least majority of such cases? The
reason I'm going on about this is that I think it's a much more
understandable way of fixing such warnings (in that it directly shows what's
going on) than using `with-no-warnings' (which is a pretty blunt tool).
-Miles
--
80% of success is just showing up. --Woody Allen
- Re: Change in bytecomp.el breaks Gnus, (continued)
- Re: Change in bytecomp.el breaks Gnus, Luc Teirlinck, 2004/11/14
- Re: Change in bytecomp.el breaks Gnus, Stefan Monnier, 2004/11/14
- Re: Change in bytecomp.el breaks Gnus, Richard Stallman, 2004/11/15
- Re: Change in bytecomp.el breaks Gnus, Stefan Monnier, 2004/11/15
- Re: Change in bytecomp.el breaks Gnus, Miles Bader, 2004/11/15
- Re: Change in bytecomp.el breaks Gnus, Stefan Monnier, 2004/11/15
- Re: Change in bytecomp.el breaks Gnus,
Miles Bader <=
- Re: Change in bytecomp.el breaks Gnus, Stefan Monnier, 2004/11/15
- Re: Change in bytecomp.el breaks Gnus, Luc Teirlinck, 2004/11/15
- Re: Change in bytecomp.el breaks Gnus, Nick Roberts, 2004/11/15
- Re: Change in bytecomp.el breaks Gnus, Luc Teirlinck, 2004/11/15
- Re: Change in bytecomp.el breaks Gnus, Luc Teirlinck, 2004/11/15
- Re: Change in bytecomp.el breaks Gnus, Richard Stallman, 2004/11/16