Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

Interesting tangent about syntactic elegance ... I have not seen enough differences in Perl6 to say it has significant syntactic elegance over Perl5. Can you point out some specific examples?

You mention COBOL which I had the (mis)fortune of getting paid to program in for a short time back when I was a college intern. In addition to liberal GOTO use, the code was peppered with ALTER statements, which is COBOL's way of writing self modifying code. So, far from being elegant to maintain, it was a syntactically pleasing maintenance nightmare I inherited.

After that I worked on some easy to maintain C, then C++, then C code. C is really only a step or two above assembler if you look at it honestly. The reason for the ease of maintenance had less to do with the language than it did with the design and with the logical way the problems were abstracted and factored down to interfaces.

So I'm not sure I believe that syntactic changes will make a huge difference, although I agree with you that coming more towards that Java-like middle ground syntax helps those less capable programmers pick things up faster.

Then there's the Java code I inherited that had one method named main ...


In reply to Re^2: Critique of Where Perl 6 is Heading on Freshmeat.net by steves
in thread Critique of Where Perl 6 is Heading on Freshmeat.net by cyocum

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others musing on the Monastery: (4)
As of 2024-04-20 00:43 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found