From: David Reitter <david.reitter@gmail.com>
Cc: anton.belyaev@gmail.com
Subject: Re: to big nest level of recursion
Date: Tue, 21 Mar 2006 21:31:29 +0000 [thread overview]
Message-ID: <0E851319-E5C4-4617-872F-29459A5970BB@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 680 bytes --]
> 2) Pascal Bourguignon mentioned TCO. Is it relatively right recursion
> handling? Why does it works only with boolean expressions? I thought
> that it is enougth to make recursive call the last in the expression
> (as it is in Haskell). Where can I read about it?
TCO = tail call optimization, just what you were referring to.
In Prolog, I'd formulate the algorithm just like you did. In elisp,
you can't, because stack size is small and there is obviously no TCO.
http://en.wikipedia.org/wiki/Tail_recursion
Maybe it's a consolation for you that for every recursive algorithm,
you can formulate an iterative version. And you don't bloat a call
stack when you do so.
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2454 bytes --]
[-- Attachment #2: Type: text/plain, Size: 152 bytes --]
_______________________________________________
help-gnu-emacs mailing list
help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
next reply other threads:[~2006-03-21 21:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 21:31 David Reitter [this message]
[not found] <mailman.21.1142976703.14011.help-gnu-emacs@gnu.org>
2006-03-25 10:30 ` to big nest level of recursion Alan Mackenzie
2006-03-25 11:46 ` David Kastrup
2006-04-04 13:36 ` david.reitter
-- strict thread matches above, loose matches on Subject: below --
2006-03-20 12:35 Anton V. Belyaev
2006-03-20 12:45 ` Hans-Christoph Wirth
2006-03-20 12:51 ` David Kastrup
2006-03-20 13:52 ` Pascal Bourguignon
2006-03-20 15:56 ` Anton V. Belyaev
2006-03-21 17:09 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0E851319-E5C4-4617-872F-29459A5970BB@gmail.com \
--to=david.reitter@gmail.com \
--cc=anton.belyaev@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).