IE> It's the definition of linking that is usually troublesome with Lisp IE> and licensing. If we look at it like Python as you intend below, then IE> only the Lisp image itself need be open source (i.e. SBCL). However IE> Lisp is also compiled and dynamically linked with the image, which IE> tends to make us look a little bit more like a dynamically linked IE> program that GNU, in general, considers part of the application (i.e. IE> contaminated)
heh, that's interesting.. it's legal to use BDB from CLISP (since technically CLISP doesn't differ from Perl or Python), but illegal from SBCL? _______________________________________________ elephant-devel site list elephant-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/elephant-devel
