Stories
Slash Boxes
Comments
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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by cwest (1514) on 2003.04.18 9:17 (#19267) Homepage Journal
    We are in the process of ramping ourselves up. We're going to be doing edtorial work for the Perl FAQ, and one of the goals of the project originally was to do editorial work for the core Perl documentation as well. We are the folks you're looking for.
    --
    Casey West
  • I'd like to point out as well that the perlfaq*.pod manpages have their own CVS repository and mailing list(s) : perlfaq-workers [develooper.com] and perl-documentation [develooper.com]. I still don't get the difference between the two, even if I'm officially in charge of integrating the FAQ changes into Perforce.
  • bike shed (Score:2, Interesting)

    I think the "bike shed" metaphor is a good one in this case:

    you can go in to the board of directors and get approval for building a multi-million or even billion dollar atomic power plant, but if you want to build a bike shed you will be tangled up in endless discussions.

    From A bike shed (any colour will do) [freebsd.org]

    The docs are a good reference but probably not the best thing to learn Perl from. That's not necessarily a bad thing, nor does it make Perl unfriendly to "newbies". There's such a wealth of decent