From: Jon Harrop <jon@jdh30.plus.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Ocaml license - why not GPL?
Date: Fri, 28 Jan 2005 19:09:10 +0000 [thread overview]
Message-ID: <200501281909.11006.jon@jdh30.plus.com> (raw)
In-Reply-To: <20050128170854.GA18431@old.davidb.org>
On Friday 28 January 2005 17:08, David Brown wrote:
> The only
> thing that would be restricted would be if your program links with or uses
> parts of the compiler itself.
A commercial product may bundle and use the ocaml compilers and run-time in
their entirety (e.g. by executing ocamlopt) without infringing the license.
Commercial products may not link to or lift code from the compilers though,
of course, as this counts as redistribution of a modification to the
compiler.
I can see this descending into a discussion about the definition of linking in
the presence of HOFs... :-)
IMHO, academics be encouraged by their funding bodies to release their code
under an artistic/BSD license because they are funded by the tax payer.
Naturally, this shouldn't apply to me.
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
next prev parent reply other threads:[~2005-01-28 19:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 16:47 Jozef Kosoru
2005-01-28 17:08 ` [Caml-list] " David Brown
2005-01-28 19:09 ` Jon Harrop [this message]
2005-01-29 23:46 ` Stefan Monnier
2005-01-28 17:14 ` [Caml-list] " Luc Maranget
2005-01-29 6:05 ` Jacques Garrigue
2005-01-30 6:22 ` Sven Luther
2005-01-31 0:57 ` Jacques Garrigue
2005-01-31 7:03 ` Alex Baretta
2005-01-31 7:38 ` Sven Luther
2005-01-31 7:47 ` Alex Baretta
2005-01-31 7:59 ` Sven Luther
2005-01-31 9:09 ` skaller
2005-01-31 9:23 ` Sven Luther
2005-01-31 9:00 ` Xavier Leroy
2005-01-31 9:15 ` Sven Luther
2005-01-31 9:47 ` Nicolas Cannasse
2005-01-31 10:29 ` Xavier Leroy
2005-01-31 10:41 ` Nicolas Cannasse
2005-01-31 11:08 ` Alex Baretta
2005-01-31 11:49 ` Alex Baretta
2005-01-31 7:35 ` Sven Luther
2005-01-30 6:18 ` Sven Luther
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=200501281909.11006.jon@jdh30.plus.com \
--to=jon@jdh30.plus.com \
--cc=caml-list@yquem.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).