I am still waiting for your explanation of the escaping syntax so that comments that include Perl arrays don't accidentally turn into Texinfo directives.
Oh. I don't think I understand what you're talking about. In that Texinfo example I was using in the OP, I figured: 
# This is a regular comment. Don't start one of 
# these with a '#@'. 
#@ This could be a Pod comment. 
#@ Make sure they always start with a '#@'.

[download]

chromatic isn't talking about this. How do you suggest to escape these so that texinfo parses them correctly?

#@ @node do_something
#@ 
#@ @array has to be defined.
#@
#@ You'd use this @emph{awesome} function..
#@ 
#@ Also note that hash slices like @hash{oops} are needed.
#@

[download]

In reply to Re^7: Perl 6 Pod -- reinventing the wheel? by Leviathan
in thread Perl6 Pod -- reinventing the wheel? by j3

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.