summaryrefslogtreecommitdiff
path: root/regen
diff options
context:
space:
mode:
authorKarl Williamson <public@khwilliamson.com>2014-02-20 11:10:39 -0700
committerKarl Williamson <public@khwilliamson.com>2014-02-20 11:47:05 -0700
commit850b7ec98b08ce3e7330267f4331f3006ea95551 (patch)
treea7b7689dca59b74f5243cb8757db46fc43ef1c20 /regen
parentb9f2b68390014b991c227e8c56d3e813584245b9 (diff)
downloadperl-850b7ec98b08ce3e7330267f4331f3006ea95551.tar.gz
Change 'semantics' to 'rules'
The term 'semantics' in documentation when applied to character sets is changed to 'rules' as being a shorter less-jargony synonym in this case. This was discussed several releases ago, but I didn't get around to it.
Diffstat (limited to 'regen')
-rwxr-xr-xregen/feature.pl6
-rw-r--r--regen/mk_PL_charclass.pl2
2 files changed, 4 insertions, 4 deletions
diff --git a/regen/feature.pl b/regen/feature.pl
index a46ebbcc91..fccfc2da16 100755
--- a/regen/feature.pl
+++ b/regen/feature.pl
@@ -361,7 +361,7 @@ read_only_bottom_close_and_rename($h);
__END__
package feature;
-our $VERSION = '1.35';
+our $VERSION = '1.36';
FEATURES
@@ -456,7 +456,7 @@ This feature is available starting with Perl 5.10.
=head2 The 'unicode_strings' feature
-C<use feature 'unicode_strings'> tells the compiler to use Unicode semantics
+C<use feature 'unicode_strings'> tells the compiler to use Unicode rules
in all string operations executed within its scope (unless they are also
within the scope of either C<use locale> or C<use bytes>). The same applies
to all regular expressions compiled within the scope, even if executed outside
@@ -464,7 +464,7 @@ it. It does not change the internal representation of strings, but only how
they are interpreted.
C<no feature 'unicode_strings'> tells the compiler to use the traditional
-Perl semantics wherein the native character set semantics is used unless it is
+Perl rules wherein the native character set rules is used unless it is
clear to Perl that Unicode is desired. This can lead to some surprises
when the behavior suddenly changes. (See
L<perlunicode/The "Unicode Bug"> for details.) For this reason, if you are
diff --git a/regen/mk_PL_charclass.pl b/regen/mk_PL_charclass.pl
index 63c06bc9f6..918bb4de58 100644
--- a/regen/mk_PL_charclass.pl
+++ b/regen/mk_PL_charclass.pl
@@ -161,7 +161,7 @@ my @bits; # Bit map for each code point
# For each character, calculate which properties it matches.
for my $ord (0..255) {
my $char = chr($ord);
- utf8::upgrade($char); # Important to use Unicode semantics!
+ utf8::upgrade($char); # Important to use Unicode rules!
# Look at all the properties we care about here.
for my $property (@properties) {