This is the mail archive of the cygwin-developers@sourceware.cygnus.com mailing list for the Cygwin project.


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

Introducing slight binary incompatibility in newer executables?


I am contemplating a change to the cygwin crt0 code that will move some
more shared data into the DLL.  I can make the DLL backwards compatible
with older executables but making the new executables backwards
compatible with older DLLs is not as easy.  So:

DLL		"New" exe	"Old" exe
<1.1.3		doesn't work	works
>1.1.3		works		works

What's the consensus on this?  We've discussed breaking binary
compatibility from time to time.  This is not precisely that bad
but it may generate some confused mailing list traffic.

The error will be something like "entry point cygwin_user_data not
found".  The solution will be simple: "Upgrade your DLL".

The benefits are smaller user programs and a slightly faster cygwin DLL.

cgf

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