clisp-list

from COPYRIGHT file:
This copyright does *not* cover user programs that run in CLISP, if
they don't reference symbols in CLISP's built-in packages (except
the packages LISP, USER, COMMON-LISP, COMMON-LISP-USER, KEYWORD),
So programs that use the FFI must be released under the GPL? Thus it
follows that its illegal to produce a propritary program with a GUI using
CLISP?

> * In message <15226.57031.400882.150661@...>
> * On the subject of "[clisp-list] gpl + foreign functions"
> * Sent on Wed, 15 Aug 2001 13:42:47 -0700
> * Honorable Dave Morse <svref@...> writes:
>
> from COPYRIGHT file:
> This copyright does *not* cover user programs that run in CLISP, if
> they don't reference symbols in CLISP's built-in packages (except
> the packages LISP, USER, COMMON-LISP, COMMON-LISP-USER, KEYWORD),
>
> So programs that use the FFI must be released under the GPL?
I think so.
[you appear to be using a pre-2.26 release. 2.27 is current.]
> Thus it follows that its illegal to produce a propritary program with
> a GUI using CLISP?
you can use sockets to communicate to a web browser
(like the portable CLOCC/CLLIB/inspect.lisp does).
--
Sam Steingold (http://www.podval.org/~sds)
Support Israel's right to defend herself! <http://www.i-charity.com/go/israel&gt;
Read what the Arab leaders say to their people on <http://www.memri.org/&gt;
Why use Windows, when there are Doors?

> * In message <20010815144121.A11669@...>
> * On the subject of "Re: [clisp-list] gpl + foreign functions"
> * Sent on Wed, 15 Aug 2001 14:41:21 -0700
> * Honorable David Morse <svref@...> writes:
>
> Sam Steingold <sds@...> wrote:
> > > from COPYRIGHT file:
> > > This copyright does *not* cover user programs that run in CLISP, if
> > > they don't reference symbols in CLISP's built-in packages (except
> > > the packages LISP, USER, COMMON-LISP, COMMON-LISP-USER, KEYWORD),
> > >
> > > So programs that use the FFI must be released under the GPL?
> >
> > I think so.
>
> Lets face it, FFIs are a standard non-standard feature.
but they are incompatible between the implementations, so the code
written for CLISP will not run under CMUCL and ACL and vice versa.
> In that sense, clisp's FFI package belongs to the list of packages above.
I will let Bruno make a decision on that.
--
Sam Steingold (http://www.podval.org/~sds)
Support Israel's right to defend herself! <http://www.i-charity.com/go/israel&gt;
Read what the Arab leaders say to their people on <http://www.memri.org/&gt;
Lisp: Serious empowerment.

David Morse writes:
> So programs that use the FFI must be released under the GPL?
Yes, definitely. By using the FFI you are linking together GPLed C
code with your additions. So you must put your additions under the GPL
if you want to distribute them.
> In that sense, clisp's FFI package belongs to the list of packages above.
There is no need to change the copyright wording. If you link some
pieces of C code with clisp, and use some Lisp code that accesses it
through the FFI, and want to distribute that, then you have to put
both under GPL because
- The GPL exception does not apply to your C code because it is not
code that "runs in CLISP". It is rather code that is linked with
CLISP.
- The GPL exception does not apply to your Lisp code because it
makes use of the non-standard FFI package.
Bruno