It means helping people in #perlhelp need to un-learn telling people to "perldoc perlreftut".
So? Big deal.
Point them to perlref, perldsc, and/or perllol. Or, as diotalevi said, point them to perldoc.com. Or give them the ten minute tutorial (with examples) that it usually takes to explain references adequately on IRC. What's the point of "helping" people if all you do is cite perldoc perl all the time.
In any case, it is far better for us to have to unlearn perldoc perlreftut than for Debian to violate the overly restrictive copyright on a single document in the Perl distribution. Better to remove the offending document than to remove perl itself. Afterall, perlreftut is useless when it comes to running scripts.
-sauoq
"My two cents aren't worth a dime.";
-
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.
|