Front page | perl.perl5.porters |
Postings from May 2012
[PATCH] [POD] Minor improvements to perl5160delta POD
From:
Toby Wintermute
Date:
May 3, 2012 01:49
Subject:
[PATCH] [POD] Minor improvements to perl5160delta POD
Message ID:
CABEgq95mAaO4O=O0LL=rJX+qfhVgn5XVfFS7jnaoGkQf_PNJ=g@mail.gmail.com
Tidies up a few spelling and grammar issues. Improves language
usage slightly.
---
Porting/perl5160delta.pod | 37 ++++++++++++++-----------------------
1 file changed, 14 insertions(+), 23 deletions(-)
diff --git a/Porting/perl5160delta.pod b/Porting/perl5160delta.pod
index 5f3be51..9e94569 100644
--- a/Porting/perl5160delta.pod
+++ b/Porting/perl5160delta.pod
@@ -84,7 +84,7 @@ See L<feature> for more detail.
=head3 C<substr> lvalue revamp
-=for comment Does this belong here, or under Incomptable Changes?
+=for comment Does this belong here, or under Incompatible Changes?
When C<substr> is called in lvalue or potential lvalue context with two
or three arguments, a special lvalue scalar is returned that modifies
@@ -284,7 +284,7 @@ letter. That has been extended to all Unicode
identifier characters.
One-character non-ASCII non-punctuation variables (like C<$é>) are now
subject to "Used only once" warnings. They used to be exempt, as they
-was treated as punctuation variables.
+were treated as punctuation variables.
Also, single-character Unicode punctuation variables (like C<$‰>) are now
supported [perl #69032].
@@ -699,7 +699,7 @@ L<perlunicode/Hacking Perl to work on earlier
Unicode versions (for very serious
=head2 Borland compiler
All support for the Borland compiler has been dropped. The code had not
-worked for a long time anyway.
+been working for a long time.
=head2 Certain deprecated Unicode properties are no longer supported by default
@@ -834,22 +834,13 @@ Improved performance for Unicode properties in
regular expressions
=for comment Can this be compacted some? -- rjbs, 2012-02-20
Matching a code point against a Unicode property is now done via a
-binary search instead of linear. This means for example that the worst
-case for a 1000 item property is 10 probes instead of 1000. This
-inefficiency has been compensated for in the past by permanently storing
-in a hash the results of a given probe plus the results for the adjacent
-64 code points, under the theory that near-by code points are likely to
-be searched for. A separate hash was used for each mention of a Unicode
-property in each regular expression. Thus, C<qr/\p{foo}abc\p{foo}/>
-would generate two hashes. Any probes in one instance would be unknown
-to the other, and the hashes could expand separately to be quite large
-if the regular expression were used on many different widely-separated
-code points. This can lead to running out of memory in extreme cases.
-Now, however, there is just one hash shared by all instances of a given
-property. This means that if C<\p{foo}> is matched against "A" in one
-regular expression in a thread, the result will be known immediately to
-all regular expressions, and the relentless march of using up memory is
-slowed considerably.
+binary search instead of linear. In the worst case for a 1000-item
+property, the number of probes required has decreased from 1000 to 10.
+
+Also, there is now a unified hash cache for property look-ups. This
+means that if C<\p{foo}> is matched against "A" in one regular expression
+in a thread, the result will be known immediately to all regular
+expressions.
=item *
@@ -2820,9 +2811,9 @@ fixed [perl #95964].
The combination of the regular expression modifiers C</aa> and the C<\b>
and C<\B> escape sequences did not work properly on UTF-8 encoded
strings. All non-ASCII characters under C</aa> should be treated as
-non-word characters, but what was happening was that Unicode rules were
-used to determine wordness/non-wordness for non-ASCII characters. This
-is now fixed [perl #95968].
+non-word characters, however Unicode rules were being used to determine
+wordness/non-wordness for non-ASCII characters. This is now fixed
+[perl #95968].
=item *
@@ -3678,7 +3669,7 @@ on what changed.
The F<INSTALL> file for how to build Perl.
-The F<README> file for general stuff.
+The F<README> file for general information.
The F<Artistic> and F<Copying> files for copyright information.
--
1.7.10
-
[PATCH] [POD] Minor improvements to perl5160delta POD
by Toby Wintermute