It would be interesting to see just how many lines of Perl you need to trigger the same functionality as this example.
That's not a fair comparison, for several reasons:
- SLOC isn't an interesting metric until you get to orders of magnitude difference
- Comparing a framework to something at a different abstraction level is misleading
- There's running Perl code behind the aXML example that looks much like the eventual Perl code someone would have to write anyway
- SLOC isn't the only meaningful concern. Consider syntax checking or highlighting, or debugging, or testing. The Perl infrastructure and toolchain has quite a few advantages over aXML due to its maturity
I'm not saying aXML lacks its advantages, but concision alone isn't such a meaningful metric.
Also your example Perl 5 code has a security hole. (We've talked about this before.)
-
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.
|
