From: Andres Varon <avaron@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Reporting on sucess/failure of tail recursion
Date: Sat, 3 Dec 2005 23:11:06 -0500 [thread overview]
Message-ID: <B77F9062-C657-4983-9A3D-7CB618B0CE6F@google.com> (raw)
In-Reply-To: <20051203002821.44840.qmail@web30515.mail.mud.yahoo.com>
While exploring the (undocumented) options of ocamlopt I discovered
once that -dlinear explicitly says if a function is a tailcall or
not. It has worked consistently for me whenever I needed to check
this afterwards.
Andres
On Dec 2, 2005, at 7:28 PM, David Thomas wrote:
> Particularly with respect to list operations,
> "non-tail-recursive" usually implies stack space used
> is O(n) to the length of the list, whereas "tail
> recursive" implies O(1). I, for one, would love to
> see these figures explicitly, instead.
>
> --- skaller <skaller@users.sourceforge.net> wrote:
>
>> What needs to be documented for a library function
> is its
>> complexity (time/space etc). In this sense the
> documentation
>> of the C++ Standard Library should be taken as an
> examplar.
>
>
>
>
> __________________________________
> Start your day with Yahoo! - Make it your home page!
> http://www.yahoo.com/r/hs
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
next prev parent reply other threads:[~2005-12-04 4:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-03 0:28 David Thomas
2005-12-04 4:11 ` Andres Varon [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-02 9:09 Erik de Castro Lopo
2005-12-02 9:13 ` [Caml-list] " Jonathan Roewen
2005-12-02 9:25 ` Erik de Castro Lopo
2005-12-02 9:29 ` basile
2005-12-02 10:16 ` Erik de Castro Lopo
2005-12-02 15:17 ` Jean-Christophe Filliatre
2005-12-02 23:58 ` skaller
2005-12-02 10:45 ` David MENTRE
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=B77F9062-C657-4983-9A3D-7CB618B0CE6F@google.com \
--to=avaron@gmail.com \
--cc=caml-list@yquem.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