Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Stan Shebs'" <stan@codesourcery.com>,
	       "'Joel Brobecker'" <brobecker@adacore.com>
Cc: "'Pedro Alves'" <pedro@codesourcery.com>, <gdb-patches@sourceware.org>
Subject: RE: [ARI] Remove all editCase warnings
Date: Wed, 05 May 2010 21:03:00 -0000	[thread overview]
Message-ID: <002a01caec96$4f7e3080$ee7a9180$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <4BE1A7BA.9000803@codesourcery.com>



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Stan Shebs
> Envoyé : Wednesday, May 05, 2010 7:16 PM
> À : Joel Brobecker
> Cc : Pierre Muller; 'Pedro Alves'; gdb-patches@sourceware.org
> Objet : Re: [ARI] Remove all editCase warnings
> 
> Joel Brobecker wrote:
> >>  static void
> >> -ada_remove_Xbn_suffix (const char *encoded, int *len)
> >> +ada_remove_Xbn_suffix ( /* ARI: editCase function */
> >> +		       const char *encoded, int *len)
> >>
> >
> > I would rather have:
> >
> > ada_remove_Xbn_suffix /* ARI: editCase function */
> >   (const char *encoded, int *len)
> >
> 
> I frequently grep for "foo (", so this would cause the function to be
> overlooked.  But, fewer grep results means less work when changing the
> code... :-)
  That is also what is done inside gdb_ari.sh,
which means that it is not possible to fulfill
Joel's request.

  Eliminating the ' (' in the pattern would probably lead to lots of
false positive.

  I don't know what to think now...

  I fully agree that this is not one of the important 
rules, but I hoped that clearing up more fields would make
the ARI more efficient.
  Simply removing the rule is not better than 
leaving the source code unchanged in my opinion,
but I will follow the consensus if we reach one.

  
Pierre



  reply	other threads:[~2010-05-05 21:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 23:25 Pierre Muller
2010-05-04 23:32 ` Stan Shebs
2010-05-04 23:44 ` Pedro Alves
2010-05-04 23:51   ` Michael Snyder
2010-05-05  9:03   ` Pierre Muller
2010-05-05 14:54     ` Joel Brobecker
2010-05-05 15:11     ` Pedro Alves
2010-05-05 16:09       ` Pierre Muller
2010-05-05 16:55         ` Joel Brobecker
2010-05-05 17:15           ` Stan Shebs
2010-05-05 21:03             ` Pierre Muller [this message]
2010-05-06 18:10               ` Joel Brobecker
2010-05-05 18:34           ` Daniel Jacobowitz
2010-05-05 18:37             ` 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='002a01caec96$4f7e3080$ee7a9180$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=stan@codesourcery.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox