Re: need for flag for incompatible-changes

[Paul Koning <pkoning at xedia dot com>]

>>>>> "Joe" == Joe Buck <jbuck@Synopsys.COM> writes:

 Joe> On Thu, Jan 29, 1998 at 09:24:01AM -0500, Paul Koning wrote:
 >> > Clearly, if the names of the functions change (due to
 >> namespaces) but > their calling conventions did not (same argument
 >> types etc.) then the > linker can map old names to new names if it
 >> is told to do so.

 Joe> rth writes:
 >> You know, at some point it becomes much easier to just force
 >> people (and companies) to rebuild the libraries.

 Joe> I agree.  The only reason for some kind of name-munging trick
 Joe> would be to support old executables that are available only in
 Joe> binary form.  That's a job that probably isn't worth doing by
 Joe> the egcs team.  If a specific customer has a need for it, it
 Joe> might be a nice way for some consultant to make a bit of money.

That sounds reasonable.  But for it to be possible, the compiler has
to supply the raw data, i.e., it has to emit the version data into the
object files.

	paul