This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [wip] BFD from an arbitrary object; Was: provide pass-throughvalue in bfd_elf_bfd_from_remote_memory


On Fri, Feb 13, 2004 at 09:34:03PM -0500, Ian Lance Taylor wrote:

Andrew Cagney <cagney@gnu.org> writes:

> - is the theory ok?

Looks good to me.


I think it's a good idea too.  I can't see the sense in those bread,
bwrite etc. names though.  Why not simply read, write etc.?  bfd_bread
and bfd_bwrite were added when I needed to make changes to bfd_read
and bfd_write, but thought it a good idea to keep the old functions
for backward compatibility.  Let's not perpetuate silly names.
Hmm, unless some system #define's read, write etc.

Some history. It started out with "fread" et.al. (since the interface mimics "fread" and not "read"). I switched to bread cos at one stage the vector include fileno() and that was a macro ...


Andrew



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]