From: Saptarshi Guha <saptarshi.guha@gmail.com>
To: guillaume.yziquel@citycable.ch
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] The need to specify 'rec' in a recursive function defintion
Date: Tue, 9 Feb 2010 17:14:12 -0500 [thread overview]
Message-ID: <1e7471d51002091414k35830faapb321b8ab7f1546e1@mail.gmail.com> (raw)
In-Reply-To: <4B71D9BB.3090605@citycable.ch>
Thanks, very helpful.
>> let f = fun x -> x + 1 (1)
>>
>> let f x = f (f x) (2)
This works in ocaml because, it replaces f (in (2) ) from that of (1).
Which is why i need f previously defined.
Correct me if i'm wrong.
>
>> Wouldn't one of way of detecting a recursive function would be to see
>> if the indeed the function calls itself?
>
> No. Because you never know if you intended to call the function recursively,
> or if you intended to call an homonymous function you defined before.
>
Very true, hadn't considered this.
> All the best,
>
> --
> Guillaume Yziquel
> http://yziquel.homelinux.org/
>
next prev parent reply other threads:[~2010-02-09 22:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 20:50 Saptarshi Guha
2010-02-09 21:55 ` [Caml-list] " Guillaume Yziquel
2010-02-09 22:14 ` Saptarshi Guha [this message]
2010-02-09 22:01 ` Gerd Stolpmann
2010-02-09 21:58 ` Guillaume Yziquel
2010-02-09 22:34 ` Gerd Stolpmann
2010-02-10 0:07 ` Guillaume Yziquel
2010-02-10 3:10 ` Alain Frisch
2010-02-09 22:16 ` Saptarshi Guha
2010-02-09 23:29 ` Jon Harrop
2010-02-10 10:15 ` rossberg
2010-02-10 7:19 ` Andrej Bauer
2010-02-10 9:36 ` Francois Maurel
2010-02-10 10:12 ` rossberg
2010-02-09 23:33 ` Jon Harrop
2010-02-09 22:31 ` Saptarshi Guha
2010-02-10 0:12 ` Jon Harrop
2010-02-10 22:01 ` Stefan Monnier
2010-02-10 22:25 ` [Caml-list] " Till Varoquaux
2010-02-11 1:48 ` Jon Harrop
2010-02-15 15:46 ` Stefan Monnier
2010-02-15 17:33 ` [Caml-list] " Jon Harrop
2010-02-15 20:36 ` Stefan Monnier
2010-02-16 14:42 ` Stefan Monnier
2010-02-16 16:21 ` [Caml-list] " Ashish Agarwal
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=1e7471d51002091414k35830faapb321b8ab7f1546e1@mail.gmail.com \
--to=saptarshi.guha@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=guillaume.yziquel@citycable.ch \
/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).