Here's a variation on the above solution,
using named recursive subpatterns and named captures.
Nowadays I write all my non-trivial regexes this way.
use 5.010;
my $source = 'function convert(beg string, end string, read_date date,
+ step char(6)) returns (date, date, char(1))';
my $matched =
$source =~ m{
\A \s*+
(?<access> private | public )?+ \s*+
(?<keyword> function | report ) \s*+
(?<name> (?&identifier) ) \s*+
(?<params> (?&list) ) \s*+
(returns \s*+ (?<returns> (?&list) ) )?+
\s*+ \z
(?(DEFINE)
(?<identifier> [^\W\d]\w*+ )
(?<list> [(] [^()]*+ (?: (?&list) [^()]*+ )*+ [)] )
)
}xms;
if ($matched) {
my %components = %+;
use Data::Dumper 'Dumper';
say Dumper \%components;
}
else {
say 'parse failed';
}
which outputs:
$VAR1 = {
keyword => 'function',
name => 'convert',
params => '(beg string, end string, read_date date, step char(6))',
returns => '(date, date, char(1))',
};
-
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>
<u> <ul>
-
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
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.