It requires a fair amount of work to write. Which reminds me, I'd better finish writing the latest summary.
To be honest, I'm not really sure that the summary is really what Flame wants, in fact, I'm not even sure that what zie wants currently exists. The problem is that stuff changes all the time, and keeping a document up to date with what has changed would be Hard Work (and if it's to be definitive it'd need a fair amount of time from Larry & Co to proofread it and make sure it's accurate, and really we want them working on Apocalypses.)
However, the perl6-documentation people are plugging away at producing detailed documentation which covers the 'nailed down' behaviour. So far they've produced a document on numeric literals and are working on the string literals doc at the moment.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.