In fact the difference you are showing stems from 2 things: mostly that XSLT uses a tree-model while HTML::TokeParser::Simple uses a low-level pull model. The fact that XSLT has an encode_entities function instead of the longer HTML::Entities::encode_entities also makes the XSLT code look nicer.

Using a tree-based module, XML::LibXML or XML::Twig for example, would lead to code that would look very similar to the XSLT one.

As for the vaunted difference between what ("state the section you want") and how (select the section you want by navigating, or by using XPath)... frankly I don't see whatthe big deal is.

In reply to Re: Re: Why XSLT and not just Perl? by mirod
in thread Why XSLT and not just Perl? by blahblah

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.