Slash Boxes
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I for one would like to see a separate pod file dealing specifically with sed, awk, etc. Possibly either detailing the differences between perl and these, or detailing how to convert bits of sed and awk into pure perl..

    Yes it's in there now, but moving them off to their own section would allow a little more expounding on these topics, and may remove some of the clutter from those pods that contain these references now.

    If this makes no sense, it's because I'm still on my first cup of coffee.. ;-)
  • by VSarkiss (704) on 2003.05.14 10:20 (#20113) Journal

    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? ;-)