cvsuser 05/12/30 16:58:24
Modified: bin perlfaq_toc.pl
* Updated the template for the perlfaq intro. I wanted a nicer tone and
Revision Changes Path
1.4 +63 -59 perlfaq/bin/perlfaq_toc.pl
RCS file: /cvs/public/perlfaq/bin/perlfaq_toc.pl,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- perlfaq_toc.pl 10 Nov 2005 00:37:15 -0000 1.3
+++ perlfaq_toc.pl 31 Dec 2005 00:58:24 -0000 1.4
@@ -47,69 +47,76 @@
-The perlfaq is divided into several documents based on topics. A table
-of contents is at the end of this document.
+The perlfaq comprises several documents that answer the most commonly
+asked questions about Perl and Perl programming. It's divided by topic
+into nine major sections outlined in this document.
=head2 Where to get the perlfaq
-Extracts of the perlfaq are posted regularly to
-comp.lang.perl.misc. It is available on many web sites:
-http://www.perldoc.com/ and http://faq.perl.org/
+The perlfaq comes with the standard Perl distribution, so if you have Perl
+you should have the perlfaq. You should also have the C<perldoc> tool
+that let's you read the perlfaq:
+ $ perldoc perlfaq
+Besides your local system, you can find the perlfaq on the web,
+including at http://perldoc.perl.org/ .
+The perlfaq is an evolving document and you can read the latest version
+at http://faq.perl.org/ . The perlfaq-workers periodically post extracts
+of the latest perlfaq to comp.lang.perl.misc.
+You can view the source tree at http://cvs.perl.org/cvsweb/perlfaq/
+(which is outside of the main Perl source tree). The CVS repository
+notes all changes to the FAQ and holds the latest version of the working
+documents and may vary significantly from the version distributed with
+the latest version of Perl. Check the repository before sending your
=head2 How to contribute to the perlfaq
-You may mail corrections, additions, and suggestions to
-firstname.lastname@example.org . This alias should not be used to
-I<ask> FAQs. It's for fixing the current FAQ. Send
-questions to the comp.lang.perl.misc newsgroup. You can
-view the source tree at http://cvs.perl.org/cvsweb/perlfaq/
-(which is outside of the main Perl source tree). The CVS
-repository notes all changes to the FAQ.
+You can mail corrections, additions, and suggestions to
+email@example.com . The perlfaq volunteers use this address to
+coordinate their efforts and track the perlfaq development. They
+appreciate your contributions to the FAQ but do not have time to provide
+individual help, so don't use this address to ask FAQs.
+The perlfaq server posts extracts of the perlfaq to that newsgroup every
+6 hours (or so), and the community of volunteers reviews and updates the
+answers. If you'd like to help review and update the answers, check out
=head2 What will happen if you mail your Perl programming problems to the authors
-Your questions will probably go unread, unless they're
-suggestions of new questions to add to the FAQ, in which
-case they should have gone to the firstname.lastname@example.org
-You should have read section 2 of this faq. There you would
-have learned that comp.lang.perl.misc is the appropriate
-place to go for free advice. If your question is really
-important and you require a prompt and correct answer, you
-should hire a consultant.
-The original perlfaq was written by Tom Christiansen, then expanded
-by collaboration between Tom and Nathan Torkington. The current
-document is maintained by the perlfaq-workers (email@example.com).
-Several people have contributed answers, corrections, and comments.
-=head1 Author and Copyright Information
-Copyright (c) 1997-2005 Tom Christiansen, Nathan Torkington, and
-other contributors noted in the answers.
-All rights reserved.
-=head2 Bundled Distributions
-This documentation is free; you can redistribute it and/or modify it
-under the same terms as Perl itself.
-Irrespective of its distribution, all code examples in these files
-are hereby placed into the public domain. You are permitted and
-encouraged to use this code in your own programs for fun
-or for profit as you see fit. A simple comment in the code giving
-credit would be courteous but is not required.
-This information is offered in good faith and in the hope that it may
-be of use, but is not guaranteed to be correct, up to date, or suitable
-for any particular purpose whatsoever. The authors accept no liability
-in respect of this information or its use.
+The perlfaq-workers like to keep all traffic on the firstname.lastname@example.org
+so that everyone can see the work being done (and the work that needs to
+be done). The mailing list serves as an official record. If you email the
+authors or maintainers directly, you'll probably get a reply asking you to
+post to the mailing list. If you don't get a reply, it probably means that
+the person never saw the message or didn't have time to deal with it. Posting
+to the list allows the volunteers with time to deal with it when others are
+If you have a question that isn't in the FAQ and you would like help with it,
+try the resources in L<perlfaq2>.
+Tom Christiansen wrote the original perlfaq then expanded it with the
+help of Nat Torkington. The perlfaq-workers maintain current document
+and the dezinens of comp.lang.perl.misc regularly review and update the
+FAQ. Several people have contributed answers, corrections, and comments,
+and the perlfaq notes those contributions wherever appropriate.
+=head1 AUTHOR AND COPYRIGHT
+Tom Christainsen wrote the original version of this document.
+brian d foy C<< <email@example.com> >> wrote this version. See the
+individual perlfaq documents for additional copyright information.
+This document is available under the same terms as Perl itself. Code
+examples in all the perlfaq documents are in the public domain. Use
+them as you see fit (and at your own risk with no warranty from anyone).
=head1 Table of Contents
@@ -135,13 +142,10 @@
=item perlfaq9 - Networking
=head1 The Questions
foreach my $file ( @files )