From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFA] (cli/cli-cmds.c) ARI fix: Avoid assignment inside if statement
Date: Sun, 23 Dec 2012 21:58:00 -0000 [thread overview]
Message-ID: <001801cde158$8b8ba990$a2a2fcb0$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <837go8pnxn.fsf@gnu.org>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Eli Zaretskii
> Envoyé : dimanche 23 décembre 2012 20:29
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: [RFA] (cli/cli-cmds.c) ARI fix: Avoid assignment inside if
> statement
>
> > From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
> > Date: Sun, 23 Dec 2012 19:59:49 +0100
> >
> > Looks almost obvious, but
> > as it's the first of that kind,
> > I thought I will send it as RFA nonetheless...
> >
> > Can similar changes be committed as obvious?
> > They usually require some formatting changes,
> > but generated behavior should not change.
> >
> >
> > Pierre Muller
> > as ARI maintainer
> >
> >
> > 2012-12-20 Pierre Muller <muller@sourceware.org>
> >
> > ARI fixes: Assignment within if rule.
> > * cli/cli-cmds.c (shell_escape): Do not set variable value
inside
> > if statement.
> > (edit_command): Likewise.
>
> Since when is that bad C, so much so that we would need to enforce it?
Eli, as you know,
I am not a C specialist at all...
But I didn't invent that rule either.
This rule part of gdb_ari.sh since it's introduction in CVS ss repository
back in 2002.
It's probably now your chance to challenge this rule...
I would tend to agree that an assignment should be a statement on it's
own, but you could rightly consider this as a 'pascal' language
preference!
Pierre Muller
both ARI and pascal language support maintainer!
next prev parent reply other threads:[~2012-12-23 21:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001201cde13f$af3ad4b0$0db07e10$%muller@ics-cnrs.unistra.fr>
2012-12-23 19:29 ` Eli Zaretskii
2012-12-23 21:58 ` Pierre Muller [this message]
2012-12-23 22:28 ` Sergio Durigan Junior
2012-12-24 4:11 ` Joel Brobecker
2012-12-23 22:28 ` Andreas Schwab
2012-12-24 3:41 ` Eli Zaretskii
2012-12-24 10:17 ` Andreas Schwab
2013-01-10 12:28 ` Pierre Muller
2013-01-11 4:29 ` Joel Brobecker
2012-12-23 19:00 Pierre Muller
2012-12-24 4:17 ` Joel Brobecker
2012-12-24 10:22 ` Andreas Schwab
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='001801cde158$8b8ba990$a2a2fcb0$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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