caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: John Max Skaller <skaller@ozemail.com.au>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
Cc: Xavier.Leroy@inria.fr, caml-list@inria.fr
Subject: Re: [Caml-list] Caml toplevel and readline
Date: Tue, 19 Jun 2001 02:34:38 +1000	[thread overview]
Message-ID: <3B2E2D9E.A85C2201@ozemail.com.au> (raw)
In-Reply-To: <20010618184841N.garrigue@kurims.kyoto-u.ac.jp>

Jacques Garrigue wrote:

> As long as you distribute the special runtime containing readline
> separately from the toplevel, this reasoning is OK. 

	Hang on! I already have libreadline.
I don't want INRIA to distribute it, just detect if I already
have it. If I do, I would like to be able to link it in
to the top level.

	Alternatively, why not build the toplevel
with ledit?

> But the first man making a custom toplevel is dead: 
> having both in the same file won't do.

	I am the one linking it into the toplevel, not INRIA.
It will have no impact on me, since I do not use the top
level for producing code (only for testing the occasional
small fragments).

	It's doubtful if the FSF licences mean much
anyhow. Python uses readline by default in its top level,
if available. There are lots of Python programs out there,
being run with a binary with readline linked in, which
are not licenced GPL, Python itself being an example.

> Even distributing libreadline inside the ocaml distribution might
> be a problem: 

	Please don't. 

-- 
John (Max) Skaller, mailto:skaller@maxtal.com.au
10/1 Toxteth Rd Glebe NSW 2037 Australia voice: 61-2-9660-0850
checkout Vyper http://Vyper.sourceforge.net
download Interscript http://Interscript.sourceforge.net
-------------------
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


  reply	other threads:[~2001-06-19  7:28 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 [this message]
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=3B2E2D9E.A85C2201@ozemail.com.au \
    --to=skaller@ozemail.com.au \
    --cc=Xavier.Leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=garrigue@kurims.kyoto-u.ac.jp \
    /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).