Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: thetza@sent.com
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] License clarification
Date: Fri, 21 Oct 2005 11:16:48 +0900 (JST)	[thread overview]
Message-ID: <20051021.111648.126757916.garrigue@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <1129859175.26911.245665540@webmail.messagingengine.com>

From: "Tato Thetza" <thetza@sent.com>

> I'm sorry to bother you all but I'd like some clarification on the Ocaml
> license. First, let me state that I do not plan to modify the Ocaml
> compilers, libraries, or any thing else which is included in the
> official Ocaml distribution. I wouldn't even know where to start :-D.
> 
> That said, few question:
> 1) If I write a program or library in the ocaml language, are there any
> restrictions on the licensing/distribution of source code or
> bytecode/binaries produced by the ocaml compilers?
> 
> 2) If I write a C extension to be linked with an ocaml program, are
> there any restrictions on its license/distribution?
> 
> 3) May I link a closed source (or other restrictively licensed) C
> library to ocaml code?

No restrictions.
No restrictions.
Yes. (except if the license of the C library itself forbids it)

To be more precise, restrictions only appear if you modify the ocaml
runtime itself, or distribute executables including other parts of the
system (the ocaml toplevel for instance). Then you must read the
license to see what you are allowed to do.

Jacques Garrigue


      reply	other threads:[~2005-10-21  2:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-21  1:46 Tato Thetza
2005-10-21  2:16 ` Jacques Garrigue [this message]

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=20051021.111648.126757916.garrigue@math.nagoya-u.ac.jp \
    --to=garrigue@math.nagoya-u.ac.jp \
    --cc=caml-list@yquem.inria.fr \
    --cc=thetza@sent.com \
    /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