Re: Regular Expression multi-match not as expected

On Wed, 2010-02-03 at 11:11 -0500, Dennis Lovelady wrote:

Folks, I'm getting unexpected result from Regular Expression matching on
System i at V5R3. You can see the code in question at
http://code.midrange.com/e15d4eb99d.html.



I expect the expression to match on both the word "one" and the second
position of the word "none" but the search seems to stop after the first
match. (I can see that it has initialized all elements of match, however,
for whatever that's worth.) To see the issue, run in debug mode and set a
breakpoint at the line that contains "Match(es)". At that point, rc should
be zero (and it is); the first element of match should point to the second
character of done. (all good so far). But the second element of match
should point to the word "one" and it doesn't.



Can you see what might be wrong with this? Thanks.

The "first" match that you see is the *whole* match. For up to two
submatches, you might want to try regular expression
\(one\).*\(one\)
and look at match(2) and match(3). match(1) will point to the string
"one but the one".

If, on the other hand, you want to find all the matches without
committing ahead of time to how many there might be, I think you have
call regexec in a loop, advancing the point where you start the search.

Cheers,
Terry.

Dennis E. Lovelady
AIM: delovelady MSN: fastcounter@xxxxxxxxxxxx
<http://www.linkedin.com/in/dennislovelady>
www.linkedin.com/in/dennislovelady --
"Nothing makes you more tolerant of a neighbor's noisy party than being
there."
- Franklin P. Jones