Oh, who cares? No, that was rhetorical. They sound rather snippetish to me and the few I looked at don't look utterly unsnippetish. Yes, it'd be better to get rid of the distinction between "code" and "snippets". Creating sections that were too specialized was a mistake. We should have only one "here's code" section (and Cool Uses For Perl is probably the best format as the categorization features never worked well -- one day somebody may get some kind of tagging system working which makes more sense than trying to create categories). We should also merge poems and obfu into a single "fun" section. No, I wouldn't suggest holding your breath. :)

- tye        

In reply to Re: moving nodes from Snippets to Code (why?) by tye
in thread moving nodes from Snippets to Code by zentara

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.