Thanks, that's an interesting approach. I find the logic still rather complex, though, and I think if I were going in this direction I'd separate it out a bit differently: 

  while (pos($tag) < length($tag)) {
    if (m{ \G (\w+) \s* = }gcx) {
      push @args [ $1 ];
    } elsif (m{ \G (\w+) (?= \s* | \z ) \s* }gcx) {
      push @args, $1;
    } elsif (m{ \G (['"]) ( \\. | [^\\] )*? \1 \s* }gcx) {
      (my $quoted = $2) =~ s/\\(.)/$1/g;
      push @args, $quoted;
    } else {
      die "parsing error\n";
    }
  }
  for (my $i = 0; $i < @args; ++$i) {
    $args[$i][1] = splice(@args, $i + 1, 1) if ref $args[$_];
  }

[download]

Hugo

In reply to Re: Re: Parsing arguments by hv
in thread Parsing arguments by hv

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.