Keep telling yourself that a series of blogs, example mathematical puzzles, and Larry promising that this year for sure he'll write a book (he's been saying that since 2005) are acceptable forms of documentation that people like me want. (They aren't.)
You suggested that the only documentation was "a pile of specification tests hyperlinked to synopses under constant churn". That comment ignored the doc.perl6.org project and the above follow up does so again.
You do Rosettacode a great disservice, and mislead monks, when you suggest that it's just mathematical puzzles. The 679 programming tasks cover any programming task contributors have chosen to contribute. It only takes a quick glance to see that most of them are things like basic and advanced programming techniques, file, string, Unicode, and date manipulation, and so on. (There are Perl 6 solutions for over 600 of them.)
(Edit: removed comment about Larry, and simplified initial paragraph.)
-
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.
|