"Way better than Java's. Way better than any documentation that I saw before ..."
It is more close to reality and fair to put it in this way: If we are talking about the document for each module, Java's is better than Perl's in most cases; but Java lacks the kind of documentation like perltoot, perlfaq etc., which put things together for you.
When you read Java document, you may get a very clear picture of what the module is doing but it does not usually contain information as how to use the module in an application with other related modules.
However, the other side of the life is that, there are big knowledge bases for both languages on internet and in book stores beyond pure documentation.
-
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.
|
