So the APL library on cpan6 is not far away and all those old financial programs not written in COBOL will be moved over from ancient mainframes to perl. Hooray ;-)

Terseness is not a problem in itself. No one likes to type 'System.out.println' instead of 'print' (one of the reasons I never got around programming in java).

The problems begin when the redundancy is so low and the feature density so high that you can replace or add one single punctuation character or even a space and the statement is with high probability still syntactically correct and does something totally different.

perl already has a reputation as a obfuscated language, this reputation might even get worse with perl6. I've gotten a lot better reading perl code since I've started posting here on perlmonks, but I still get the uneasy feeling occassionaly that the bug I identified in some users code might be valid syntax that I just forgot. Just a few days ago I saw that someone had typed =\ instead of =~ in his code. To my surprise the whole statement was still valid syntax but I couldn't say why at first. With the explosion of (syntactically) overloaded/reused punctuation characters in perl6 I fear I might get that surprise a lot more often

Don't get me wrong, I like perl6 and the freedom of picking all the bits I like out of the language will make me a happy coder. And my fears are probably based on ignorance and an overdose of apocalypses read a long time ago. But my impression was that perl6 syntax has twice or three times as many constructs/elements as perl5 and instead of using words to make those constructs easily distinguishable, another layer of meaning is heaped upon some punctuation character.

brackets have 4 uses in perl5 depending on context, caret three and colons two. In perl6 each has a lot more (if my impression is correct). Apart from the poor people who have to write the perl6 parser what about the humans who have to parse it?

In reply to Re^3: A Romp Around addn by jethro
in thread A Romp Around addn by John M. Dlugosz

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.