NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Yes! (Score:2)
I'm sure it could be repaired, but I don't think it's worth the effort. As it is it's worse than useless and should be discarded as soon as possible.
-sam
PS: And don't get me started about DSLIP codes!
Re:Yes! (Score:1)
I agree with this part...
should be discarded as soon as possible
...but I totally disagree with this one! I think if we had an updated module list it would be to the benefit of our community!
Re:Yes! (Score:1)
Not only does it do no good, but it does harm. One of the ways it does harm is by making us think that we have something reasonable in place, so we can "fix this later." Let's get rid of this system, which is not reasonable.
If it then becomes apparent that we need a new system, we will feel more compelled to produce it. I imagine, though, that this need will
rjbs
Re:Yes! (Score:1)
I strongly believe that a long module list of that kind is something good for the community, as long as it is updated.
Many of you may say you don't need it, as you use search.cpan.org instead... I don't use it either (in part because the list is outdated), but I know such a list would be a good thing to have.
You can use search.cpan.org to search for specific modules, but others can use the long list to look at all those modules and get new ideas from them.
It's not kind of a "let's see if I have this" list, it's more kind of a "let's see what I have" list.
Reply to This
Parent