From: "Jeff Meister" <nanaki@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Re: Order of evaluation when constructing record values
Date: Sat, 11 Aug 2007 14:15:21 -0400 [thread overview]
Message-ID: <6806cf750708111115w3c3170abj3a4096ed95376222@mail.gmail.com> (raw)
In-Reply-To: <6806cf750708111056v19107705p288e0b0bb152ef63@mail.gmail.com>
I seem to have answered my own question by playing around. It appears
that the order of evaluation is last-to-first and based on the order
of the fields in the type declaration, not in the value construction.
Oh well. I guess it's let-bindings for me.
On 8/11/07, Jeff Meister <nanaki@gmail.com> wrote:
> I ask for forgiveness in advance for this silly pedantic question.
>
> I think my question is best illustrated with an example. Say I have
> this simple record type for holding a date:
>
> type date = { year : int; month : int; day : int; }
>
> Now, I want to read the year/month/day values from stdin, and I know
> they will appear in that order. So I do the following:
>
> let today = {
> year = read_int ();
> month = read_int ();
> day = read_int ();
> }
>
> For this to work, I need the ints to be read in the order given, or I
> could end up with a day of 2007 and a year of 11. Is there any
> guarantee that OCaml will follow that order of evaluation when
> constructing the record? Or do I have to force it with let-bindings
> like this:
>
> let today =
> let y = read_int () in
> let m = read_int () in
> let d = read_int () in
> { year = y; month = m; day = d; }
>
> Of course, it's not that big a deal for me to just use the let-binding
> method, but I'm curious, and it might make my code look nicer if I can
> rely on order of evaluation.
>
next prev parent reply other threads:[~2007-08-11 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 17:56 Jeff Meister
2007-08-11 18:15 ` Jeff Meister [this message]
2007-08-11 22:13 ` [Caml-list] " Jon Harrop
2007-08-12 8:25 ` Till Varoquaux
2007-08-12 9:12 ` [Caml-list] " David Allsopp
2007-08-13 0:25 ` Jacques Garrigue
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=6806cf750708111115w3c3170abj3a4096ed95376222@mail.gmail.com \
--to=nanaki@gmail.com \
--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