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

> Currently
> 	int (*func) (CORE_ADDR, unsigned long, int, int, int, void *),
> 
> is used on many places to find memory regions.  Changing the prototype
> requires even changes on places which would not have to be changed otherwise.

I think we should generalize this idea and use function types whenever
possible. Using a function type, for instance, makes it easier for
someone to find the description of that function.  I had that problem
recently, and it took me a long time to find what I was looking for.

I also believe that we should explicitly name the parameters in the
function type declaration.  I think this is important, because I think
that this practice would have helped prevent an unfortunate regression
(filename/fullname confusion in MI command). We should name the parameters
so that we know which parameter is what.  And that also helps IMO writing
the function description.

-- 
Joel


  parent reply	other threads:[~2010-08-30 14:15 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 [this message]
2010-08-30 14:25   ` Jan Kratochvil
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=20100830141454.GG2986@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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