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
--Mark Hahn, <hahn@neurocog.lrdc.pitt.edu>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Reorganize rather than re-write (Score:3, Interesting)
It's useful information, but you're right, it doesn't belong in an introductory document. It might be more appropriate in perltrap, for instance.
In the same vein, I keep thinking there's a lot of documentation, but it's hard to skim because it's all one flat structure. (How many people remember what's in perldsc?) It would be nice to have it arranged into groups, maybe something like:
- Introductory and Core: perlsyn, perlfunc, perldata, perlbook, perlboot, etc.
- Internals: perlguts, perlhack, perldebguts, etc.
- FAQs: perlfaq1 thru N
- System-specific: perlaix, perlhpux, and all the rest.
- Tutorials: perldsc, perltoot, perltooc, perlretut, etc.
I could go on, but you get the idea. It would be even better if you could cross-reference, since some things easily fit in more than one category.I'd gladly make and maintain such a list, but I don't know how to get it out there. Give it to you? ;-)
Reply to This
Re:Reorganize rather than re-write (Score:3, Insightful)
5.8.0's perl(1) [perldoc.com] already does that breakdown, pretty much exactly along those lines.
As an aside, the formatting on perldoc.com is quite nice.