Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: David Teller <David.Teller@ens-lyon.org>
To: Caml list <caml-list@inria.fr>
Subject: Re: [Caml-list] Toplevel wishlist
Date: Thu, 19 Jan 2006 22:32:46 +0000	[thread overview]
Message-ID: <1137709966.5973.39.camel@titania> (raw)
In-Reply-To: <43CFF2D6.4080108@andrej.com>

Le jeudi 19 janvier 2006 à 21:13 +0100, Andrej Bauer a écrit :
> 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.

TeXmacs ? Talk about *extremely* pretty-printing :)

More seriously, do you have any application in mind ? I wonder what kind
of "abstract" information should be communicated. 

> 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.

Nice idea, too. It reminds me of a Microsoft video I saw some time ago
about how The Next Big Thing In Programming Languages (tm) would be
getting rid of syntax.


Cheers,
 David
-- 
Read, Write, and Publish Standard eBooks
  Free, Open Software, Open Standards and multi-platform
    The OpenBerg project http://www.openberg.org


  parent reply	other threads:[~2006-01-19 22:32 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 ` [Caml-list] " Jonathan Roewen
2006-01-19 22:32 ` David Teller [this message]
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=1137709966.5973.39.camel@titania \
    --to=david.teller@ens-lyon.org \
    --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