I think a response to a posting of "I do not know how to split properly" should include a link to the documentation and the advice to read it, and of course I wish more people coming to post here would read the docs and Google their question first. But apparently you and the other anon have a different sense of rudeness than me. IMO:

Positive: "The split documentation describes its behavior well and contains several helpful examples. If you have any specific questions about split please don't hesitate to ask, and remember to follow the advice in 'How do I post a question effectively?' to get the most effective help."

Civil: "The split function is documented, with examples, in split."

Rude: "so read the documentation."

A pure "read the docs" without anything additional - which is what this whole little subthread is about - is entirely useless because the response "Why don't you go figure it out on your own?", whether rude or not, applies to every question asked here. As for rudeness, remember that RTFM has two equally valid synonyms: "Read The Fine Manual" and "Read The F**king Manual", and it is not civil. Even if the post in question isn't that rude, or maybe it wasn't even intended to be rude, it's still useless.

In reply to Re^8: Accessing Array of Arrays by Anonymous Monk
in thread Accessing Array of Arrays by GuiPerl

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.