Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Doug Evans'" <dje@google.com>, <gdb-patches@sourceware.org>
Subject: RE: New ARI warning Wed May 26 01:54:51 UTC 2010
Date: Wed, 26 May 2010 09:06:00 -0000	[thread overview]
Message-ID: <000901cafcaa$80ddf470$8299dd50$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <AANLkTin1WZ2kXmsG-BjRKD8LN1_LVZIvZrBqtpqHxpJO@mail.gmail.com>



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Doug Evans
> Envoyé : Wednesday, May 26, 2010 4:48 AM
> À : gdb-patches@sourceware.org
> Objet : Re: New ARI warning Wed May 26 01:54:51 UTC 2010
> 
> On Tue, May 25, 2010 at 6:54 PM, GDB Administrator
> <gdbadmin@sourceware.org> wrote:
> > 1084a1085
> >> gdb/python/py-cmd.c:192: gettext: _ markup: All messages should be
> marked up with _.
> > gdb/python/py-cmd.c:192:        error ("%s", msg);
> >
> 
> There were already a couple of uses of error ("%s", ...) so I figured
> it was safe.

  Of course, translation of "%s" into another language does make sense!
 
> OOC, is this why source.c has:
> 
> error (("%s"), msg);

  I suspect that the braces around "%s" are exactly here for that reason:
they avoid getting this ARI report.
  Does anyone have another idea of the utility of such a wrapping?

  I could probably try to improve the ARI rule 
so that it does not complain if the string is just "%s",
but I would like to be sure that I am not missing some information here.

Pierre Muller
as ARI maintainer.


  reply	other threads:[~2010-05-26  8:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26  2:47 GDB Administrator
2010-05-26  4:44 ` Doug Evans
2010-05-26  9:06   ` Pierre Muller [this message]
2010-06-02 23:08     ` Joel Brobecker

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='000901cafcaa$80ddf470$8299dd50$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=dje@google.com \
    --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