| Newsgroups |
perl.cvs.perlfaq |
| Message-ID |
<[email protected]> |
cvsuser 02/02/21 06:49:15
Modified: . perlfaq1.pod
Log:
* strengthen statement that 'Perl' is not an ancronym. it's less namby-pamby now :)
Revision Changes Path
1.7 +2 -2 perlfaq/perlfaq1.pod
Index: perlfaq1.pod
===================================================================
RCS file: /cvs/public/perlfaq/perlfaq1.pod,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -w -r1.6 -r1.7
--- perlfaq1.pod 31 Jan 2002 01:46:23 -0000 1.6
+++ perlfaq1.pod 21 Feb 2002 14:49:15 -0000 1.7
@@ -1,6 +1,6 @@
=head1 NAME
-perlfaq1 - General Questions About Perl ($Revision: 1.6 $, $Date: 2002/01/31 01:46:23 $)
+perlfaq1 - General Questions About Perl ($Revision: 1.7 $, $Date: 2002/02/21 14:49:15 $)
=head1 DESCRIPTION
@@ -216,7 +216,7 @@
can parse Perl." You may or may not choose to follow this usage. For
example, parallelism means "awk and perl" and "Python and Perl" look
OK, while "awk and Perl" and "Python and perl" do not. But never
-write "PERL", because perl isn't really an acronym, apocryphal
+write "PERL", because perl is not an acronym, apocryphal
folklore and post-facto expansions notwithstanding.
=head2 Is it a Perl program or a Perl script?