From: Dan Nicolaescu <dann@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 6740@debbugs.gnu.org
Subject: bug#6740: Spurious byte compiler warnings
Date: Wed, 28 Jul 2010 19:00:11 -0400 [thread overview]
Message-ID: <yxqfwz3tdok.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <AANLkTinPrue70-0fO0Z+S=594dok0CmzZfo5WKgf22xg@mail.gmail.com> (Juanma Barranquero's message of "Wed\, 28 Jul 2010 21\:54\:04 +0200")
Juanma Barranquero <lekktu@gmail.com> writes:
> On Wed, Jul 28, 2010 at 21:45, Alan Mackenzie <acm@muc.de> wrote:
>
>>
>> "`(featurep 'xemacs)' has been translated to nil"
>
> ????
>
> That's worse that what you're complaining now; every use of (featurep
> 'xemacs) in the sources would produce warnings!
Exactly, and it would defeat the purpose of optimizing away
(featurp 'xemacs) (and (featurep 'emacs): being able to have a single source base that
works on both platforms, and it can be compiled warning free.
next prev parent reply other threads:[~2010-07-28 23:00 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
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 [this message]
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=yxqfwz3tdok.fsf@fencepost.gnu.org \
--to=dann@gnu.org \
--cc=6740@debbugs.gnu.org \
--cc=lekktu@gmail.com \
/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).