From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>,
gdb-patches <gdb-patches@sourceware.org>,
Cary Coutant <ccoutant@google.com>
Subject: Re: [PATCH] Fix Gold/strip discrepancies for PR 11786
Date: Tue, 05 Nov 2013 18:01:00 -0000 [thread overview]
Message-ID: <CADPb22Tcg9g=pCG1q07hK6DkRnTQop7bZynqnoN+upiuDBWsZA@mail.gmail.com> (raw)
In-Reply-To: <20131105172219.GA21529@host2.jankratochvil.net>
On Tue, Nov 5, 2013 at 9:22 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Tue, 05 Nov 2013 18:04:38 +0100, Doug Evans wrote:
>> I'm not sure how to read this.
>
> Primarily I do not understand if you really defend "()". "()" is wrong and
> obsolete syntax. Reason is that it does not check against passed parameters,
> making bugs more difficult to catch and therefore the code expensive to
> maintain.
All I'm asking for is clarity and consistency.
[I'm not asking for perfection, but IWBN to make sure we're all on the
same page.]
> The real bug is that gdb/testsuite/ does not use the same CFLAGS like gdb/
> does, including -Wmissing-prototypes.
>
> It would be nice to enable it there one day. But nowadays nobody is going to
> fix all the gdb/testsuite/ sources to make them compliant. But it is not
> right to (1) make the testsuite code more expensive to maintain,
> (2) needlessly different from the main GDB codebase code, (3) making the
> future work of enabling -Wmissing-prototypes for gdb/testsuite/ more expensive
> (if it ever happens).
New tests go in all the time that are needlessly different from GDB.
>> It's ok by me, but it seems to me it's not a requirement today as
>> there are plenty of existing examples,
>
> Any existing code should be irrelevant, existing GDB code base is in a worse
> state than what should be required for new commits.
If the decision is to be more strict with the rules for testcases
that's fine by me.
Let's write it down, then discussions like these will become a *lot* shorter.
>> including recent ones.
>
> This is worse, I am aware of it. Just I do not want to spend more time
> catching such nitpicks when GDB has in several orders of magnitude more
> serious problems.
We spend time pointing out rule violations all the time.
Why is this any different?
Point (3) above says don't make the problem worse, but if I hadn't
raised this issue I'm quite sure tests will continue to go in that
violate any or all of 1,2,3.
> Discussing such a clear thing like that "()" is forbidden
> seems also as a loss of time to me. C++ even does not know K&R prototype
> anymore so it will not even be possible in GDB anymore in some time,
> hopefully.
We also spend time discussing things from time to time. Why should
this be any different?
next prev parent reply other threads:[~2013-11-05 17:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 23:26 Doug Evans
2013-10-30 23:57 ` Doug Evans
2013-10-31 16:42 ` Jan Kratochvil
2013-11-04 22:38 ` Doug Evans
2013-11-04 23:04 ` Cary Coutant
2013-11-05 3:42 ` Tom Tromey
2013-11-05 17:22 ` Doug Evans
2013-11-05 17:23 ` Jan Kratochvil
2013-11-05 18:01 ` Doug Evans [this message]
2013-11-05 18:13 ` Jan Kratochvil
2013-11-06 21:16 ` Doug Evans
2013-11-06 21:28 ` Jan Kratochvil
2013-11-07 1:05 ` Stan Shebs
2013-11-07 18:01 ` Doug Evans
2013-11-07 19:03 ` Jan Kratochvil
2013-11-08 17:57 ` Doug Evans
2013-11-08 19:17 ` Jan Kratochvil
2013-11-12 18:46 ` Doug Evans
2013-11-12 19:58 ` Jan Kratochvil
2013-11-12 22:05 ` Doug Evans
2013-11-05 17:32 ` Tom Tromey
2013-11-05 17:32 ` Pedro Alves
2013-11-05 17:04 ` Jan Kratochvil
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='CADPb22Tcg9g=pCG1q07hK6DkRnTQop7bZynqnoN+upiuDBWsZA@mail.gmail.com' \
--to=dje@google.com \
--cc=ccoutant@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@redhat.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