In perl.git, the branch maint-5.10 has been updated <http://perl5.git.perl.org/perl.git/commitdiff/8e68ea1a6a9fa92b41c2a9776370ac378153d1b1?hp=0a0ac76f85c2afdb382436b9fc46854b2fa15df7>
- Log ----------------------------------------------------------------- commit 8e68ea1a6a9fa92b41c2a9776370ac378153d1b1 Author: Paul Fenwick <[email protected]> Date: Fri Jun 26 02:39:47 2009 +1000 feature and lib are pragmas and have moved to the pragma section of the perldelta M pod/perl5101delta.pod commit 3ec5c0a45fc991166c368688e462c478673eb3fd Author: Frank Wiegand <[email protected]> Date: Fri Jun 26 13:18:56 2009 +0200 pod/perlfilter.pod: two POD typos Hi, while reading perlfilter.pod I found two typos, patch is attached. Thanks, Frank From ab8b547c7f60f1793dfd111d0d758853a07fbc95 Mon Sep 17 00:00:00 2001 From: Frank Wiegand <[email protected]> Date: Fri, 26 Jun 2009 13:15:24 +0200 Subject: [PATCH] perlfilter.pod: fix two typos Signed-off-by: H.Merijn Brand <[email protected]> (cherry picked from commit d00c6acb5649055ca8b949a4bc7e614ee7cf8323) M pod/perlfilter.pod commit 1ef5df36ac161d4600025b9ada4529ebd5e6aa73 Author: Frank Wiegand <[email protected]> Date: Thu Jun 25 10:21:46 2009 +0200 document the maximum length of barewords (amended by rgs to be in line with perldiag) (cherry picked from commit 05b4f1ece255de95efcc5a4c74e28b5d04f54401) M pod/perldata.pod ----------------------------------------------------------------------- Summary of changes: pod/perl5101delta.pod | 29 +++++++++++++---------------- pod/perldata.pod | 7 +++++-- pod/perlfilter.pod | 4 ++-- 3 files changed, 20 insertions(+), 20 deletions(-) diff --git a/pod/perl5101delta.pod b/pod/perl5101delta.pod index b5e5dd0..8626f4c 100644 --- a/pod/perl5101delta.pod +++ b/pod/perl5101delta.pod @@ -245,6 +245,19 @@ have been recognised; for example, C<"\N{LATIN CAPITAL LETTER GHA}">. upgraded from version 1.13 to 1.17 +=item C<feature> + +The meaning of the C<:5.10> and C<:5.10.X> feature bundles has +changed slightly. The last component, if any (ie C<X>) is simply ignored. +This is predicated on the assumption that new features will not, in +general, be added to maintenance releases. So C<:5.10> and C<:5.10.X> +have identical effect. This is a change to the behaviour documented for +5.10.0. + +=item C<lib> + +upgraded from version 0.5565 to 0.62 + =item C<overloading> See L</"The C<overloading> pragma"> above. @@ -253,7 +266,6 @@ See L</"The C<overloading> pragma"> above. upgraded from version 0.74 to 0.76 - =back =head2 Updated Modules @@ -262,21 +274,6 @@ upgraded from version 0.74 to 0.76 =item * -C<feature> - -The meaning of the C<:5.10> and C<:5.10.X> feature bundles has -changed slightly. The last component, if any (ie C<X>) is simply ignored. -This is predicated on the assumption that new features will not, in -general, be added to maintenance releases. So C<:5.10> and C<:5.10.X> -have identical effect. This is a change to the behaviour documented for -5.10.0. - -=item * - -C<lib> upgraded from version 0.5565 to 0.62 - -=item * - C<Archive::Extract> upgraded from version 0.24 to 0.32 =item * diff --git a/pod/perldata.pod b/pod/perldata.pod index b263609..8f0feb7 100644 --- a/pod/perldata.pod +++ b/pod/perldata.pod @@ -442,8 +442,11 @@ be treated as if it were a quoted string. These are known as "barewords". As with filehandles and labels, a bareword that consists entirely of lowercase letters risks conflict with future reserved words, and if you use the C<use warnings> pragma or the B<-w> switch, -Perl will warn you about any -such words. Some people may wish to outlaw barewords entirely. If you +Perl will warn you about any such words. Perl limits barewords (like +identifiers) to about 250 characters. Future versions of Perl are likely +to eliminate these arbitrary limitations. + +Some people may wish to outlaw barewords entirely. If you say use strict 'subs'; diff --git a/pod/perlfilter.pod b/pod/perlfilter.pod index d43028c..79f7a5d 100644 --- a/pod/perlfilter.pod +++ b/pod/perlfilter.pod @@ -205,7 +205,7 @@ source filter (see Decryption Filters, below). All decryption filters work on the principle of "security through obscurity." Regardless of how well you write a decryption filter and -how strong your encryption algorithm, anyone determined enough can +how strong your encryption algorithm is, anyone determined enough can retrieve the original source code. The reason is quite simple - once the decryption filter has decrypted the source back to its original form, fragments of it will be stored in the computer's memory as Perl @@ -227,7 +227,7 @@ module. An alternative to writing the filter in C is to create a separate executable in the language of your choice. The separate executable reads from standard input, does whatever processing is necessary, and -writes the filtered data to standard output. C<Filter:cpp> is an +writes the filtered data to standard output. C<Filter::cpp> is an example of a source filter implemented as a separate executable - the executable is the C preprocessor bundled with your C compiler. -- Perl5 Master Repository
