I agree on the two-step approach (at least for now
1), but I'd reverse the specificity of the regexes: I'd first do the validation using a specific regex and in a second phase split out the data you want from the capture in the first, which might be using a simpler regex because you validated the data already:
while (<DATA>) {
my ($params) = /^foo ((?:m \d+ *)*) bar$/;
my @nums = $params=~ /\d+/g;
print "$params -> (@nums)\n";
}
__DATA__
foo m 1 m 2 m 3 m 4 bar
foo m 2 m 4 m 7 bar
foo m 1 bar
1 Looking at demerphq's slides on his work on extended regexes in Perl 5.10, it might become possible to have a simpler, single step solution in the near future. See %-.
But maybe I'm just dreaming.
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.