That beta does fix that issue, but I consider its behaviour with the following line to be wrong: 
my %hash : Test('one', 'two', 'three)');

[download]
Any human looking at this would say that the first closing paren is inside of a quoted string, and so this code is correct. But Attribute::Handlers disagrees. It is perfectly willing to stop at the first paren, and claim that the passed argument was the string: 
"'one', 'two', 'three"

[download]
And therefore the following quote is interpreted differently than it should be.

I assume that this is due to the heuristics it uses to parse Perl. If it is hard to fix (as I assume) then it is probably something to solve in 6.0. But I think it is a gotcha worth noting, along with the workaround: 

my %hash : Test('one', 'two', 'three\)');

[download]

In reply to Re (tilly) 3: autotie in Attribute Handlers by tilly
in thread autotie in Attribute Handlers by davorg

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.