[cl-ppcre-devel] possible bug with non-word boundaries and greedy matching

28 Mar
2012
28 Mar
'12
12:52 a.m.
I have an odd little regular expression \B.* that seems to generate inconsistent behavior between CL-PPCRE and other regular expression engines that I've tried it with. Using CL-PPCRE: CL-USER> (cl-ppcre::scan "\\B.*" "foo bar baz") NIL This matches in Perl, PPCRE, and RE2. Am I missing something, or should CL-PPCRE be matching this as well? Oddly enough, change * to + leads CL-PPCRE to match: CL-USER> (cl-ppcre::scan "\\B.+" "foo bar baz") 1 11 #() #() It seems like + matching implies that * should as well... Thanks, Moshe
4843
Age (days ago)
4843
Last active (days ago)
0 comments
1 participants
participants (1)
-
Moshe Looks