From: "Till Varoquaux" <till.varoquaux@gmail.com>
To: "Jeff Meister" <nanaki@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: Order of evaluation when constructing record values
Date: Sun, 12 Aug 2007 10:25:17 +0200 [thread overview]
Message-ID: <9d3ec8300708120125t1af4df64ga60e2ef09d6a35d4@mail.gmail.com> (raw)
In-Reply-To: <6806cf750708111115w3c3170abj3a4096ed95376222@mail.gmail.com>
Even though you found the order record were assigned, I would advice
to explicitly force this order (i.e. let bindings). AFAIK the order of
evaluation for records is not specified by the specification, therefor
it could change between revisions of the compiler.
Till
--
http://till-varoquaux.blogspot.com/
next prev parent reply other threads:[~2007-08-12 8:31 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
2007-08-11 22:13 ` [Caml-list] " Jon Harrop
2007-08-12 8:25 ` Till Varoquaux [this message]
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=9d3ec8300708120125t1af4df64ga60e2ef09d6a35d4@mail.gmail.com \
--to=till.varoquaux@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=nanaki@gmail.com \
/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).