>>>>> "tl" == Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
tl> 1) it looks lisp-y, but I didn't look very closely; how much tl> does this code resemble that for other lisp
packagessuch as tl> Allegro?
I assume you mean other "lisp implementations such as Allegro Common
Lisp"? The answer is that I have also written a Common Lisp version
(actually I wrote the CL version first), and a Scheme version
(Scheme is another language in the Lisp family), but given that there
is no standard interface to sockets in either Common Lisp or Scheme,
the code is implementation-specific. tl> 2) you are distributing it under GPL. No problem with that, but tl> if you
wereamenable to distributing under a BSD-style license tl> we could include it in the main Postgres distribution. Is
thata tl> possibility? It would be nice to have the foundation for another tl> language interface for folks to work
with.
this may be a little tricky. pg.el will probably be distributed with
Emacs in the future, and thus I will have to assign copyright to the
FSF. I will talk with rms about that. Does that mean that even for
client code which is intended to run completely independently from the
backend, it is not possible to mix BSD and GNU GPL code? The Common
Lisp and Scheme implementations, however, are under GNU LGPL, and I
have no problem releasing them under another licence. tl> Thanks again for the code. If the url you published is a
goodtl> long-term reference, then I'll add your introductory mail tl> message to the docs.
give me a few days and I'll write a special page for it. Thanks.
--
Eric Marsden
It's elephants all the way down
