From: Eric Christopher <echristo@redhat.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: binutils@sources.redhat.com
Subject: Re: RFC: Short circuit bfd_map_over_sections
Date: Fri, 30 Apr 2004 00:29:00 -0000 [thread overview]
Message-ID: <1083284421.3591.17.camel@dzur.sfbay.redhat.com> (raw)
In-Reply-To: <20040430001811.GB28069@lucon.org>
> That is fine. What should we call it? bfd_run_over_sections,
> bfd_call_over_sections, bfd_call_on_sections, ...
I like call_on or call_over. If I had to choose I think I like call_on
more.
run_over sounds painful :)
-eric
--
Eric Christopher <echristo@redhat.com>
next prev parent reply other threads:[~2004-04-30 0:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 0:12 H. J. Lu
2004-04-30 0:15 ` Ian Lance Taylor
2004-04-30 0:20 ` H. J. Lu
2004-04-30 0:29 ` Eric Christopher [this message]
2004-04-30 1:33 ` Ian Lance Taylor
2004-04-30 1:36 ` H. J. Lu
2004-04-30 7:29 ` Nick Clifton
2004-04-30 4:15 ` Alan Modra
2004-04-30 5:25 ` H. J. Lu
2004-04-30 17:53 ` PATCH: Add bfd_get_section_by_name_if H. J. Lu
2004-05-01 14:20 ` Alan Modra
2004-05-01 15:19 ` H. J. Lu
2004-05-02 13:32 ` Alan Modra
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=1083284421.3591.17.camel@dzur.sfbay.redhat.com \
--to=echristo@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=hjl@lucon.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).