From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Clifton To: Alan Modra , Andrew Cagney 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 Message-id: References: <20010905145037.K13524@bubble.sa.bigpond.net.au> <3B965696.70401@cygnus.com> <20010905122109.A17937@redhat.com> <3B96C2B2.8050409@cygnus.com> <20010906112244.C24712@bubble.sa.bigpond.net.au> <3B96E752.8030205@cygnus.com> X-SW-Source: 2001-09/msg00073.html 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