From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id q1BHY1bB004830 for ; Sat, 11 Feb 2012 18:34:01 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqwCAKilNk/ZSMDdjmdsb2JhbABEr3QiAQEBAQkLCQkSBSSBcgEBBAEyAT8HBQsLISUPAQQNGyETh3wDslSIRIJ7MhkGBAcCAhsBAwYCARQGBAUDAYNehB0EmnmFSYdV X-IronPort-AV: E=Sophos;i="4.73,403,1325458800"; d="scan'208";a="130987539" Received: from fmmailgate01.web.de ([217.72.192.221]) by mail4-smtp-sop.national.inria.fr with ESMTP; 11 Feb 2012 18:33:55 +0100 Received: from moweb001.kundenserver.de (moweb001.kundenserver.de [172.19.20.114]) by fmmailgate01.web.de (Postfix) with ESMTP id 820F21AA56CBF for ; Sat, 11 Feb 2012 18:33:55 +0100 (CET) Received: from frosties.localnet ([95.208.118.96]) by smtp.web.de (mrweb002) with ESMTPA (Nemesis) id 0MK2JZ-1RvRUC3gA9-001fCR; Sat, 11 Feb 2012 18:33:54 +0100 Received: from mrvn by frosties.localnet with local (Exim 4.77) (envelope-from ) id 1RwGpd-0000KK-4i; Sat, 11 Feb 2012 18:33:53 +0100 From: Goswin von Brederlow To: Philippe Veber Cc: Francois Berenger , caml-list@inria.fr References: <4F346DB9.2070303@riken.jp> Date: Sat, 11 Feb 2012 18:33:53 +0100 In-Reply-To: (Philippe Veber's message of "Sat, 11 Feb 2012 11:54:39 +0100") Message-ID: <871uq1cm0u.fsf@frosties.localnet> User-Agent: Gnus/5.110009 (No Gnus v0.9) XEmacs/21.4.22 (linux, no MULE) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Provags-ID: V02:K0:8L0c0vtbp21xP81GmRgNoWuIx7tgjsqJsp4rHc8xl/1 hpyMPKkThOdz+c2tE+6oUNxCgDiY4333TObonzyXIJjGW95sEA nQIz5JS7qZalAQ89PUh5S9C6hXVV72gcOWd4BkWSxiNsv6TMXP J9GjrxYB1nowflDBCwP4blNDkpa02Ci09ZiTSq3GxFzlKzmNWi N7CoKkkrI2L1k0BPMJGWg== Subject: Re: [Caml-list] Fwd: interval trees Philippe Veber writes: > Hi François, > > The Biocaml_intervalTree module is merely a specialization of Set in the > standard library. It should be fairly easy to functorize it over a type with a > total order relation. I think you might even sed -e 's/int/float/g' the current > implementation (with a couple of additional and minor modifications). > > ph. Even better would be to polymorphize or functorize the code and send the patch upstream. MfG Goswin