From: Kurt Welgehausen <kaw@kwel.net>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Str.string_match incorrect
Date: Wed, 22 Dec 2004 11:26:11 -0600 [thread overview]
Message-ID: <41C9AE33.mailBIK17BLGN@kwel.net> (raw)
In-Reply-To: <1103731044.6979.109.camel@pelican.wigram>
> 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.
>
> Then they're simply wrong. The fundamental operation is
> to check if a string is in a regular set of strings.
> Plainly 'aa' is not in the set { 'a' }.
Str.string_match is almost exactly the same as Python's
re.match:
# Str.string_match (Str.regexp "a") "ab" 0 ;;
- : bool = true
>>> re.match(re.compile("a"), "ab") #succeeds
<_sre.SRE_Match object at 0x8146f60>
# Str.string_match (Str.regexp "a") "bab" 0 ;;
- : bool = false
>>> re.match(re.compile("a"), "bab") #returns None
>>>
# Str.string_match (Str.regexp "a") "bab" 1 ;;
- : bool = true
>>> re.match(re.compile("a"), "bab"[1: ])
<_sre.SRE_Match object at 0x814c748>
>>> #Python has no parameter to change the start position
Regards
next prev parent reply other threads:[~2004-12-22 17:26 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
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 [this message]
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=41C9AE33.mailBIK17BLGN@kwel.net \
--to=kaw@kwel.net \
--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