From: Juanma Barranquero <lekktu@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: Dan Nicolaescu <dann@gnu.org>, 6740@debbugs.gnu.org
Subject: bug#6740: Spurious byte compiler warnings
Date: Wed, 28 Jul 2010 00:57:04 +0200 [thread overview]
Message-ID: <AANLkTikdVKf70_nbaBbYPyjUE7iRZ1RXX8ybFJEvaXQe@mail.gmail.com> (raw)
In-Reply-To: <20100727212328.GD2280@muc.de>
On Tue, Jul 27, 2010 at 23:23, Alan Mackenzie <acm@muc.de> wrote:
> It's a bug that the error message is repeated, at the very least.
Yes, likely.
> And
> the message is most assuredly false because (featurep 'cc-fix) isn't
> always false - for example when it's run under XEmacs.
Not, in code byte-compiled for Emacs it is always false because
(featurep 'xemacs) is false. That means that optimized bytecode is not
portable to XEmacs. But I don't think it was before (for a long time).
> At the very least, emitting such arcane warnings is unhelpful. Are there
> any circumstances in which such a warning might help a hacker improve his
> code? Surely we aren't in the business of making it difficult to adapt
> code for XEmacs?
You make it appear as it if were an attempt to warn about using
XEmacs-specific code, but it is not, as Dan has pointed out. The
warning is generic, the result of
(and X (featurep 'xemacs) Y Z...) => (prog (and X) nil) => (prog X
nil) ; IIUC the comments in byte-opt.el...
from whence, "value returned from X is unused".
> I think it's clear, the only code containing (featurep 'xemacs) is
> portable code.
The code is portable. The .elc is not.
Juanma
next prev parent reply other threads:[~2010-07-27 22:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 20:06 bug#6740: Spurious byte compiler warnings Alan Mackenzie
2010-07-27 20:26 ` Dan Nicolaescu
2010-07-27 21:23 ` Alan Mackenzie
2010-07-27 22:57 ` Juanma Barranquero [this message]
2010-07-28 17:49 ` Alan Mackenzie
2010-07-28 17:56 ` Juanma Barranquero
2010-07-28 19:45 ` Alan Mackenzie
2010-07-28 19:54 ` Juanma Barranquero
2010-07-28 23:00 ` Dan Nicolaescu
2010-07-29 20:24 ` Alan Mackenzie
2010-07-29 20:36 ` Juanma Barranquero
2010-07-27 21:40 ` Stefan Monnier
2020-11-19 4:25 ` Stefan Kangas
2020-11-24 6:40 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTikdVKf70_nbaBbYPyjUE7iRZ1RXX8ybFJEvaXQe@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=6740@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=dann@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).