caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Teller <David.Teller@univ-orleans.fr>
To: Caml <caml-list@yquem.inria.fr>
Subject: [OSR] Standard syntax extensions ?
Date: Thu, 24 Apr 2008 17:49:42 +0200	[thread overview]
Message-ID: <1209052182.6180.35.camel@Blefuscu> (raw)

    Dear list,

 Now that the forge is up, it's time to (re)start thinking about the OSR
and what we want the future of the OCaml standard distribution to look
like. Other threads will be (re)spawned regarding various aspects of
that distribution, but for now, I'd like to discuss which syntax
extensions. Oh, and before this thread diverges again, let me underline
that we're *not* discussing delivery mechanisms or ocamlfind or
ocamlbuild or repositories or GODI or IDisposable or camlp4 vs.
camlp5... We're also not discussing original vs. revised syntax vs. twt
[yet], although if you consider that some extension would be much more
useful if rendered compatible with one of these syntaxes, please mention
it.

Now, a few subjects I'd like to see covered:
* which syntax extensions do you use so often that you consider they
should be part of the language ?
* which syntax extensions are very important to you but should not be
included in the core language [yet] ?
* which syntax extensions are good ideas and should go into one of the
previous categories but miss the mark because of dependencies / cosmetic
issues and/or incompatibilities with other extensions or with the latest
camlp4 ?
* what kind of syntactic sugar is absolutely missing from the language ?

As this may come into play later, whenever you suggest an extension,
don't hesitate to comment whether you believe whom this extension would
serve: beginners ? power-users ? some more specific category ?

Cheers,
 David
-- 
David Teller
 Security of Distributed Systems
  http://www.univ-orleans.fr/lifo/Members/David.Teller
 Angry researcher: French Universities need reforms, but the LRU act brings liquidations. 


             reply	other threads:[~2008-04-24 15:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24 15:49 David Teller [this message]
2008-04-24 15:52 ` [Caml-list] " John Whitington
2008-04-25  8:22   ` Richard Jones
2008-05-01  7:45     ` Richard Jones
2008-04-24 16:16 ` [Caml-list] [OSR] Standard syntax extensions ? - voting Stefano Zacchiroli
2008-04-25 15:15   ` David Teller
2008-04-26  0:16     ` Stefano Zacchiroli
2008-04-24 16:41 ` [Caml-list] [OSR] Standard syntax extensions ? Martin Jambon
2008-04-24 17:02   ` Jon Harrop
2008-04-24 20:53     ` Berke Durak
2008-04-25  8:24       ` Richard Jones
2008-04-25 16:59         ` Berke Durak
2008-04-25 17:31           ` Gerd Stolpmann
2008-04-25 17:38           ` Richard Jones
2008-04-25 10:33       ` Andrej Bauer
2008-04-25 15:32     ` David Teller
2008-04-24 17:05 ` Dario Teixeira
2008-04-25 13:57   ` Peng Zang
2008-04-25 15:04     ` David Teller
2008-04-25 16:11       ` Peng Zang
2008-04-25 20:37 ` Arthur Chan
2008-04-26  7:41   ` Richard Jones
2008-04-26  7:53     ` Till Crueger
2008-04-26 21:32       ` Arthur Chan
2008-04-27  6:58         ` Andrej Bauer
2008-04-27 14:14           ` Christopher L Conway
2008-04-27 17:41         ` [Caml-list] " David Teller
2008-04-27 17:44       ` David Teller
2008-04-25 22:25 ` Mike Lin

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=1209052182.6180.35.camel@Blefuscu \
    --to=david.teller@univ-orleans.fr \
    --cc=caml-list@yquem.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).