This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Introducing slight binary incompatibility in newer executables?
- To: earnie_boyd at yahoo dot com
- Subject: Re: Introducing slight binary incompatibility in newer executables?
- From: DJ Delorie <dj at delorie dot com>
- Date: Mon, 26 Jun 2000 10:58:12 -0400
- CC: cygwin-developers at sourceware dot cygnus dot com
- References: <20000626003445.27880.qmail@web108.yahoomail.com>
> IMHO, it is, any cygwin-app that is updated now, will have to have
> the updated cygwin1.dll. What other changes are you thinking of?
We bump the middle number when the converse is true - when updating
the DLL means you *must* update the cygwin apps also.
All we're doing with this change is the same thing we've been doing
with all our other changes - adding functionality. This means that
apps built for the new DLL won't work with older DLLs.
If we change or remove functionality, *then* we bump the middle
number, because apps build for the old DLL won't work with the new
DLL. It's only when backward compatibility is broken do we have to
worry about migration.