But - much of perl's power lies in the great array of modules that are constantly being developed. The documentation of these
varies from wonderful to woeful.
True, but I am unhappy with the standard documentation, not the
documentation for other modules. There's no way to force authors of modules
to write documentation (except for maybe not putting them into CPAN unless
they are accompanied by documentation, but I don't think this would be a good thing), and
I'm not too worried about that, but I think that the basic core of the language should
be well documented.
-
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.
|