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 sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <39104624.CF876E7E@earthlink.net> Date: Wed, 03 May 2000 08:30:44 -0700 From: Charles Hixson X-Mailer: Mozilla 4.72 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Things you can do with Cygwin References: <200005022020 DOT QAA22623 AT envy DOT delorie DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit DJ Delorie wrote: > ...(snip) > > The static linking case is clear. > > Agreed. > > > Dynamic linking is not so clear, it is likely covered by the GPL but > > who knows for sure. > > My claim is that the fact that it's dynamically linked is irrelevent; > all that is relevent is whether there are two independent works > involved, or only one. ... (snip) And this is the area of disagreement. I feel that since a dynamically linked chunk of code only specifies the interface, and not the internals, that the internals are not parts of the same work. In particular it is certainly possible to have multiple hunks of code with the same name and effectively the same interface (minor variations may exist) because that is the source of windows "dll hell". If there can be multiple versions that do very different things, after the manner of things returned by a factory pattern, then I don't see them as being the same work at all. And since the caller doesn't know which of the different versions it will get, it can't be a part of the same work either. IANAL. But this is my opinion. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com