Code is a poor CPAN.

If it was meant as CPAN, then it would've been a poor CPAN. It's hardly meant as that, but as a collection of working examples, scripts, utilities, proof of concepts, how-to's, recipes, implementation of design patterns, workarounds, macros, joke programs, and whatever else you don't go to CPAN to look for. RFC's can go to meditations.

Also, there are many levels of Perl programmers, and at the early-to-mid levels, reading code is a great way of learning. CPAN is meant for a sort of "black box" usage, not for displaying code examples that should be abused and edited.

Software speaks in tongues of man.
Stop saying 'script'. Stop saying 'line-noise'.
We have nothing to lose but our metaphors.

In reply to Re^4: Shut down the Snippets Section by Erez
in thread Shut down the Snippets Section by jdporter

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.