From: Christophe Raffalli <raffalli@univ-savoie.fr>
To: caml-list@inria.fr
Subject: try and tail call
Date: Sat, 21 Oct 2006 16:00:11 +0200 [thread overview]
Message-ID: <453A27EB.8070609@univ-savoie.fr> (raw)
consider this piece of code:
(try
let b = f a in
(fun () -> g b)
with
(fun () -> h a)) ()
Is the call to "g" a tail call and is it omptimized as such ?
If not, how to encode a feature like this one:
try
...
end
... (* the exception raised here are not handles by with but
propagated *)
with
...
By the way I think this "try ... [end ...] with ..." syntax is usefull
anyway because you have often a bug when
you write
try
let b = f a in (* you know this may raise Not_found *)
g b (* you assume wrongly that this can not raise Not_found *)
with
Not_found -> h a
The unwanted capture of Not_found could be avoided with try ... end ...
with ...
Christophe Raffalli
next reply other threads:[~2006-10-21 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-21 14:00 Christophe Raffalli [this message]
2006-10-21 15:03 ` [Caml-list] " Chris King
2006-10-22 17:16 ` Christophe Raffalli
2006-10-22 2:44 ` ketty
2006-10-22 17:08 ` Christophe Raffalli
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=453A27EB.8070609@univ-savoie.fr \
--to=raffalli@univ-savoie.fr \
--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