Even though I am far from being a computer linguist, I can see the need for Perl 6. If Perl 5 was syntactily as pretty as Python for doing OO programming, I wouldn't be building a event driven application using Python (and having to learn Pythons's very wierd excentricities most of which come from it's lack of value assignment.). I have written tens of thousands of lines of OO-perl5, but am embarassed to pass off maintenance of this code to a non-Perl programmer.
Perl 6 syntax is far more elegant. This is important. It may be fun to write obfusticated code, but applications that require maintenance should be easy to follow. (No, I'm not a COBOL programmer ;-) I mean, easy to follow by another programmer.. who may actually be me looking at my own code two years from now after having done a dozen other projects in between. H___, I have trouble recognizing my own English text as written by me, years later.
Perlhaps, if and when Perl6 is developed and released, it will be called something other than Perl! Stranger things have happened.
-
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.
|
