From: skaller <skaller@ozemail.com.au>
To: brogoff@speakeasy.net
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Ocaml syntax.
Date: 24 Dec 2003 21:27:52 +1100 [thread overview]
Message-ID: <1072261671.2702.67.camel@pelican> (raw)
In-Reply-To: <Pine.LNX.4.44.0312231016080.2042-100000@grace.speakeasy.net>
On Wed, 2003-12-24 at 08:52, brogoff@speakeasy.net wrote:
> > The native ocaml syntax has a bunch of strange inconsistencies.
> If I believed that, I'd be using Perl and C++ more than I do. Nope, I think
> "hysterical raisins" and human laziness/inertia/risk-avoidance explains a lot.
Some of the 'inconsistencies' aren't: an 'arbitrary' decision
was made, and the result seems 'inconsistent' only when
you're not the beneficiary of the choice made :-)
As a comparison, Felix mimics many Ocaml constructions
but uses slightly different syntax in some cases.
In particular:
<statement> ;
match .. with .. endmatch
if .. then .. else .. endif
but I still use
let .. in ..
unterminated. My opinion is that the endmatch
is ugly, longwinded, but otherwise desirable.
However, the if/then/else/endif leads to a
lot of extra ugly 'endif' keywords for chains,
which also force incorrect nesting.
The fix of course is to include
elif
as a suboption. I'm seriously thinking
of the equivalent for matches:
match .. with
...
elmatch .. with
..
else
..
endmatch
and now, the original Ocaml syntax looks simpler ..
especially when you consider that 'elif' makes
sense in a match, and 'elmatch' makes sense in
a conditional ...
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-12-24 10:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 4:03 [Caml-list] Frustrated Beginner Tyler Eaves
2003-12-23 4:19 ` jayanta nath
2003-12-23 5:34 ` Matt Gushee
2003-12-23 6:11 ` Tyler Eaves
2003-12-23 6:21 ` Michael Vanier
2003-12-23 6:31 ` Michael Jeffrey Tucker
2003-12-23 12:16 ` Richard Jones
2003-12-23 20:23 ` Dustin Sallings
2003-12-23 6:32 ` Shawn Wagner
2003-12-23 6:43 ` Matt Gushee
2003-12-23 5:58 ` Dustin Sallings
[not found] ` <EAEE2FF2-3510-11D8-B3A1-000A9584A16E@ml1.net>
2003-12-23 6:53 ` Dustin Sallings
2003-12-23 7:23 ` Tyler Eaves
2003-12-23 8:26 ` Dustin Sallings
2003-12-23 6:20 ` Tom Murray
2003-12-23 8:52 ` Stefano Zacchiroli
2003-12-23 16:47 ` [Caml-list] Ocaml syntax David Brown
2003-12-23 20:19 ` Dustin Sallings
2003-12-23 21:03 ` Eric Merritt
2003-12-23 21:52 ` brogoff
2003-12-24 10:27 ` skaller [this message]
2003-12-24 11:42 ` Peter Jolly
2003-12-24 12:19 ` skaller
2003-12-30 8:14 ` dmitry grebeniuk
2003-12-30 17:48 ` David Brown
2003-12-23 10:26 ` [Caml-list] Frustrated Beginner Samuel Lacas
2003-12-23 11:01 ` Dustin Sallings
2003-12-23 14:34 ` Oleg Trott
2003-12-23 20:25 ` Dustin Sallings
2003-12-23 16:11 ` Brian Hurt
2003-12-23 16:20 ` Sven Luther
2003-12-23 16:52 ` David Brown
2003-12-23 20:32 ` Dustin Sallings
2003-12-24 10:41 ` Issac Trotts
2003-12-23 17:39 ` Brian Hurt
2003-12-24 9:35 ` Jacques Garrigue
2003-12-24 9:49 ` skaller
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=1072261671.2702.67.camel@pelican \
--to=skaller@ozemail.com.au \
--cc=brogoff@speakeasy.net \
--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