From: Sebastien Ferre <Sebastien.Ferre@irisa.fr>
To: Jon Harrop <jon@ffconsultancy.com>, caml-list@inria.fr
Subject: Re: [Caml-list] Suffix trees
Date: Fri, 31 Aug 2007 10:25:03 +0200 [thread overview]
Message-ID: <46D7D05F.6040907@irisa.fr> (raw)
In-Reply-To: <200708131017.47871.jon@ffconsultancy.com>
Hi,
Jon Harrop wrote:
> Anyone got any high-performance suffix tree implementations in OCaml? (I've
> seen Jean-Christophe's)
you can find the implementation I made for my
own needs at http://www.irisa.fr/LIS/ferre/software.en.html .
I hope it will fit your needs. I thrived to make it
efficient.
It is possible to make it more efficient by
removing the code for the computation of maximal substrings
that makes the computation of the suffix tree in O(n.ln(n))
instead of O(n).
The motivation for the computation of these maximal substrings
can be found in the following paper:
http://www.springerlink.com/content/a2p06g831821054g/
Do not hesitate to ask me explanations about the interface
as the comments are rather limited :-).
Cheers,
Sébastien Ferré
prev parent reply other threads:[~2007-08-31 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 9:17 Jon Harrop
2007-08-31 8:25 ` Sebastien Ferre [this message]
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=46D7D05F.6040907@irisa.fr \
--to=sebastien.ferre@irisa.fr \
--cc=caml-list@inria.fr \
--cc=jon@ffconsultancy.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 NNTP newsgroup(s).