I was then shocked to find that the person had no experience
with either the Unix perl man pages, perldoc, or Shuck on the Macintosh. It was
surprising to me that his professor had apparently not bothered to mention these valuable
resources. Oh sure they had purchased, through their campus store, the O'Reilly book
Learning Perl which was a great text to be using. But the prof had not yet mentioned
the wealth of online docs, how its organized, etc.
Why is it that Perl books geared towards beginners, notably Learning Perl do not discuss pod and where to find the pod pages? As an author of such a book couldn't you provide your readership with a little more shelf life or longevity if you mention things like "be sure to check the online documentation that came with your Perl installation. Here is how to do just that..." or is it the case that designed absolescence in the publishing world is to be considered a good thing?
-
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.
|
