From: William Lovas <wlovas@stwing.upenn.edu>
To: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] List.rev
Date: Sat, 1 May 2004 03:08:45 -0400 [thread overview]
Message-ID: <20040501070844.GB19707@force.stwing.upenn.edu> (raw)
In-Reply-To: <1083388377.2581.383.camel@pelican.wigram>
On Sat, May 01, 2004 at 03:12:57PM +1000, skaller wrote:
> The term has no meaning without exhibiting implementation
> code, and it is usual for libraries to quite pointedly
> NOT do that: instead the behaviour is specified in
> terms of input and output of the function, and also
> side effects in terms of time and storage requirements
> are sometimes thrown in for more detail.
In many functional languages, O'Caml included, it's assumed that tail calls
are optimized to jumps, so that tail recursive functions do not allocate
any stack space for each recursive call. (I believe in Scheme this is even
included in the language specification.)
With that in mind, you can read "This function is not tail recursive" as a
behavioral specification, "This function might terminate abnormally due to
stack overflow" -- and that's a useful side effect to document.
William
-------------------
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:[~2004-05-01 7:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 17:54 [Caml-list] "List.index" or "List.unique" functions? Rahul Siddharthan
2004-04-30 18:51 ` Martin Jambon
2004-04-30 19:01 ` Benjamin Geer
2004-04-30 19:07 ` Thanks " Rahul Siddharthan
2004-04-30 19:08 ` Karl Zilles
2004-04-30 19:29 ` Matthieu Sozeau
2004-04-30 20:01 ` Karl Zilles
2004-04-30 20:05 ` Remi Vanicat
2004-04-30 20:47 ` JM Nunes
2004-04-30 20:58 ` Karl Zilles
2004-05-01 1:59 ` [Caml-list] List.rev skaller
2004-05-01 4:18 ` Jon Harrop
2004-05-01 4:38 ` brogoff
2004-05-01 5:12 ` skaller
2004-05-01 7:08 ` William Lovas [this message]
2004-05-01 8:10 ` skaller
2004-05-01 8:32 ` Jon Harrop
2004-05-01 9:24 ` skaller
2004-05-02 12:07 ` Andreas Rossberg
2004-05-02 13:29 ` skaller
2004-05-01 10:07 ` Richard Jones
2004-05-01 10:09 ` Nicolas Cannasse
2004-05-02 16:04 ` Brian Hurt
2004-05-01 10:32 ` Jon Harrop
2004-05-01 16:41 ` John Goerzen
2004-05-01 19:11 ` skaller
2004-05-01 10:03 ` [Caml-list] "List.index" or "List.unique" functions? Richard Jones
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=20040501070844.GB19707@force.stwing.upenn.edu \
--to=wlovas@stwing.upenn.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