From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] a question about syntax
Date: Wed, 14 Feb 2018 19:50:46 +0100 [thread overview]
Message-ID: <20180214195046.Horde.mSIwdxq5Yo9xUKgfzIss4Ey@webmail.in-berlin.de> (raw)
In-Reply-To: <21BC6EDE-DB27-460B-A4D5-BBD583C9E899@TimLeonard.us>
Zitat von Tim Leonard <Tim@timleonard.us> (Tue, 13 Feb 2018 22:31:14 -0500)
> A simple question of syntax: why does the first definition of
> function f cause a syntax error?
> Shouldn’t the semicolon syntactically terminate the match expression?
No.
You can use semicolon to put more then one expression together.
So the "field2 = 2" is seen as part of the match.
If you have a pattern matching, this way you can put multiple
commands/expressions in a row,
without the need to use begin/end or ( ) in any match-case.
It's the other way around: you need to put begin/end or ( ) around a
match-statement.
This way you have to add one such enclosing around a match-statement,
instead of one such enclosing in any match-case of such a statement.
>
> type my_record = { field1 : bool; field2 : int };;
>
> let f x = { field1 = match x with _ -> true ; field2 = 2 };; (*
> this fails *)
Here I get "Error: Unbound value field2",
which is, because the match-case reaches until the }.
>
> let f x = { field1 = ( match x with _ -> true ); field2 = 2 };; (*
> this is ok *)
Here it works, because the match-statement is sorrounded / enclosed by
( and ).
Ciao,
Oliver
next prev parent reply other threads:[~2018-02-14 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 3:31 Tim Leonard
2018-02-14 3:41 ` Kenneth Adam Miller
2018-02-14 4:12 ` Yawar Amin
2018-02-14 4:32 ` Tim Leonard
2018-02-14 18:50 ` Oliver Bandel [this message]
2018-02-14 23:02 ` Chet Murthy
2018-02-14 23:40 ` Ian Zimmerman
2018-02-15 0:17 ` Evgeny Roubinchtein
2018-02-15 1:17 ` Chet Murthy
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=20180214195046.Horde.mSIwdxq5Yo9xUKgfzIss4Ey@webmail.in-berlin.de \
--to=oliver@first.in-berlin.de \
--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