From: "Stefan Monnier" <monnier+lists/caml/news/@RUM.cs.yale.edu>
To: caml-list@inria.fr
Subject: Re: Undefined evaluation order
Date: 10 Oct 2000 15:26:22 -0400 [thread overview]
Message-ID: <39e36d5e$1@tequila.cs.yale.edu> (raw)
In-Reply-To: <Pine.BSF.4.21.0010081528360.11237-100000@shell5.ba.best.com>
>>>>> "Brian" == Brian Rogoff <bpr@best.com> writes:
> optimizations, but it is mentioned that this usually leads to clearer
> programs. I'm sure the bytecode compiler argument is valid, but not the code
> clarity one, since it sounds similar to an argument that having uninitialized
> variables is clearer since it forces you to make values explicit, and I don't
> believe that.
I don't think it can be compared that way. Using let does not introduce
grey-areas like uninitialized variables. All it does is give a name to
an intermediate value. This will usually improve the readability of the
code, unless the name is poorly chosen.
Stefan
next prev parent reply other threads:[~2000-10-11 19:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-05 18:14 Brian Rogoff
2000-10-06 2:02 ` Ken Wakita
2000-10-06 11:18 ` Pierpaolo BERNARDI
2000-10-07 6:46 ` Ken Wakita
2000-10-08 15:43 ` David Mentré
2000-10-08 22:47 ` Brian Rogoff
2000-10-10 12:47 ` Thorsten Ohl
2000-10-10 20:52 ` Brian Rogoff
2000-10-10 19:26 ` Stefan Monnier [this message]
2000-10-09 12:45 ` Xavier Leroy
2000-10-10 12:46 Greg Morrisett
2000-10-10 18:55 John R Harrison
2000-10-10 19:23 David McClain
2000-10-11 12:22 Greg Morrisett
2000-10-11 20:35 ` Pierre Weis
2000-10-13 7:05 ` Judicael Courant
2000-10-13 14:21 ` Markus Mottl
2000-10-16 8:38 ` Christophe Raffalli
2000-10-16 15:48 ` Brian Rogoff
2000-10-16 16:29 ` Christophe Raffalli
2000-10-17 9:19 ` Ralf Treinen
2000-10-12 9:53 Dave Berry
2000-10-12 11:32 Greg Morrisett
2000-10-12 17:06 David McClain
2000-10-13 13:56 Dave Berry
2000-10-14 1:42 David McClain
2000-10-20 14:59 Gerard Huet
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='39e36d5e$1@tequila.cs.yale.edu' \
--to=monnier+lists/caml/news/@rum.cs.yale.edu \
--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;
as well as URLs for NNTP newsgroup(s).