Out of interest with the experimental ?>, I did a benchmark with the following little test:
use Benchmark;
$str1 = "_test (folloed by 1 or more spaces)";
$str2 = "_test < xxx >";

timethese ( 1000000,
            { 'p1' => '&p1;',
              'p2' => '&p2;',
              'p3' => '&p3;',
              'p4' => '&p4;',
             } );

sub p1 ()
{
    $str1 =~ /_test(?>\s+)(?!<)/;
}

sub p2 ()
{
    $str1 =~ /_test(?:\s+)(?!<)/;
}

sub p3 ()
{
    $str2 =~ /_test(?>\s+)(?!<)/;
}

sub p4 ()
{
    $str2 =~ /_test(?:\s+)(?!<)/;
}

[download]
I got the following results:
Benchmark: timing 1000000 iterations of p1, p2, p3, p4...
        p1:  3 wallclock secs ( 3.00 usr +  0.00 sys =  3.00 CPU)
             @ 333333.33/s (n=1000000)
        p2:  3 wallclock secs ( 2.79 usr +  0.00 sys =  2.79 CPU)
             @ 358422.94/s (n=1000000)
        p3:  3 wallclock secs ( 3.09 usr +  0.00 sys =  3.09 CPU)
             @ 323624.60/s (n=1000000)
        p4:  3 wallclock secs ( 2.82 usr +  0.00 sys =  2.82 CPU)
             @ 354609.93/s (n=1000000)

[download]
It seems that the ?> runs slower than ?: matching by as much as 10 percent. So am I correct to say that optimization wise, the ?> might not be the first choice?

In reply to Re: Re: parsing question by Roger
in thread parsing question by Washie101

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.