From: ivan chollet <ivan.chollet@gmail.com>
To: "Richard W.M. Jones" <rich@annexia.org>
Cc: Lukasz Stafiniak <lukstafi@gmail.com>,
Diego Olivier Fernandez Pons <dofp.ocaml@gmail.com>,
caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Examples where let rec is undesirable
Date: Thu, 5 Jan 2012 20:27:25 +0000 [thread overview]
Message-ID: <CACm_MF8JrUsoGFG1Bq3CHEkHBFRPWg=NzrgrwBSkThpTO59LZA@mail.gmail.com> (raw)
In-Reply-To: <20120105200442.GA17669@annexia.org>
[-- Attachment #1: Type: text/plain, Size: 1860 bytes --]
Allowing variable shadowing is aesthetically more satisfying and more
expressive, but opens the door to bugs that can be harder to track by
static analysis.
I would be interested to hear the pro-arguments for variable shadowing,
besides the slight gain in expressiveness.
On Thu, Jan 5, 2012 at 8:04 PM, Richard W.M. Jones <rich@annexia.org> wrote:
> On Tue, Jan 03, 2012 at 01:05:39AM +0100, Lukasz Stafiniak wrote:
> > On Mon, Jan 2, 2012 at 11:37 PM, Diego Olivier Fernandez Pons
> > <dofp.ocaml@gmail.com> wrote:
> > > List,
> > >
> > > I was wondering if there was any reason not to make "let rec" the
> default /
> > > sole option, meaning cases where you clearly don't want a "let rec"
> instead
> > > of "let" (only in functions, not cyclic data).
> > >
> > > Diego Olivier
> >
> > The default "no-rec" allows for name recycling -- using the same name
> > for an incrementally transformed value, i.e. to bind the intermediate
> > results. Name recycling minimizes the cognitive burden: there are less
> > names to remember in a scope, and differences in names are justified
> > by differences in purpose of the values. Are there reasons to consider
> > name recycling a bad style?
>
> I had an argument about this with a noted open source developer
> recently. He was saying that C's approach -- not permitting variable
> names to be reused within a single function -- was somehow
> advantageous. From my point of view, having used both languages
> extensively, OCaml's way is *far* better.
>
> So yes, 'let' and 'let rec', long may they be different.
>
> Rich.
>
> --
> Richard Jones
> Red Hat
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
[-- Attachment #2: Type: text/html, Size: 2674 bytes --]
next prev parent reply other threads:[~2012-01-05 20:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 22:37 Diego Olivier Fernandez Pons
2012-01-02 22:49 ` Alexandre Pilkiewicz
2012-01-03 0:05 ` Lukasz Stafiniak
2012-01-03 5:47 ` Martin Jambon
2012-01-03 8:07 ` Gabriel Scherer
2012-01-05 20:04 ` Richard W.M. Jones
2012-01-05 20:27 ` ivan chollet [this message]
2012-01-05 20:46 ` Gabriel Scherer
2012-01-05 21:39 ` Richard W.M. Jones
2012-01-06 2:39 ` Cedric Cellier
2012-01-06 15:22 ` Damien Doligez
2012-01-05 21:36 ` Richard W.M. Jones
2012-01-05 23:16 ` ivan chollet
2012-01-06 8:34 ` David Allsopp
2012-01-06 10:34 ` Daniel Bünzli
2012-01-03 13:05 ` Yaron Minsky
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='CACm_MF8JrUsoGFG1Bq3CHEkHBFRPWg=NzrgrwBSkThpTO59LZA@mail.gmail.com' \
--to=ivan.chollet@gmail.com \
--cc=caml-list@inria.fr \
--cc=dofp.ocaml@gmail.com \
--cc=lukstafi@gmail.com \
--cc=rich@annexia.org \
/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