[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [DotGNU]Licence question about GNU and GCC

From: James Michael DuPont
Subject: Re: [DotGNU]Licence question about GNU and GCC
Date: Mon, 11 Mar 2002 11:51:47 -0800 (PST)

> > inherent danger that the SOAP and DOTGNU
> > will open up all of the gpl'd code to. 
> Ok.  But how is this danger greater than what was
> always
> possible with GPL programs, to create input files
> for the GPL
> program with a proprietary program and feed the data
> to
> the GPL program with a pipe or a temporary file?

The issue with soap is that you can link from any non
gpled to gpled. 

If you had a way of creating a soap linker, and all
the functions of a archive file would be wrapped, the
parameters typed-mapped and soap proxys generated. 
You could then take any of the gpled code and use it
via soap.
The issue gets foggier with the P/Invoke.

This issue occurs also with perl and script languages
according to the GPL faq, if you link a GPLed lib to a
app via perl the app will have to be GPL. But that is
hardly enforced.

Of course you can always create a single exe that is
gpled that holds only on function that is called via
parameters from the stdin and writes to the stdout.

But soap/.net make it easier to do this, with standard
serialization and binding to programming languages.

Soap seems to be the easiest platform to link to...


James Michael DuPont

Do You Yahoo!?
Try FREE Yahoo! Mail - the world's greatest free email!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]