caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
Cc: skaller@ozemail.com.au, caml-list@inria.fr
Subject: Re: [Caml-list] Caml toplevel and readline
Date: Fri, 15 Jun 2001 11:34:24 +0200	[thread overview]
Message-ID: <20010615113424.A8338@lambda.u-strasbg.fr> (raw)
In-Reply-To: <20010614154525K.garrigue@kurims.kyoto-u.ac.jp>

On Thu, Jun 14, 2001 at 03:45:25PM +0900, Jacques Garrigue wrote:
> From: John Max Skaller <skaller@ozemail.com.au>
> 
> > I find the ocaml top level 'ocaml' very clumbsy to use,
> > compared with, say, Python's top level, because it
> > doesn't understand line editing. Any chance of optionally
> > building it with gnu_readline?
> 
> No. Gnu-readline is a well-known example of library released under the
> GPL, which makes it incompatible with the caml toplevel, which is
> covered by the QPL :-)

mmm,

did not the kde guys take the version of libreadline that was distributed with
libc6 (which is under lgpl i think) and work from that ? But then it was
during the horrible kde/qt vs FSF war, so ...

Also notice, i think to remember, would need checking though, that if you
allow a program to link to a GPLed library as an alternative, then there is no
problem, so some people may be able to build ocaml with libreadline, and other
without, without further complication on the ocaml lincencing status. Not sure
though. 

If the ocaml team want to have more information on this issue, i can ask
advice on debina-legal, if you want ?

Friendly,

Sven Luther
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  parent reply	other threads:[~2001-06-15  9:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13 16:37 John Max Skaller
2001-06-14  6:40 ` Mark Wotton
2001-06-14  6:45 ` Jacques Garrigue
2001-06-14 10:32   ` leary
2001-06-14 15:47   ` Brian Rogoff
2001-06-14 19:43   ` John Max Skaller
2001-06-14 21:03     ` Pierre Weis
2001-06-15  5:05       ` leary
2001-06-15 10:21         ` Daniel de Rauglaudre
2001-06-15 20:59       ` John Max Skaller
2001-06-15 21:10       ` [Caml-list] Big_num not documented in manual John Max Skaller
2001-06-15  9:13     ` [Caml-list] Caml toplevel and readline Alan Schmitt
2001-06-15 14:12       ` Brian Rogoff
2001-06-15  9:34   ` Sven LUTHER [this message]
2001-06-16 17:46     ` leary
2001-06-18  7:32   ` Xavier Leroy
2001-06-18  9:48     ` Jacques Garrigue
2001-06-18 16:34       ` John Max Skaller
2001-06-19  1:39         ` Jacques Garrigue
2001-06-19 10:10           ` Sven LUTHER
2001-06-19 10:06         ` Sven LUTHER
     [not found]         ` <9gnrcd$4bv$1@qrnik.zagroda>
2001-06-21  6:05           ` Marcin 'Qrczak' Kowalczyk
2001-06-21  6:40             ` leary
2001-06-21  7:01               ` Jacques Garrigue
2001-06-22 14:56 ` Sven LUTHER
2001-06-22 15:36   ` Brian Rogoff
2001-06-24 20:59     ` Sven LUTHER
2001-06-22 17:52   ` Daniel de Rauglaudre
2001-06-13 20:37 [Caml-list] Repeat: is there a Qt binding for OCaml? Adriaan de Groot
2001-06-14  6:57 ` Jacques Garrigue
2001-06-14  7:51   ` leary
2001-06-14  8:36     ` [Caml-list] Caml toplevel and readline Jacques Garrigue

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=20010615113424.A8338@lambda.u-strasbg.fr \
    --to=luther@dpt-info.u-strasbg.fr \
    --cc=caml-list@inria.fr \
    --cc=garrigue@kurims.kyoto-u.ac.jp \
    --cc=skaller@ozemail.com.au \
    /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).