From: Francois Berenger <berenger@riken.jp>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Fwd: interval trees
Date: Fri, 17 Feb 2012 09:59:59 +0900 [thread overview]
Message-ID: <4F3DA68F.1030402@riken.jp> (raw)
In-Reply-To: <CAPFanBGxE0Mtv0sBzaZqseZOyH406qq2_4Aq-h9s0UX01G-10Q@mail.gmail.com>
On 02/16/2012 07:21 PM, Gabriel Scherer wrote:
> I can't resist giving the usual tail-recursive CPS-transformed version
> (untested):
Thanks! That's the technique I was looking for
(Continuation Passing Style), as I may have to use
this on some other algorithms in the future.
> let interval_tree intervals =
> let rec interval_tree intervals k =
> match intervals with
> | [] -> k Empty
> | _ ->
> let x_mid = median intervals in
> let left, mid, right = partition intervals x_mid in
> let left_list = L.sort leftmost_bound_first mid in
> let right_list = L.sort rightmost_bound_first mid in
> interval_tree left (fun left_tree ->
> interval_tree right (fun right_tree ->
> k (Node(x_mid, left_list, right_list, left_tree, right_tree))))
> in interval_tree intervals (fun t -> t)
>
> But see Goswin's remark: if non-tailrec makes your stack grow in
> log(n) only, there is no point in jumping through hoops to get a
> tail-recursive version.
>
> On Thu, Feb 16, 2012 at 3:42 AM, Francois Berenger<berenger@riken.jp> wrote:
>> Hello,
>>
>> Anyone can translate this into being tail recursive
>> if it's possible:
>>
>> let rec interval_tree intervals =
>> match intervals with
>> [] -> Empty
>> | _ ->
>> let x_mid = median intervals in
>> let left, mid, right = partition intervals x_mid in
>> let left_list = L.sort leftmost_bound_first mid in
>> let right_list = L.sort rightmost_bound_first mid in
>> Node (x_mid,
>> left_list, right_list,
>> interval_tree left, interval_tree right)
>>
>> I'm afraid my program could crash on a very long list of intervals.
>>
>> Thanks a lot,
>>
>> F.
>>
>> --
>> Caml-list mailing list. Subscription management and archives:
>> https://sympa-roc.inria.fr/wws/info/caml-list
>> 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:[~2012-02-17 1:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 1:07 Francois Berenger
2012-02-10 18:29 ` Richard W.M. Jones
2012-02-11 17:38 ` Goswin von Brederlow
2012-02-11 17:49 ` Eliot Handelman
2012-02-13 9:13 ` Sebastien Ferre
2012-02-15 1:28 ` Francois Berenger
2012-02-15 15:21 ` Goswin von Brederlow
2012-02-15 17:22 ` Edgar Friendly
2012-02-16 2:48 ` Francois Berenger
2012-02-16 2:32 ` Francois Berenger
2012-02-16 2:42 ` Francois Berenger
2012-02-16 8:34 ` Goswin von Brederlow
2012-02-16 12:20 ` John Carr
2012-02-16 10:21 ` Gabriel Scherer
2012-02-17 0:59 ` Francois Berenger [this message]
2012-02-17 8:11 ` Christophe Raffalli
2012-02-11 20:49 ` Edgar Friendly
2012-02-11 23:54 ` Philippe Veber
2012-02-11 10:54 ` Philippe Veber
2012-02-11 17:33 ` Goswin von Brederlow
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=4F3DA68F.1030402@riken.jp \
--to=berenger@riken.jp \
--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;
as well as URLs for NNTP newsgroup(s).