caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Zheng Li <zheng_li@users.sourceforge.net>
To: OCaml Mailing List <caml-list@inria.fr>
Subject: QPL license issue on toplevel
Date: Mon, 24 Nov 2008 17:28:22 +0100	[thread overview]
Message-ID: <492AD626.10703@users.sourceforge.net> (raw)

Dear list,

I'm working towards a pure library version of the enhtop (an enhanced 
toplevel). I have some question about the toplevel's license of OCaml (QPL).

IMHO, OCaml toplevel allows to dynamic load libraries that are 
distributed *independently* under other licenses (even GPL or 
proprietary ones). I'm not sure about the _official_ understanding to 
this, but I guess that loading in toplevel is considered as

  - end-user dynamic linking
  - or execution

If we neither build the libraries and toplevel into one binary (via 
ocamlmktop) to distribute, nor do we wrap their source code as a bundle 
for delivery, we don't have to face any license issue. Is that correct?

Then how about a library that explicitly calls some toplevel functions 
(e.g. Topmain.xxx). This might be considered as "intend to link with 
XXX", so must such a library be always released under QPL?  (One 
counterexample might be camlp4, part of which calls toplevel functions 
and is released under LGPL, but it comes from the same team anyway ...)

Another option (if I want to avoid QPL) is to use reflection, so that 
the library don't have to call toplevel functions explicitly, but it 
still requires to work inside a toplevel (or together with a toplevel 
library). However I doubt whether this trick (or say cheating) is 
considered valid. Any precedents?

Thanks.

--
Zheng














                 reply	other threads:[~2008-11-24 16:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=492AD626.10703@users.sourceforge.net \
    --to=zheng_li@users.sourceforge.net \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).