From: Nick Clifton <nickc@cambridge.redhat.com>
To: Alan Modra <amodra@bigpond.net.au>, Andrew Cagney <ac131313@cygnus.com>
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: bfd_read and bfd_write
Date: Thu, 06 Sep 2001 10:33:00 -0000 [thread overview]
Message-ID: <m3vgiwql7m.fsf@north-pole.nickc.cambridge.redhat.com> (raw)
In-Reply-To: <3B96E752.8030205@cygnus.com>
Hi Andrew, Hi Alan,
> could i suggest taking a step back and deciding what bfd's policy is
> going to be on public / external interfaces. remember, bfd is a
> library used by more than gdb and the other code immediately to hand.
> i don't think changing public / external interfaces should be taken
> lightly
I agree. In this case since we are changing the interface to bfd we
ought to take some time to give other users of the library a chance to
upgrade their software.
I like the idea of adding the new interface, with new function names,
and a warning message being generated if the old interface is used, as
part of the current CVS sources/forthcoming release. Then in the
release after that, we can remove the old interface.
It takes longer this way I know, but I think that we ought to give
other binary tool developers a chance to change their software.
Cheers
Nick
next prev parent reply other threads:[~2001-09-06 10:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 22:20 Alan Modra
2001-09-05 9:45 ` Andrew Cagney
2001-09-05 12:21 ` Richard Henderson
2001-09-05 17:26 ` Andrew Cagney
2001-09-05 18:52 ` Alan Modra
2001-09-05 20:03 ` Andrew Cagney
2001-09-06 10:33 ` Nick Clifton [this message]
2001-09-18 3:27 ` Alan Modra
2001-09-19 11:58 ` Andrew Cagney
2001-09-20 9:52 ` Andrew Cagney
2001-09-05 23:15 ` Andreas Jaeger
2001-09-06 0:01 ` Alan Modra
2001-09-05 20:13 ` Hans-Peter Nilsson
2001-09-05 20:30 ` Alan Modra
2001-09-08 22:42 ` Jim Blandy
2001-09-09 7:24 ` Hans-Peter Nilsson
2001-09-10 9:51 ` Ian Lance Taylor
2001-09-10 17:56 ` Hans-Peter Nilsson
2001-09-10 18:04 ` Ian Lance Taylor
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=m3vgiwql7m.fsf@north-pole.nickc.cambridge.redhat.com \
--to=nickc@cambridge.redhat.com \
--cc=ac131313@cygnus.com \
--cc=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@sources.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