Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
a very sore point ... my boss tried to look at Perl 6 ... documentation ... assumed that he was already fluent in Perl 5

P6 isn't ready for general consumption, and documentation is one of many reasons for that. That said, fwiw, I don't think p6doc ( assumes knowledge of P5 (beyond its existence). - it feels to me like some automatically generated documentation that is not intended for human consumption. Maybe it is a good reference if you're looking for a concise description of how an operator works

Update: The CSS etc for has been improved to make it less ugly; perhaps it now looks intended for human consumption.

p6doc is intended to be the P6 equivalent of P5's perldoc. "I want p6doc and to become the No. 1 resource to consult when you want to know something about a Perl 6 type or routine (be it method, sub or operator)." -- Moritz, in the readme of the p6doc project.

it surely can't be intended as the starting point for getting in touch with Perl 6.


Imo the smart starting point is to join the IRC channel #perl6 on freenode, introduce yourself, and ask for pointers. If you can't or won't join #perl6, see my P6-documentation-for-contributors PerlMonks post for some alternate starting points.

In reply to Re^3: Basic Literacy for P6 Advocates by raiph
in thread A $dayjob Perl 6 program that runs 40x faster on the JVM than on Parrot by raiph

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.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others musing on the Monastery: (7)
As of 2023-11-28 10:45 GMT
Find Nodes?
    Voting Booth?

    No recent polls found