Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: Chris Faylor Date: Thu, 31 Aug 2000 11:55:56 -0400 To: cygwin AT sources DOT redhat DOT com Subject: Re: DLL naming conventions Message-ID: <20000831115556.F5412@cygnus.com> Reply-To: cygwin AT sources DOT redhat DOT com Mail-Followup-To: cygwin AT sources DOT redhat DOT com References: <20000831133952 DOT 21477 DOT qmail AT web123 DOT yahoomail DOT com> <39AE7E06 DOT CEFB0BC8 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <39AE7E06.CEFB0BC8@ece.gatech.edu>; from cwilson@ece.gatech.edu on Thu, Aug 31, 2000 at 11:47:18AM -0400 On Thu, Aug 31, 2000 at 11:47:18AM -0400, Charles S. Wilson wrote: >(This argument is based on the supposition that dll's with the same name >will always conflict. If I'm wrong about that supposition, please >correct me...as I stated above, I'm a bit confused as to when dll's will >conflict and when they will not) Can someone write a simple test to verify Windows behavior? It's pointless to argue about what Windows does with DLLs if we don't know for sure. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com