caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Julian Assange <proff@iq.org>
To: caml-list@inria.fr
Cc: proff@iq.org
Subject: let ... in layout
Date: 15 Mar 2000 12:33:58 +1100	[thread overview]
Message-ID: <wx8zzlm2yh.fsf@suburbia.net> (raw)


let .. in
let .. in ...

seems such a common construct in caml that it could do with some
syntatic sugar. I often see let..in run to 5-20 clauses. This appears
incredibly ugly compared to the equivalent haskell code, is harder to
read and takes longer to write due to the clutter of the surrounding
token magic. Has anyone thought about applying layout in general to
ocaml, or otherwise sugaring let...in? Is there any reason why the BNF

        let {name = expr}+ in

would be ambiguous?

The only other haskell features I frequently miss, are list
comprehensions and multiple argument pattern matching.

Cheers,
Julian.



             reply	other threads:[~2000-03-15  7:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-15  1:33 Julian Assange [this message]
2000-03-15  8:22 ` Jean-Yves Moyen
2000-03-15 22:18   ` Julian Assange
2000-03-17  9:42     ` Pierre Weis
2000-03-15  8:56 ` Benoit Deboursetty
2000-03-17 13:16 ` Dmitri Lomov

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=wx8zzlm2yh.fsf@suburbia.net \
    --to=proff@iq.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;
as well as URLs for NNTP newsgroup(s).