As we all know, this site holds old 5.0 perldocs. Perldocs on this site are handier than linking directly to perldoc with the perldoc:// tag, because that is a lot of typing.

After some ranting about this, crazyinsomniac told me that there has been discussion and the decision was that this site would never get a documentation update. That's a shame.

If it is not going to be updated, it needs to be removed. We are now giving people bad advice by refering them to old documentation. That is not a nice thing to do.

I suggest that we remove all documentation and link to http://perldoc.com/ instead. While you're at it, add documentation for all releases. I'm thinking of something like this:

perlreftut

Perl documentation is no longer maintained on this site. Please refer to one of the documents below:

It shouldn't be hard to implement.

We're Perl Hackers. We can parse html, we know how to link. There is, in my view, no excuse to not do this. I have no idea how Everything works, but I'm sure the possibility of updating nodes automatically does exist, somehow.

crazyinsomniac said I had to have convincing code to support my plead. I don't know if the following is convincing, but it should ease the automatic node updates: 

use HTML::TreeBuilder;
use LWP::Simple;
use Data::Dumper;

print Dumper( do {
    my %pod;

    push @{ $pod{ substr $_->[1], 4, -5 } }, "http://perldoc.com/perl$
+_->[0]/$_->[1]"
        for map {
            my $v = $_;
            map {
                [
                    $v,
                    $_->attr('href')
                ],
            } HTML::TreeBuilder
                -> new
                -> parse( get "http://perldoc.com/perl$v/pod.html" )
                -> look_down(
                    _tag => 'a',
                    sub { shift->attr('href') =~ /^pod/ }
                )
        } reverse sort map {
            $_->attr('value')
        } HTML::TreeBuilder
           -> new
           -> parse( get 'http://perldoc.com/' )
           -> look_down( name => 'version' )
           -> content_list;
    \%pod;
} );

[download]

Please make this site a bit more useable. 

- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.

In reply to I want site documentation updates and I want them now. by Juerd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.