Logic that attempts to do this "by hand" becomes extremely specific to the XML data structure that was originally parsed when it was originally written, and can be extremely difficult to accurately update when the XML definition changes.
This sentence could just as well apply to XSLT. Properly written Perl code will be easy to adapt to changes in the XML.
Fully-leveraging XML technologies via these standard binaries eliminates great code complexity
I've written XSLT, and I found its syntax somewhat cumbersome.
Plus, Perl is much more powerful (regexes, the ability to access other data sources like databases, JSON, and so on). Sorry, I currently don't see the strength of your argument for XSLT. But perhaps you could write an XSLT solution that demonstrates its advantages.
-
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.
|
