From: William Lovas <wlovas@stwing.upenn.edu>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Str.string_match incorrect
Date: Wed, 22 Dec 2004 03:00:10 -0500 [thread overview]
Message-ID: <20041222080009.GA4501@force.stwing.upenn.edu> (raw)
In-Reply-To: <20041222074455.GA81342@trout>
On Tue, Dec 21, 2004 at 11:44:55PM -0800, Evan Martin wrote:
> This is consistent with the docs, which say:
> [string_match r s start] tests whether the characters in s starting at
> position start match the regular expression r.
> and in general with how regular expression systems work. string_match
> corresponds to running your automaton directly and seeing whether you
> end up in an accept state, while string_partial_match effectively adds
> an extra ".*" to the beginning.
> (It's more debatable whether this makes sense.)
I concur with your assessment, but i think you're characterization of the
semantics of string_partial_match is inaccurate:
# Str.string_match (Str.regexp "ab") "a" 0;;
- : bool = false
# Str.string_partial_match (Str.regexp "ab") "a" 0;;
- : bool = true
# Str.string_match (Str.regexp ".*ab") "a" 0;;
- : bool = false
... unless of course, i've misunderstood you. I don't think there's a
simple transformation on regular expressions that allow you to emulate
string_partial_match's behavior using only string_match. (Does anyone
care to prove me wrong? :)
cheers,
William
next prev parent reply other threads:[~2004-12-22 8:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 3:49 skaller
2004-12-22 7:44 ` [Caml-list] " Evan Martin
2004-12-22 8:00 ` William Lovas [this message]
2004-12-22 8:38 ` Evan Martin
2004-12-22 10:37 ` Gerd Stolpmann
2004-12-22 15:57 ` skaller
2004-12-22 16:58 ` David Brown
2004-12-23 2:33 ` skaller
2004-12-24 17:40 ` Christopher A. Watford
2004-12-25 0:57 ` skaller
2004-12-25 3:07 ` Christopher A. Watford
2004-12-25 4:24 ` skaller
2004-12-26 1:14 ` William Lovas
2004-12-22 17:26 ` Kurt Welgehausen
2004-12-23 2:09 ` skaller
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=20041222080009.GA4501@force.stwing.upenn.edu \
--to=wlovas@stwing.upenn.edu \
--cc=caml-list@yquem.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