You cite your argument for the creation of the new macros is:

so that we can easily type solutions to puzzles without bothering others

However, I would consider this a fallacy. I grant I only recently became a scribe, nevertheless I think that such tags would not be conducive to the ready dissemination of perl knowledge. Therefore, perhaps the pertinent question is:

How can we optimize the dissemination of perl knowledge?

This is a complex issue as perl knowledge manifests itself in a variety of forms; however the objective remains the same: to impart (or further) an understanding of perl. I do not purport to know the best didactic method, however I do not think abstractions would be beneficial.

With respect to the notion of a puzzle/quiz thread specifically, why not change the organization so as to better elucidate the solution as opposed to abstracting it within a "spoiler" tag. Furthermore, these threads and their solutions are akin to Categorized Questions and Answers and Snippets Section (and possibly Code Catacombs and portions of Tutorials).

While I enjoy perl puzzles, and often code a solution to a Seekers of Perl Wisdom node as a practical exercise, I think that there are better ways to disseminate perl knowledge than with the inclusion of "spoiler tags."

In reply to Re: black tags by eibwen
in thread black tags by cog

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.