From: Markus Mottl <markus@oefai.at>
To: caml-list@inria.fr
Subject: Re: [Caml-list] syntax foo
Date: Wed, 6 Feb 2002 21:41:42 +0100 [thread overview]
Message-ID: <20020206204142.GB32204@fichte.ai.univie.ac.at> (raw)
In-Reply-To: <20020206215807.A18430@kruuna.Helsinki.FI>
On Wed, 06 Feb 2002, Lauri Alanko wrote:
> Note that the layout rule in Haskell is _optional_. You can always use
> explicit braces and semicolons and forget about indentation. So at least
> your point on code generation doesn't hold.
Ok.
> Personally, I find Haskell's syntax (with or without the layout rule)
> infinitely more convenient than OCaml's. Anything that uses "end" to mark
> the end of a block is hopelessly clumsy and old-fashioned. :)
I agree that Haskell-code looks much nicer than OCaml-code. The question
is whether anybody would want to write an advanced parser for OCaml...
> The sorest lack in both the old and the revised syntax is the need for a
> let*-form, ie. a sequence of bindings, each of which is in the scope of the
> previous ones. I _so_ hate doing this:
>
> let foo = bar in
> let baz = quux in
> let fnord = fnarp in
> ...
Well, one doesn't have to indent each line, of course. It's still a bit
painful to have all those "let"s and "in"s.
Regards,
Markus Mottl
--
Markus Mottl markus@oefai.at
Austrian Research Institute
for Artificial Intelligence http://www.oefai.at/~markus
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2002-02-06 20:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 20:48 james woodyatt
2002-02-05 21:21 ` Jérôme Marant
2002-02-06 15:30 ` Brian Rogoff
2002-02-06 18:25 ` Markus Mottl
2002-02-06 19:58 ` Lauri Alanko
2002-02-06 20:41 ` Markus Mottl [this message]
2002-02-06 20:47 ` Alexander V. Voinov
2002-02-07 1:43 ` Brian Rogoff
2002-02-06 19:08 ` Alexander V. Voinov
2002-02-06 19:10 ` David Brown
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=20020206204142.GB32204@fichte.ai.univie.ac.at \
--to=markus@oefai.at \
--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