tybalt89 is combining the \G meta with //gc modifiers
- \G achors the search at the pos where the last regex left off
- unless you used the //c modifier, the pos of a previous regex was erased when it didn't match
This allows to split a big complicated regex into multiple perl statements.
And after combining with recursive calls this permits to parse nested structures.
See perldocs for examples and details of this technique (e.g. perlretut ) or Friedl's Regex Book.
Or even better older threads in the monastery :)
You shouldn't be despaired, the demonstrated code is neither easy to read nor maintain.
It should better use //x modifiers and more comments, but obfuscated wizardry is of course cooler! ;-))
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.