I think this idea is probably not a good one, though your case is presented logically and well. My reasoning is that an OP getting an answer to a Perl question is only one part of the whole SoPW process and what it can offer us all.

First, a multitude of answers offers people many different ways of approaching a problem. Even though the OP may find one of these quite sufficient, it is good for people to see the wide variety of possibilities that are often available. Second, the OP may need something quick and dirty, just to get a particular job done, and will gladly take the first thing that works. And that's fine - that's what s/he needed at the time. But to stop the answers at that point may deny us from seeing some very creative, even eloquent possibilities. Some of the Perl idioms are truly works of art.

I think maybe the point I'm making is contained in the title of the section - 'Seekers of Perl wisdom'. Whether intentional or not, that title suggests that we're getting more than just answers to questions. We're getting the attitude behind the code, the Perlish ways of thinking that make this such a unique and fun language. The 'wisdom', as it says. Really, it's more than just 'Answers to Perl Questions'.

In reply to Re: indicating "the answer" by spiritway
in thread indicating "the answer" by qbxk

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.