From: Iain Truskett Date: Mon, 8 Jul 2002 16:50:55 +0000 (+1000) Subject: [DOC PATCH] perlfaq2.pod, perlmodstyle.pod X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=ccbb3b41ea16d89eb30c068060208b3313b4a11f;p=p5sagit%2Fp5-mst-13.2.git [DOC PATCH] perlfaq2.pod, perlmodstyle.pod Message-ID: <20020708065055.GC14168@eh.org> p4raw-id: //depot/perl@17418 --- diff --git a/pod/perlfaq2.pod b/pod/perlfaq2.pod index 7fbed98..2f49681 100644 --- a/pod/perlfaq2.pod +++ b/pod/perlfaq2.pod @@ -183,9 +183,10 @@ following groups: comp.infosystems.www.authoring.cgi Writing CGI scripts for the Web. -There is also a Usenet gateway to Perl mailing lists sponsored by perl.org at -nntp://nntp.perl.org , or a web interface to the same lists at -http://nntp.perl.org/group/ . Other groups are listed at +There is also a Usenet gateway to Perl mailing lists sponsored by perl.org at +nntp://nntp.perl.org , a web interface to the same lists at +http://nntp.perl.org/group/ and these lists are also available under the +C hierarchy at http://groups.google.com . Other groups are listed at http://lists.perl.org/ . =head2 Where should I post source code? @@ -368,7 +369,7 @@ Recommended books on (or mostly on) Perl follow. =head2 Perl in Magazines -The first and only periodical devoted to All Things Perl, +The first (and for a long time, only) periodical devoted to All Things Perl, I contains tutorials, demonstrations, case studies, announcements, contests, and much more. I has columns on web development, databases, Win32 Perl, graphical programming, regular @@ -419,6 +420,8 @@ Most of the major modules (Tk, CGI, libwww-perl) have their own mailing lists. Consult the documentation that came with the module for subscription information. +A comprehensive list of Perl related mailing lists can be found at: + http://lists.cpan.org/ =head2 Archives of comp.lang.perl.misc diff --git a/pod/perlmodstyle.pod b/pod/perlmodstyle.pod index 558edcf..9431691 100644 --- a/pod/perlmodstyle.pod +++ b/pod/perlmodstyle.pod @@ -177,6 +177,9 @@ You may not even need to write the module. Check whether it's already been done in Perl, and avoid re-inventing the wheel unless you have a good reason. +Good places to look for pre-existing modules include +http://search.cpan.org/ and asking on modules@perl.org + If an existing module B does what you want, consider writing a patch, writing a subclass, or otherwise extending the existing module rather than rewriting it.