I meant my post(reply) being a flame. Whenever I've pointed out a perl 6 issue, it's usually met with "Troll" instead of addressing the actual content of my words, so it was about my post, in response to yours. I was talking about perl 6, yes. As far as language agnosticism goes, maybe it's more polytheist? It borrows arrow syntax, dot syntax, weird syntax from Mars, syntax from Python specifically, whitespace matters (sometimes), on and on... not aligning itself to any bias completely and that was my reasoning for my reply. I've been meaning to make a meditation on it and describe this point fully, but nothing directed at the quality of your response, only adding to the perl 6 part.

In reply to Re^5: functional functions by Zen
in thread functional functions by punkish

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.