Indent your text (even by one column), and it will be rendered verbatim

Yes - but then if you copy the 'perldoc crap' output (without removing the leading whitespace) and save it as a typemap, you get all sorts of weird warnings when you run a 'make' process that uses that typemap: 
Warning: File './typemap' Line 3 ' INPUT' TYPEMAP entry needs 2 or 3 c
+olumns
Warning: File './typemap' Line 4 ' SOLDIER' TYPEMAP entry needs 2 or 3
+ columns
Warning: File './typemap' Line 7 ' OUTPUT' TYPEMAP entry needs 2 or 3 
+columns
Warning: File './typemap' Line 8 ' SOLDIER' TYPEMAP entry needs 2 or 3
+ columns
Warning: File './typemap' Line 12 '        SvREADONLY_on(obj);' TYPEMA
+P entry needs 2 or 3 columns
Warning: File './typemap' Line 13 '        $arg;' TYPEMAP entry needs 
+2 or 3 columns
Warning: File 'typemap' Line 3 ' INPUT' TYPEMAP entry needs 2 or 3 col
+umns
Warning: File 'typemap' Line 4 ' SOLDIER' TYPEMAP entry needs 2 or 3 c
+olumns
Warning: File 'typemap' Line 7 ' OUTPUT' TYPEMAP entry needs 2 or 3 co
+lumns
Warning: File 'typemap' Line 8 ' SOLDIER' TYPEMAP entry needs 2 or 3 c
+olumns
Warning: File 'typemap' Line 12 '        SvREADONLY_on(obj);' TYPEMAP 
+entry needs 2 or 3 columns
Warning: File 'typemap' Line 13 '        $arg;' TYPEMAP entry needs 2 
+or 3 columns
Warning: File 'typemap' Line 3 ' INPUT' TYPEMAP entry needs 2 or 3 col
+umns
Warning: File 'typemap' Line 4 ' SOLDIER' TYPEMAP entry needs 2 or 3 c
+olumns
Warning: File 'typemap' Line 7 ' OUTPUT' TYPEMAP entry needs 2 or 3 co
+lumns
Warning: File 'typemap' Line 8 ' SOLDIER' TYPEMAP entry needs 2 or 3 c
+olumns
Warning: File 'typemap' Line 12 '        SvREADONLY_on(obj);' TYPEMAP 
+entry needs 2 or 3 columns
Warning: File 'typemap' Line 13 '        $arg;' TYPEMAP entry needs 2 
+or 3 columns

[download]
The idea is that 'perldoc crap' should output something that can be copy'n'pasted to a 'typemap' and run trouble-free (without having to bother about removing leading whitespace).

Thanks Sidhekin, moritz.

Cheers,
Rob
Update: Probably a silly objection. The 'perldoc' output always displays leading whitespace at the beginning of every line (afaict). That being the case, all I'm really quibbling about is the *amount* of preceding whitespace ... pointless, really :-)

In reply to Re^2: POD not rendering as I intend by syphilis
in thread POD not rendering as I intend by syphilis

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.