From: Richard Copley <rcopley@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>,
Emacs Development <emacs-devel@gnu.org>
Subject: Re: C warning in MSYS2 build
Date: Fri, 6 Oct 2017 18:23:04 +0100 [thread overview]
Message-ID: <CAPM58ojoQBt+cY+DjfbeAtJZE=mhoi41_gDVry-pb_6VvkCRKw@mail.gmail.com> (raw)
In-Reply-To: <E1e0UMU-0001vP-J6@fencepost.gnu.org>
On 6 October 2017 at 16:16, Richard Stallman <rms@gnu.org> wrote:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> > The GCC bug is not fixed yet. etags.c confused GCC by using an
> > assignment inside an 'if' expression, which is contrary to the usual GNU
> > style, and last year I worked around the GCC bug by changing etags.c to
> > use a cleaner style. I notice that indent.c also has an assignment
> > inside an 'if' expression that is relevant to these warnings. Richard,
> > does it help to recode indent.c to use the usual GNU style, as in the
> > attached patch?
>
> I don't understand the question.
Paul was asking me to test the attached patch.
> An assignment inside an if condition is somewhat ugly,
> and moving the assignment out of the code is in general
> a good thing for clarity. So by all means do it.
That's not the proposal. You're free to read the patch if you wish.
> If that works around a GCC bug, that is good -- but the bug
> still needs to be fixed.
Indeed, but fortunately the impact is low.
prev parent reply other threads:[~2017-10-06 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 17:44 C warning in MSYS2 build Richard Copley
2017-10-05 18:54 ` Eli Zaretskii
2017-10-05 19:32 ` Paul Eggert
2017-10-05 20:08 ` Richard Copley
2017-10-05 22:44 ` Paul Eggert
2017-10-06 15:16 ` Richard Stallman
2017-10-06 17:23 ` Richard Copley [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPM58ojoQBt+cY+DjfbeAtJZE=mhoi41_gDVry-pb_6VvkCRKw@mail.gmail.com' \
--to=rcopley@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.