caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: John Max Skaller <skaller@ozemail.com.au>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Caml toplevel and readline
Date: Fri, 22 Jun 2001 16:56:48 +0200	[thread overview]
Message-ID: <20010622165648.B24296@lambda.u-strasbg.fr> (raw)
In-Reply-To: <3B2796C1.9144F7AE@ozemail.com.au>

On Thu, Jun 14, 2001 at 02:37:21AM +1000, John Max Skaller wrote:
> 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?

Note :

There is also libeditline as an option. It comes under an BSD without ad
clause, and as thus is prefectly compatible with the current ocaml code and is
source-cod compatible with the basic features of readline.

If you want to use libreadline, well, the toplevel parts must be released
under a GPL compatible licence, which i suppose will not happen. It could be
possible to do some tricks to offer at configuration time the ability to link
with libreadline, so that people can built it for themselves, but not
distribute it. I don't know how much work this is and if the caml team may be
willing to apply a patch providing such.

One could imagine a default build using libeditline and a switch for linking
against libreadline, but disabled by default, and with a warning about the non
distribuability of it.

In the end the ledit option seems the more attractive, being written in ocaml
and all. I would love to have it included in the base ocaml tarball.

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-22 14:53 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
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 [this message]
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=20010622165648.B24296@lambda.u-strasbg.fr \
    --to=luther@dpt-info.u-strasbg.fr \
    --cc=caml-list@inria.fr \
    --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).