From: Miles Bader <miles@gnu.org>
Cc: teirllm@dms.auburn.edu, emacs-pretest-bug@gnu.org, ding@gnus.org,
yamaoka@jpl.org
Subject: Re: Change in bytecomp.el breaks Gnus
Date: Mon, 15 Nov 2004 18:38:50 -0500 [thread overview]
Message-ID: <20041115233850.GB16890@fencepost> (raw)
In-Reply-To: <jwvis86els2.fsf-monnier+emacs@gnu.org>
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
next prev parent reply other threads:[~2004-11-15 23:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877jouepy8.fsf@telia.com>
[not found] ` <b9yd5ymkq11.fsf@jpl.org>
2004-11-11 7:40 ` Katsumi Yamaoka
2004-11-11 11:18 ` Katsumi Yamaoka
2004-11-11 17:45 ` Luc Teirlinck
2004-11-11 21:55 ` Stefan
2004-11-11 22:41 ` Luc Teirlinck
2004-11-11 22:54 ` Luc Teirlinck
2004-11-12 0:22 ` Katsumi Yamaoka
2004-11-12 3:57 ` Stefan Monnier
2004-11-12 4:30 ` Katsumi Yamaoka
2004-11-13 23:03 ` Stefan
2004-11-14 0:14 ` Katsumi Yamaoka
2004-11-14 5:21 ` Stefan
2004-11-14 6:10 ` Katsumi Yamaoka
2004-11-14 6:36 ` Stefan
2004-11-14 13:44 ` Katsumi Yamaoka
2004-11-14 17:29 ` Luc Teirlinck
2004-11-14 19:17 ` Stefan Monnier
2004-11-15 14:00 ` Richard Stallman
2004-11-15 15:36 ` Stefan Monnier
2004-11-15 23:22 ` Miles Bader
2004-11-15 23:28 ` Stefan Monnier
2004-11-15 23:38 ` Miles Bader [this message]
2004-11-15 23:44 ` Stefan Monnier
2004-11-15 23:57 ` Luc Teirlinck
2004-11-16 1:29 ` Nick Roberts
2004-11-16 1:49 ` Luc Teirlinck
2004-11-16 2:19 ` Luc Teirlinck
2004-11-16 16:49 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041115233850.GB16890@fencepost \
--to=miles@gnu.org \
--cc=ding@gnus.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=teirllm@dms.auburn.edu \
--cc=yamaoka@jpl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).