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

On Monday 30 August 2010 09:59:53, Jan Kratochvil wrote:
> Hi,
> 
> This is a code cleanup without any compiled code changes.
> 
> 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 see I have chosen the *_t type name again, 

I suggest you don't use _t for this.  Most of our function typedefs
use the *_ftype prefix, a few _func, and only a couple _fn or _t.

Try something like:

$ grep -rn "_ftype)" * | grep -v ChangeLog | grep typedef | wc -l
155

$ grep -rn "_func)" * | grep -v ChangeLog | grep typedef | wc -l
15

...


So, I'd suggest something like:

 find_memory_regions_callback_ftype
 find_memory_regions_ftype
 find_memory_region_callback_ftype
 find_memory_region_ftype

-- 
Pedro Alves


  reply	other threads:[~2010-08-30 10:44 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 [this message]
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
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=201008301143.55582.pedro@codesourcery.com \
    --to=pedro@codesourcery.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