From: Eli Zaretskii <eliz@gnu.org>
To: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: New ARI warning Sat Mar 12 01:53:29 UTC 2011
Date: Sun, 13 Mar 2011 19:39:00 -0000 [thread overview]
Message-ID: <E1PyiT1-0005DR-16@fencepost.gnu.org> (raw)
In-Reply-To: <010f01cbe157$aebb5cb0$0c321610$@muller@ics-cnrs.unistra.fr> (pierre.muller@ics-cnrs.unistra.fr)
> From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
> Date: Sun, 13 Mar 2011 09:21:35 +0100
>
> This is the consequence of the two new ARI rules I added:
> http://sourceware.org/ml/gdb-patches/2011-03/msg00654.html
>
> As I just introduced these new rules,
> I felt that it would be cheating to
> use OBVIOUS rule as we normally do to fix
> a ARI regression...
> This is why I will submit shortly two patches
> to remove all those new warnings.
The rule to detect "()" without a "void" is fine, but why on Earth do
we need the other rule, about prototypes like this:
int
foo (bar);
This is a perfectly valid formatting. In your patch, you modify long
prototypes like this as follows:
extern struct hppa_objfile_private *
-hppa_init_objfile_priv_data (struct objfile *objfile);
+ hppa_init_objfile_priv_data (struct objfile *objfile);
But that is not a good idea, because if you type TAB in Emacs on the
line with the function name, Emacs will reindent the name to column
zero. So I expect this rule to annoy us quite a bit, e.g. if someone
reindents a large region.
Can you tell why we need this?
next prev parent reply other threads:[~2011-03-13 10:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 2:17 GDB Administrator
2011-03-13 9:32 ` Pierre Muller
2011-03-13 10:24 ` [RFA] Fix ARI warning about function call in first column (was : New ARI warning Sat Mar 12 01:53:29 UTC 2011) Pierre Muller
2011-03-13 13:42 ` [RFA] Fix ARI warnings about function with no parameters ( " Pierre Muller
2011-03-14 16:03 ` Pierre Muller
2011-03-13 19:39 ` Eli Zaretskii [this message]
2011-03-14 11:26 ` New ARI warning Sat Mar 12 01:53:29 UTC 2011 Pierre Muller
2011-03-14 12:13 ` Eli Zaretskii
2011-03-14 12:34 ` Pedro Alves
2011-03-14 12:34 ` Eli Zaretskii
2011-03-14 12:49 ` Pierre Muller
2011-03-14 13:06 ` Eli Zaretskii
2011-03-14 12:51 ` Eli Zaretskii
2011-03-14 12:52 ` Pierre Muller
2011-03-14 13:16 ` Eli Zaretskii
2011-03-14 12:59 ` Pedro Alves
2011-03-14 13:27 ` Eli Zaretskii
2011-03-14 13:46 ` Pedro Alves
2011-03-14 15:46 ` Pierre Muller
2011-03-19 21:15 ` Mark Kettenis
[not found] ` <18667.385276831$1300008680@news.gmane.org>
2011-03-14 15:54 ` [RFA] Fix ARI warning about function call in first column Tom Tromey
2011-03-14 16:46 ` [RFA-v2] " Pierre Muller
2011-03-14 17:02 ` Tom Tromey
[not found] ` <001401cbe261$5490ec40$fdb2c4c0$%muller@ics-cnrs.unistra.fr>
2011-03-14 17:17 ` Eli Zaretskii
2011-03-14 17:26 ` Pierre Muller
[not found] ` <10281.0550401502$1300122152@news.gmane.org>
2011-03-14 17:39 ` Tom Tromey
2011-03-15 12:19 ` [RFA] Fix formatting in " Pierre Muller
[not found] ` <45563.9187516228$1300186224@news.gmane.org>
2011-03-15 15:42 ` Tom Tromey
2011-03-15 16:01 ` Pierre Muller
[not found] ` <002001cbe269$85ed0e60$91c72b20$%muller@ics-cnrs.unistra.fr>
2011-03-14 21:26 ` Eli Zaretskii
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=E1PyiT1-0005DR-16@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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