caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jonathan Roewen <jonathan.roewen@gmail.com>
To: Andrej.Bauer@andrej.com
Cc: Caml list <caml-list@inria.fr>
Subject: Re: [Caml-list] Toplevel wishlist
Date: Fri, 20 Jan 2006 10:01:12 +1300	[thread overview]
Message-ID: <ad8cfe7e0601191301o7741d2a7u10ad45e9f79b98a0@mail.gmail.com> (raw)
In-Reply-To: <43CFF2D6.4080108@andrej.com>

> 1) First, provide not only a toplevel but also a library that others
> could use to make toplevel-like interfaces to ocaml bytecode engine.

You mean toplevellib.cma for bytecode? ;-)

> 2) Do not hardcode stdin/stdout communication into toplevel. Instead,
> have a toplevel that communicates with the outside in a more abstract
> way. Thus it should be relatively easy to create toplevels that are
> equipped with line editing, that communicate through a graphical user
> interface (in a natural way), that talk via Texmacs, etc.

Using toplevellib.cma, you can create your own loop that reads/writes
from anything (though, for some reason, it appears the error printing
interface is not in the library dirs--why is that?).

> 4) Provide reasonable configuration options that allow one to customize
> the toplevel in a sensible way (such as pre-installed pretty printers
> and pre-open modules). Reading stuff _only_ from .ocamlinit is not fancy
> enough.

I made my own change to compiler/toplevel to specify modules to open
automatically. Look in mantis for it (it's not a proper patch, but
should be easy enough to apply yourself).

Jonathan


  reply	other threads:[~2006-01-19 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19 20:13 Andrej Bauer
2006-01-19 21:01 ` Jonathan Roewen [this message]
2006-01-19 22:32 ` [Caml-list] " David Teller
2006-01-20  8:09 ` Daniel Bünzli

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=ad8cfe7e0601191301o7741d2a7u10ad45e9f79b98a0@mail.gmail.com \
    --to=jonathan.roewen@gmail.com \
    --cc=Andrej.Bauer@andrej.com \
    --cc=caml-list@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).