Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-ID: <20000625221009.25276.qmail@web118.yahoomail.com> Date: Sun, 25 Jun 2000 15:10:09 -0700 (PDT) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: Re: Introducing slight binary incompatibility in newer executables? To: cygwin-developers AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- Chris Faylor wrote: > 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. > I'm in favor of anything that adds speed up. I would suggest a final release of the current dll (a 1.1.4) and to increment the minor version so that we would get 1.3.0. Cheers, ===== --- Earnie Boyd: __Cygwin: POSIX on Windows__ Cygwin Newbies: __Minimalist GNU for Windows__ Mingw32 List: Mingw Home: __________________________________________________ Do You Yahoo!? Get Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/