From: Chris Uzdavinis <chris@atdesk.com>
To: Garry Hodgson <garry@sage.att.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] why the "rec" in "let rec"?
Date: Wed, 7 May 2003 10:31:25 -0400 [thread overview]
Message-ID: <200305071431.h47EVPG09424@plover.atdesk.com> (raw)
In-Reply-To: <2003050710041052316284@kestrel.sage.att.com>
Garry Hodgson <garry@sage.att.com> 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?
>
> is it a compiler/grammar optimization? or to help the user, forcing
> them to be precise with recursion? or required by the type system?
It affects the name lookup rules. For example:
let f x = x
let f x = f x
The 2nd definition for function f is not an infinite loop. It calls
the previously defined version of f, and is thus a more expensive
identity function. However:
let f x = x
let rec f x = f x
Now the first function is not used by the second (which, due to the
"rec" having been added, is now an infinite loop calling itself.)
> do other ML's do it this way?
Yes.
--
Chris
-------------------
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:31 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 [this message]
2003-05-07 14:50 ` Neel Krishnaswami
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=200305071431.h47EVPG09424@plover.atdesk.com \
--to=chris@atdesk.com \
--cc=caml-list@inria.fr \
--cc=garry@sage.att.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