From: Neel Krishnaswami <neelk@alum.mit.edu>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] why the "rec" in "let rec"?
Date: Wed, 7 May 2003 10:50:11 -0400 [thread overview]
Message-ID: <16057.7459.42552.45637@h00045a4799d6.ne.client2.attbi.com> (raw)
In-Reply-To: <2003050710041052316284@kestrel.sage.att.com>
Garry Hodgson writes:
>
> something i was always curious about: why do you need to
> specify the "rec" in a "let rec" function definition? as opposed
> to, say, having the compiler figure out when a function is recursive?
It's the simplest way of dealing with the interaction of lexical scope
and recursion. Consider the following examples:
let f = fun x -> (Printf.printf "#"; x) in
let f x = f x
in
f 5
versus
let f = fun x -> (Printf.printf "#"; x) in
let rec f x = f x
in
f 5
The reference to 'f' in the second function body refers to the f
already in scope. The 'rec' keyword is how you tell the compiler to
ignore that and make it a recursive binding.
So the first example prints "#" and return 5. The second loops
indefinitely.
--
Neel Krishnaswami
neelk@alum.mit.edu
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-05-07 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 14:04 Garry Hodgson
2003-05-07 14:31 ` Chris Uzdavinis
2003-05-07 14:50 ` Neel Krishnaswami [this message]
2003-05-07 14:57 ` Hal Daume III
2003-05-07 15:11 ` Falk Hueffner
2003-05-07 15:16 ` David Brown
2003-05-07 15:53 ` Brian Hurt
2003-05-07 15:51 ` Garry Hodgson
2003-05-07 15:40 ` Neel Krishnaswami
2003-05-07 15:59 ` Gerd Stolpmann
2003-05-13 16:36 ` Pierre Weis
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=16057.7459.42552.45637@h00045a4799d6.ne.client2.attbi.com \
--to=neelk@alum.mit.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