From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Str, regular expressions, longest match
Date: Wed, 01 Oct 2014 18:28:16 +0200 [thread overview]
Message-ID: <542C2BA0.8020900@inria.fr> (raw)
In-Reply-To: <CABooLwNvJ_4frafqjjV0zpoDbduAV5MmVjdrNL=o3ibgMEVoLg@mail.gmail.com>
On 29/09/14 22:04, Tom Ridge wrote:
> I am trying to use the Str module to match regular expressions. I want to
> return the longest match.[...] I don't want the order of
> the alternatives to matter. What am I doing wrong?
Nothing: it's just that Str has first-match semantics, not longest-match.
> What can I do to match the longest substring?
In this particular example, you can sort the string patterns in
decreasing lexicographic order before putting them in ...|...|...
In more general case, you might have more luck with other regexp
libraries (e.g. PCRE or Vouillon's RE, but I didn't check whether they
implement longest match).
Hope this helps,
- Xavier Leroy
next prev parent reply other threads:[~2014-10-01 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 20:04 Tom Ridge
2014-09-30 12:47 ` Christophe Raffalli
2014-10-01 16:28 ` Xavier Leroy [this message]
2014-10-01 19:10 ` Tom Ridge
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=542C2BA0.8020900@inria.fr \
--to=xavier.leroy@inria.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;
as well as URLs for NNTP newsgroup(s).