I expect that option 1 would be the most efficient.
Option 2 as originally described doesn't work (but see Tye's response below), because when a match fails, pos gets reset, so it won't be at the end of the string. Instead, you have to set a flag by testing pos against length within the loop:
while (<DATA>) {
my @accum;
my $ate_the_whole_thing = 0;
while (/\G$item_regex/g) {
push @accum, [$1, $2, $3];
$ate_the_whole_thing = (pos() == length);
}
if ($ate_the_whole_thing) {
print join ',', @$_, "\n" for @accum;
}
}
Option #3 would put a lookahead in the iterative match, which is expensive (as I noted), but does work:
while (<DATA>) {
my @accum;
push @accum, [$1, $2, $3] while (/\G$item_regex(?=$item_regex*\Z)/g)
+;
print join ',', @$_, "\n" for @accum;
}
Caution: Contents may have been coded under pressure.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.