a 'nice' from the module author... i'm honored... ;=)

I never noticed this feature of $_ set to $_[1] (or well, i used incosciously..)

May be worth to add some line in the Synopsis: 
para    => sub { $_[1]->set_tag( 'p')  }, # change para to p (handlers
+ receive $twig and $element as argouments)
para    => sub { $_->set_tag( 'p')  },    # change para to p ($_ is al
+iased to $_[1] for convenience  )


###and in the corpus of the docs:

$_ is also set to the element (ie: $_[1]), so it is easy to write inli
+ne handlers like

[download]


L*
There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.

In reply to Re^4: Easy XML-parser that can handle large file? by Discipulus
in thread Easy XML-parser that can handle large file? by DreamT

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.