Exactly. In more detail, what the original regex ends up doing goes like this:
<%start_(.*?)\s*(.*?)\s*%>\n?(.+?)<%end_\1%>\n?
$1- -A- $2- -B- $3- C-
Quickly matches <%start_
Tries $1 matching ""
Tries A matching ""
Tries $2 matching "wibble XXX"
Tries $3 matches to just before "<%end_flub%>"
Is forced to backtrack by C
Tries $3 matches to just before "<%end_wibble%>"
Is forced to backtrack by C
Tries $1 matching "w"
Tries A matching ""
Tries $2 matching "ibble XXX"
Tries $3 matches to just before "<%end_flub%>"
Is forced to backtrack by C
Tries $3 matches to just before "<%end_wibble%>"
Is forced to backtrack by C
Tries $1 matching "wi"
Tries A matching ""
Tries $2 matching "bble XXX"
Tries $3 matches to just before "<%end_flub%>"
Is forced to backtrack by C
Tries $3 matches to just before "<%end_wibble%>"
Is forced to backtrack by C
...
Tries $1 matching "wibble"
Tries A matching " "
Tries $2 matching "XXX"
Tries $3 matching to just before "<%end_flub%>"
Is forced to backtrack by C
Tries $3 matches to just before "<%end_wibble%>"
Succeeds finding one match
which you can see wastes a lot of time.
That is one reason why Death to dot star! suggests you use character class
instead of . whenever possible in a regex.
- tye
-
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.
|