Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I personally disagree with the idea of Yet Another Section To Place Code. I find it daunting enough to figure out whether a bit of code I'd like to share should go in Code, Craft, CUFP, or Snippets; the difference seems to mostly be an issue of size vs. general usefulness vs. "Wow, you couldn't do that in most languages". I don't think that a similar split between obfuscation and JAPHs makes any sense... it's not as though the Obfuscation area gets more than a couple posts a day anyways. If you're dissatisfied with the recent posts in the Obfuscation section, just ignore them... save your votes up so that the real Obfuscations can rack up the ++. ;)

In reply to Re: Separated JAPH/Obfuscation sections by Falkkin
in thread Separated JAPH/Obfuscation sections by BooK

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.