delorie.com/archives/browse.cgi | search |
From: | noer AT cygnus DOT com (Geoffrey Noer) |
Subject: | Re: Why is cygwin.dll? |
22 Jan 1997 08:03:17 -0800 : | |
Approved: | cygnus DOT gnu-win32 AT cygnus DOT com |
Distribution: | cygnus |
Message-ID: | <199701221228.EAA19670.cygnus.gnu-win32@rtl.cygnus.com> |
Original-To: | mjo AT mrao DOT cam DOT ac DOT uk (Martin Oldfield) |
Original-Cc: | loki AT maison-otaku DOT net, s2172184 AT cse DOT unsw DOT edu DOT au, M DOT Carter AT gcal DOT ac DOT uk, |
gnu-win32 AT cygnus DOT com | |
In-Reply-To: | <m0vkrv5-000AcLC@joanna.robinson.cam.ac.uk> from "Martin Oldfield" at Jan 16, 97 01:31:00 pm |
X-Mailer: | ELM [version 2.4 PL23] |
Original-Sender: | owner-gnu-win32 AT cygnus DOT com |
Martin Oldfield wrote: > > What happens if we change the name of cygwin.dll to include a (major) > version number ? Then people can keep cygwin1.dll, cygwin2.dll, &c on > their machine and run both old and new executables without any > problems. I have thought of this before and am still considering doing something like this. Of course, if we never make any future incompatible changes to the cygwin.dll that invalidate old executables, this won't be necessary but of course I would never promise that. :-) -- Geoffrey Noer noer AT cygnus DOT com - For help on using this list, send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |