Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Andrej Bauer <Andrej.Bauer@andrej.com>
To: Caml list <caml-list@inria.fr>
Subject: Toplevel wishlist
Date: Thu, 19 Jan 2006 21:13:10 +0100	[thread overview]
Message-ID: <43CFF2D6.4080108@andrej.com> (raw)

Thank you for suggestions on how to tweak custom toplevels.

For a while now I have been thinking that there should be a fancy
alternative to the current toplevel. If I had the time, I would actually
go ahead and try to write one. But what would be a good feature list?

I can think of several improvements:

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

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.

3) Equip toplevel with pretty printers that can manage polymorphic
types, and essentially make it possible to pretty print _everything_. It
should be possible to create a toplevel linked to a graphical user
interface that shows pictures and typeset text as results.

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.

What else can we put on the wishlist?

If only someone else did it :-)

Andrej


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19 20:13 Andrej Bauer [this message]
2006-01-19 21:01 ` [Caml-list] " Jonathan Roewen
2006-01-19 22:32 ` 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=43CFF2D6.4080108@andrej.com \
    --to=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