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
--Larry Wall in perl.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Re: (Score:1)
Well, I‘m pretty serious about it.
search.cpan.orgis my main browsing tool, and if that shows me “Perl extension for blah blah blah” I’m unlikely to even click through. And if I do so and find a nearly untouched POD template, well, I have to be desperate before I’ll consider using the module and delve into the source.I may be a snob, but I believe that someone who can’t or won’t write at least minimally useful documentation either doesn’t care beyond “it works, somehow,” or isn’t even capable of writing decent documentation because they aren’t capable of designing a coherent interface independent of its implementation. Neither are good signs… So far, I’ve not had much reason to doubt these assertions; whenever I looked at source for a “Perl extension for blah blah blah,” it generally turned out to be really trivial (which likely means “unfinished”) or really shoddy code.
If there’s an exception to these rules, it will only serve to confirm them.
Without at least a modicum of documentation, code may as well not exist.
Reply to This