Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Code cleanup: Make function typedef for find memory region
Date: Mon, 30 Aug 2010 14:25:00 -0000	[thread overview]
Message-ID: <20100830142507.GA1356@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <20100830141454.GG2986@adacore.com>

On Mon, 30 Aug 2010 16:14:54 +0200, Joel Brobecker wrote:
> I also believe that we should explicitly name the parameters in the
> function type declaration.

I try to do that whenever I can, I am for making it a part of patch reviews.

When we are at the rules:

I am also for requiring comment to be placed at the function definition and
not at its declaration.  Using tag jumps one will never find the declaration
and I have considered these functions to have no comment (randomly found now
simple_displaced_step_copy_insn, it was a different function I had the problem
with).

I am also for forbidding putting comments there at both places as such way
they get inconsistent soon or they differ etc. (randomly found init_type).


Regards,
Jan


  reply	other threads:[~2010-08-30 14:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30  9:00 Jan Kratochvil
2010-08-30 10:44 ` Pedro Alves
2010-08-30 14:10   ` Joel Brobecker
2010-08-31 17:27   ` Jan Kratochvil
2010-08-31 18:12     ` Pedro Alves
2010-08-30 14:15 ` Joel Brobecker
2010-08-30 14:25   ` Jan Kratochvil [this message]
2010-08-30 14:58     ` Joel Brobecker
2010-08-30 15:04       ` Jan Kratochvil
2010-08-30 18:38     ` Tom Tromey
2010-08-31 13:02       ` Jan Kratochvil
2010-08-31 16:51         ` Tom Tromey
2010-08-31 17:13           ` Joel Brobecker
2010-08-31 17:33 ` Joel Brobecker
2010-08-31 18:09   ` 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=20100830142507.GA1356@host1.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.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