Your honor the jury rules on the following counts.
- clearer, more concise syntax
- Charges not proved. Clearer != more concise sysntax. As has been mentioned many times with regard to sigils, a core perl design object was that different types of things should look different so as to reduce confusion
- a shorter path to producing autogenerating documentation
- Not proved. I wrote a simple but effective tool to add pod to an arbitray module class and it only took me an hour. But thats cause I used one of the most sophisticated regex engines there is: Perl.
- having to only worry about, maybe, 4-5 different styles to maintain vs. 20
- Not proved your honor. Complaints like this are redundant in the face of autoindenters like Emacs and PerlTidy. Does Python have a tidier?
- far fewer rules to remember
- Irrelevant. Try doing complicated things with simple tools and the result is convoluted.
Yves / DeMerphq
Writing a good benchmark isnt as easy as it might look.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.