caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: bcpierce@cis.upenn.edu
To: datta@math.berkeley.edu
Cc: caml-list@inria.fr
Subject: Re: Why Not Tail-Recursive?
Date: Thu, 26 Oct 2000 11:37:02 -0400	[thread overview]
Message-ID: <1249.972574622@silvercomet.emperorlinux.com> (raw)
In-Reply-To: Message from Ruchira Datta <datta@math.berkeley.edu>  of "Wed, 25 Oct 2000 23:57:38 PDT." <20001025235738.A7286@blue1.berkeley.edu>

> The only thing I can think of is that the functions deepen and next_path
> are not actually tail-recursive as I expected them to be.  But why not?  

Because each call installs a new exception handler.  To make them
tail-recursive, you need to change the style a little (e.g., make them
return an option instead of raising an exception).

       B



  reply	other threads:[~2000-10-26 18:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-26  6:57 Ruchira Datta
2000-10-26 15:37 ` bcpierce [this message]
2000-10-26 16:30 ` hubert.fauque
2000-10-26 16:55 ` Alain Frisch
2000-10-26 17:24 ` John Prevost
2000-10-26 21:09 Ruchira Datta

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=1249.972574622@silvercomet.emperorlinux.com \
    --to=bcpierce@cis.upenn.edu \
    --cc=caml-list@inria.fr \
    --cc=datta@math.berkeley.edu \
    /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).