You really need a parser. Using extended regexp features, you can write a parser in a regexp.
use strict;
use warnings;
my $text = <<'__EOI__';
<%def .errors>
missing_name: You must provide your name.
missing_email: You must provide your email address.
</%def>
__EOI__
# Perl code in regexps close over lexicals when
# the regexp is compiled. It's best to avoid
# using lexical variables declared outside the
# regexp in Perl code in regexps.
local our %errors;
$text =~ /
(?{ +{} })
<%def\ \.errors> \n
(?:
(\w+): \s* (.*) \n
(?{ +{ %{$^R}, $1 => $2 } })
)*
<\/%def> \n
(?{ %errors = %{$^R} })
/x
or die("Bad text\n");
for (keys %errors) {
print("$_ => $errors{$_}\n");
}
5.10 has features that make this even easier, but I haven't taken the time to look at them yet.
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.