Reply to Update.
Read the paragraph you quoted above very carefully.....
The regex engine works something like this: it moves from left to right, checking each alternation in order before moving on to the next position in the string.
Now, lets consider the pattern /(a|b|c)/
against the string 123abc. In the following diagram
'^' denotes the current position in the string. The "pointer" gets moved one char to the right after each stanza:
($txt = '123abc') =~ /(a|b|c)/;
1. ^123abc - check for a -> fail
- check for b -> fail
- check for c -> fail
2. 1^23abc - check for a -> fail
- check for b -> fail
- check for c -> fail
3. 12^3abc - check for a -> fail
- check for b -> fail
- check for c -> fail
4. 123^abc - check for a -> succeess, $1 becomes 'a'
Here are a few others, to illustrate the point.
($txt = 'barefoot') =~ /(foo|foot)/;
1. ^barefoot - check for foo -> fail
- check for foot -> fail
2. b^arefoot - check for foo -> fail
- check for foot -> fail
3. ba^refoot - check for foo -> fail
- check for foot -> fail
4. bar^efoot - check for foo -> fail
- check for foot -> fail
5. bare^foot - check for foo -> success, $1 becomes 'foo'
Here, 'foo' beats 'foot' because they match at the same spot in the string, and foo is listed first in the alternation. The leftmost match will always win, the order they are listed in the alternation is merely a tie breaker.
And the one in question (slightly shortened)..
($txt = 'arvec') =~ /(ar|ec|vec)$/
1. ^arvec - check for ar$ -> fail (because of the end-of-string anch
+or)
- check for ec$ -> fail
- check for vec$ -> fail
2. a^rvec - check for ar$ -> fail
- check for ec$ -> fail
- check for vec$ -> fail
3. ar^vec - check for ar$ -> fail
- check for ec$ -> fail
- check for vec$ -> success, $1 becomes 'vec'
Notice how 'ec' *would* match in the next stanza ("arv^ec"), but we never get that far. The first match wins, and in this situation it is the one we want.
Now, go back and read that paragraph you quoted again... does it make more sense now?
-Blake
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.