Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Fri, 2 Jul 1999 11:51:15 -0400
To: DJ Delorie <dj AT delorie DOT com>
Cc: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: Experimental changes in the new snapshot
Message-ID: <19990702115114.A772@cygnus.com>
References: <19990701232752 DOT A3414 AT cygnus DOT com> <199907021355 DOT JAA08918 AT indy DOT delorie DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <199907021355.JAA08918@indy.delorie.com>; from DJ Delorie on Fri, Jul 02, 1999 at 09:55:29AM -0400

On Fri, Jul 02, 1999 at 09:55:29AM -0400, DJ Delorie wrote:
>> 3) Detects when the DLL is run from a non-compatible version of
>>    a previous DLL and aborts with an error message.
>
>Is there any way to treat it like a non-cygwin parent, so that the
>program runs with reduced functionality rather than aborting?

We could easily do this but I felt that that would lead to people
reporting additional problems where they forgot to mention that
they were getting a warning when they were attempting to run some
applications.

The bottom line is that if someone has two incompatible versions of
a DLL in their path then they are really asking for trouble.

cgf