From: Paul Eggert <eggert@cs.ucla.edu>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master b7fa6b1 1/4: Simplify use of FOR_EACH_TAIL
Date: Tue, 7 Feb 2017 14:18:33 -0800 [thread overview]
Message-ID: <1cb52f4a-16b3-9ace-62fe-9ff419383aa1@cs.ucla.edu> (raw)
In-Reply-To: <E1cbDeJ-0003mc-Vy@fencepost.gnu.org>
On 02/07/2017 01:50 PM, Richard Stallman wrote:
> Why should we restrict ourselves to cater to Clang?
It's not just Clang, it's any compiler that interprets that part of the
C standard strictly. I have heard that Visual Studio is like Clang here,
and I wouldn't be surprised if other compilers were in the strict camp.
Since there is a short and clean workaround for this that does not hurt
performance, it should be OK for Emacs to use the workaround. After all,
Emacs has localized workarounds elsewhere for proprietary compilers like
AIX xlc, HP-UX cc and Oracle Studio cc.
prev parent reply other threads:[~2017-02-07 22:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170205213033.19755.8264@vcs.savannah.gnu.org>
[not found] ` <20170205213034.20306220171@vcs.savannah.gnu.org>
2017-02-06 1:19 ` [Emacs-diffs] master b7fa6b1 1/4: Simplify use of FOR_EACH_TAIL Stefan Monnier
2017-02-06 5:23 ` Paul Eggert
2017-02-06 15:37 ` Eli Zaretskii
2017-02-07 1:35 ` Paul Eggert
2017-02-07 15:32 ` Eli Zaretskii
2017-02-06 17:38 ` Davis Herring
2017-02-07 1:04 ` Paul Eggert
2017-02-07 20:45 ` Johan Bockgård
2017-02-07 21:50 ` Richard Stallman
2017-02-07 22:18 ` Paul Eggert [this message]
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=1cb52f4a-16b3-9ace-62fe-9ff419383aa1@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rms@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).