There are some documents that I think should be made available as perldocs. Coping with Scoping could be named perlscopetut and Suffering from Buffering could be named perlbuffertut.
I believe the reason these are not mentioned in the docs is that they are not specific to perl. For example, lexical scoping is not native to perl and the perl docs will generally assume that you have a programming background so there is no need for this to be covered given the assumptions that are made. Most of the perl docs cover areas that are native to perl e.g perlreftut and while references are found in other languages the way perl deals with them is very much different to, say, C.
The most important tutorial can not be found in the standard distribution. perltut it should be called
I have to say I wholeheartedly agree. But I think this is more down to the distribution of perl than the core as this would be making the assumption that the user of perl also has an understanding of *nix man pages. Perhaps a better option would be if there was a standard perl tutorial that would be bundled with all versions of perl whether it be in the form of man pages or an HTML document.
_________
broquaint
-
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.
|
