Browse thread
Undefined evaluation order
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Stefan Monnier <monnier+lists/caml/news/@R...> |
| Subject: | Re: Undefined evaluation order |
>>>>> "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