[PATCH] perl5180delta Fixes #12897
Comments
From @SmylersThis is a bug report for perl from Smylers@stripey.com, Some fixes for perl5180delta.pod, in the rjbs/perldelta-5.18 branch. Flags: Site configuration information for perl 5.14.2: Configured by Debian Project at Mon Mar 18 19:35:03 UTC 2013. Summary of my perl5 (revision 5 version 14 subversion 2) configuration: Locally applied patches: @INC for perl 5.14.2: Environment for perl 5.14.2: Smylers |
From @Smylers0001-perldelta-no-hyphens-after-ly-adverbs.patchFrom 481c362c38d452402873c0457c8fc27e1b5b69c6 Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 10:02:54 +0100
Subject: [PATCH 01/19] perldelta: no hyphens after "ly" adverbs
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
English doesn't have hyphens in adverb-adjective compound modifiers: the
adverb unambiguously modifies the following adjective, so there isn't the
ambiguity you get with double-adjective modifiers (where a hyphen is often
required to get the intended meaning).
---
Porting/perl5180delta.pod | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0001-perldelta-no-hyphens-after-ly-adverbs.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0001-perldelta-no-hyphens-after-ly-adverbs.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index caaf656..5b3ed920 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -16,7 +16,7 @@ L<perl5160delta>, which describes differences between 5.14.0 and 5.16.0.
=head2 New mechanism for experimental features
-Newly-added experimental features will now require this incantation:
+Newly added experimental features will now require this incantation:
no warnings "experimental::feature_name";
use feature "feature_name"; # would warn without the prev line
@@ -25,7 +25,7 @@ There is a new warnings category, called "experimental", containing
warnings that the L<feature> pragma emits when enabling experimental
features.
-Newly-added experimental features will also be given special warning IDs,
+Newly added experimental features will also be given special warning IDs,
which consist of "experimental::" followed by the name of the feature. (The
plan is to extend this mechanism eventually to all warnings, to allow them
to be enabled or disabled individually, and not just by category.)
@@ -1498,7 +1498,7 @@ string buffers in CPAN modules. [perl #73542]
=item *
-Inside a BEGIN block, C<PL_compcv> now points to the currently-compiling
+Inside a BEGIN block, C<PL_compcv> now points to the currently compiling
subroutine, rather than the BEGIN block itself.
=item *
@@ -1914,7 +1914,7 @@ of the return value of C<s///e>.
The C<$|> autoflush variable is created on-the-fly when needed. If this
happened (e.g., if it was mentioned in a module or eval) when the
-currently-selected filehandle was a typeglob with an empty IO slot, it used
+currently selected filehandle was a typeglob with an empty IO slot, it used
to crash. [perl #115206]
=item *
@@ -2031,7 +2031,7 @@ error, but now is merely a warning (and that something won't match).
It used to be possible for formats defined in subroutines that have
subsequently been undefined and redefined to close over variables in the
-wrong pad (the newly-defined enclosing sub), resulting in crashes or
+wrong pad (the newly defined enclosing sub), resulting in crashes or
"Bizarre copy" errors.
=item *
@@ -2138,7 +2138,7 @@ Formats and C<use> statements are now permitted inside formats.
C<print $x> and C<sub { print $x }-E<gt>()> now always produce the same output.
It was possible for the latter to refuse to close over $x if the variable was
-not active; e.g., if it was defined outside a currently-running named
+not active; e.g., if it was defined outside a currently running named
subroutine.
=item *
@@ -2836,7 +2836,7 @@ non-objects.
=item *
-C<$byte_overload .= $utf8> no longer results in doubly-encoded UTF8 if the
+C<$byte_overload .= $utf8> no longer results in doubly encoded UTF8 if the
left-hand scalar happened to have produced a UTF8 string the last time
overloading was invoked.
--------------1.7.10.4--
|
From @Smylers0002-perldelta-order-is-intended-word.patchFrom 73d76451c91ea95ba5c3298a8d31bd381fa15762 Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 10:04:48 +0100
Subject: [PATCH 02/19] perldelta: "order" is intended word
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
---
Porting/perl5180delta.pod | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0002-perldelta-order-is-intended-word.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0002-perldelta-order-is-intended-word.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index 5b3ed920..e2ee6f5 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -46,7 +46,7 @@ experimental.
Changes to the implementation of hashes in perl 5.18.0 will be one of the most
visible changes to the behavior of existing code. For the most part, these
changes will be visible as two distinct hash variables now providing their
-contents in a different variable where it was previously identical. When
+contents in a different order where it was previously identical. When
encountering these changes, the key to cleaning up from them is to accept that
B<hashes are unordered collections> and to act accordingly.
--------------1.7.10.4--
|
From @Smylers0003-perldelta-missing-parenthetical-comma.patchFrom ccefe25cc0414c0130aad20a85f23aed173e79a7 Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 10:07:50 +0100
Subject: [PATCH 03/19] perldelta: missing parenthetical comma
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
"in hex" is parenthetical
---
Porting/perl5180delta.pod | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0003-perldelta-missing-parenthetical-comma.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0003-perldelta-missing-parenthetical-comma.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index e2ee6f5..bcf1aca 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -92,7 +92,7 @@ which might exceed that of an integer. (SipHash uses a 16 byte seed).
=head3 Output of PERL_HASH_SEED_DEBUG has been changed
The environment variable PERL_HASH_SEED_DEBUG now shows both the hash
-function perl was built with AND the seed, in hex in use for that process.
+function perl was built with AND the seed, in hex, in use for that process.
Code parsing this output, should it exist, must change to accomodate the
new format. Example of the new format:
--------------1.7.10.4--
|
From @Smylers0004-perldelta-an-env-var-doesn-t-do-anything-itself.patchFrom 538217cf11e7345245c75f6bb1535271f435ac01 Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 10:12:54 +0100
Subject: [PATCH 04/19] perldelta: an env var doesn't do anything itself
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
---
Porting/perl5180delta.pod | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0004-perldelta-an-env-var-doesn-t-do-anything-itself.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0004-perldelta-an-env-var-doesn-t-do-anything-itself.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index bcf1aca..e7d79a9 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -91,10 +91,10 @@ which might exceed that of an integer. (SipHash uses a 16 byte seed).
=head3 Output of PERL_HASH_SEED_DEBUG has been changed
-The environment variable PERL_HASH_SEED_DEBUG now shows both the hash
-function perl was built with AND the seed, in hex, in use for that process.
-Code parsing this output, should it exist, must change to accomodate the
-new format. Example of the new format:
+The environment variable PERL_HASH_SEED_DEBUG now makes perl show both the
+hash function perl was built with AND the seed, in hex, in use for that
+process. Code parsing this output, should it exist, must change to accomodate
+the new format. Example of the new format:
$ PERL_HASH_SEED_DEBUG=1 ./perl -e1
HASH_FUNCTION = MURMUR3 HASH_SEED = 0x1476bb9f
--------------1.7.10.4--
|
From @Smylers0005-perldelta-spelling-fix.patchFrom b5b8b659332c37609d9804b0f5baed40545d7eb5 Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 10:17:05 +0100
Subject: [PATCH 05/19] perldelta: spelling fix
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
---
Porting/perl5180delta.pod | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0005-perldelta-spelling-fix.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0005-perldelta-spelling-fix.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index e7d79a9..28f4bab 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -93,7 +93,7 @@ which might exceed that of an integer. (SipHash uses a 16 byte seed).
The environment variable PERL_HASH_SEED_DEBUG now makes perl show both the
hash function perl was built with AND the seed, in hex, in use for that
-process. Code parsing this output, should it exist, must change to accomodate
+process. Code parsing this output, should it exist, must change to accommodate
the new format. Example of the new format:
$ PERL_HASH_SEED_DEBUG=1 ./perl -e1
--------------1.7.10.4--
|
From @Smylers0006-perldelta-DTrace-probes-as-bullet-list.patchFrom ce7d91799a1fa89cd5e06a7974bac62da64ba05b Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 10:20:11 +0100
Subject: [PATCH 06/19] perldelta: DTrace probes as bullet list
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
It was a definition list, but with only terms (no definitions), and hence
no indentation.
---
Porting/perl5180delta.pod | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0006-perldelta-DTrace-probes-as-bullet-list.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0006-perldelta-DTrace-probes-as-bullet-list.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index 28f4bab..abd8c62 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -123,11 +123,17 @@ The following new DTrace probes have been added:
=over 4
-=item C<op-entry>
+=item *
+
+C<op-entry>
+
+=item *
+
+C<loading-file>
-=item C<loading-file>
+=item *
-=item C<loaded-file>
+C<loaded-file>
=back
--------------1.7.10.4--
|
From @Smylers0007-perldelta-short-circuit-cross-reference-chain.patchFrom 2bed457ffc9d99a129ca8cd465918d012a954986 Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 10:26:23 +0100
Subject: [PATCH 07/19] perldelta: short-circuit cross-reference chain
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
perlre/(?[ ]) just says to see perlrecharclass/Extended Bracketed
Character Classes, so may as well point people there in the first place.
---
Porting/perl5180delta.pod | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0007-perldelta-short-circuit-cross-reference-chain.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0007-perldelta-short-circuit-cross-reference-chain.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index abd8c62..9551b25 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -150,7 +150,7 @@ intersection, etc., of sets of code points, similar to
L<Unicode::Regex::Set>. It can also be used to extend C</x> processing
to [bracketed] character classes, and as a replacement of user-defined
properties, allowing more complex expressions than they do. See
-L<perlre/(?[ ])>.
+L<perlrecharclass/Extended Bracketed Character Classes>.
=head2 Lexical subroutines
--------------1.7.10.4--
|
From @Smylers0008-perldelta-avoid-comma-splice.patchFrom 995b0beb2981a0191b9690bd17b12ef7b35e9a23 Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 11:34:21 +0100
Subject: [PATCH 08/19] perldelta: avoid comma splice
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
---
Porting/perl5180delta.pod | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0008-perldelta-avoid-comma-splice.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0008-perldelta-avoid-comma-splice.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index 9551b25..6474919 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -186,7 +186,7 @@ empty string.
=head2 More CORE:: subs
Several more built-in functions have been added as subroutines to the
-CORE:: namespace, namely, those non-overridable keywords that can be
+CORE:: namespace - namely, those non-overridable keywords that can be
implemented without custom parsers: C<defined>, C<delete>, C<exists>,
C<glob>, C<pos>, C<protoytpe>, C<scalar>, C<split>, C<study>, and C<undef>.
--------------1.7.10.4--
|
From @Smylers0009-perldelta-join-sentence-fragment.patchFrom 0ffe525b3faf1b3dfebbd15b249419df8491ed04 Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 11:41:00 +0100
Subject: [PATCH 09/19] perldelta: join sentence fragment
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
---
Porting/perl5180delta.pod | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0009-perldelta-join-sentence-fragment.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0009-perldelta-join-sentence-fragment.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index 6474919..c750959 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -277,7 +277,7 @@ functions in L<charnames> have been correspondingly updated.
Unicode has now withdrawn their previous recommendation for regular
expressions to automatically handle cases where a single character can
-match multiple characters case-insensitively; for example, the letter
+match multiple characters case-insensitively, for example the letter
LATIN SMALL LETTER SHARP S and the sequence C<ss>. This is because
it turns out to be impracticable to do this correctly in all
circumstances. Because Perl has tried to do this as best it can, it
--------------1.7.10.4--
|
From @Smylers0010-perldelta-extraneous-word-removed.patchFrom 5b9c13db8fc915f9568c8532e3cd23528eb18879 Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 11:43:57 +0100
Subject: [PATCH 10/19] perldelta: extraneous word removed
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
---
Porting/perl5180delta.pod | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0010-perldelta-extraneous-word-removed.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0010-perldelta-extraneous-word-removed.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index c750959..b1815d9 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -286,7 +286,7 @@ However, a new restriction is being added on such matches when they
occur in [bracketed] character classes. People were specifying
things such as C</[\0-\xff]/i>, and being surprised that it matches the
two character sequence C<ss> (since LATIN SMALL LETTER SHARP S occurs in
-this range). This behavior is also inconsistent with the using a
+this range). This behavior is also inconsistent with using a
property instead of a range: C<\p{Block=Latin1}> also includes LATIN
SMALL LETTER SHARP S, but C</[\p{Block=Latin1}]/i> does not match C<ss>.
The new rule is that for there to be a multi-character case-insensitive
--------------1.7.10.4--
|
From @Smylers0011-perldelta-semicolon-there-isn-t-code.patchFrom 80c3b43e090dc23e8d74680787cd23f4f7dd17d5 Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 11:47:58 +0100
Subject: [PATCH 11/19] perldelta: semicolon there isn't code
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
---
Porting/perl5180delta.pod | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0011-perldelta-semicolon-there-isn-t-code.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0011-perldelta-semicolon-there-isn-t-code.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index b1815d9..26a8687 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -305,7 +305,7 @@ unrestricted, and opened the door to several kinds of insanity. As of
to accepting characters that match the C<\p{POSIX_Punct}> property.
There are no longer any differences in the parsing of identifiers
-specified as C<$...> or C<${...};> previously, they were dealt with in
+specified as C<$...> or C<${...}>; previously, they were dealt with in
different parts of the core, and so had slightly different behavior. For
instance, C<${foo:bar}> was a legal variable name. Since they are now
both parsed by the same code, that is no longer the case.
--------------1.7.10.4--
|
From @Smylers0012-perldelta-moved-here-doc-parsing-fix-to-fixes.patchFrom 15e572c2e5b0ebb9cf7e2ee8f3b9e5a545d14d83 Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 11:56:16 +0100
Subject: [PATCH 12/19] perldelta: moved here-doc parsing fix to fixes
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
The change is to make it always behave as it was already documented, so
that's a bug fix rather than an incompatible change.
---
Porting/perl5180delta.pod | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0012-perldelta-moved-here-doc-parsing-fix-to-fixes.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0012-perldelta-moved-here-doc-parsing-fix-to-fixes.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index 26a8687..92a9a33 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -397,13 +397,6 @@ that identified the caller. Nothing on CPAN was using this, and it got in
the way of a bug fix, so it was removed. If you really need to identify
the caller, see L<Devel::Callsite> on CPAN.
-=head2 Here-doc parsing
-
-The body of a here-document inside a quote-like operator now always begins
-on the line after the "<<foo" marker. Previously, it was documented to
-begin on the line following the containing quote-like operator, but that
-was only sometimes the case [perl #114040].
-
=head2 Alphanumeric operators must now be separated from the closing
delimiter of regular expressions
@@ -1650,6 +1643,13 @@ and PERL_DEBUG_READONLY_OPS, has been retired.
=item *
+The body of a here-document inside a quote-like operator now always begins
+on the line after the "<<foo" marker. Previously, it was documented to
+begin on the line following the containing quote-like operator, but that
+was only sometimes the case [perl #114040].
+
+=item *
+
Here-doc terminators no longer require a terminating newline character when
they occur at the end of a file. This was already the case at the end of a
string eval [perl #65838].
--------------1.7.10.4--
|
From @Smylers0013-perldelta-fatal-error-is-an-error-not-a-warning.patchFrom 431619847a42158412c45e188fe4015593e2242f Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 12:46:50 +0100
Subject: [PATCH 13/19] perldelta: fatal error is an error, not a warning
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
"(F)" removed, since everything in the 'New Errors' section is obviously
an error, and none of the other errors in there are marked as such.
---
Porting/perl5180delta.pod | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0013-perldelta-fatal-error-is-an-error-not-a-warning.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0013-perldelta-fatal-error-is-an-error-not-a-warning.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index 92a9a33..ca9c419 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -915,6 +915,16 @@ non-magical variables, and then in Perl 5.14 for magical (e.g., tied)
variables. It has now been restored. In the mean time, undef was treated
as an empty string [perl #113576].
+=item *
+
+L<Experimental "%s" subs not enabled|perldiag/"Experimental "%s" subs not enabled">
+
+To use lexical subs, you must first enable them:
+
+ no warnings 'experimental::lexical_subs';
+ use feature 'lexical_subs';
+ my sub foo { ... }
+
=back
=head3 New Warnings
@@ -955,16 +965,6 @@ L<'Passing malformed UTF-8 to "%s" is deprecated'|perldiag/"Passing malformed UT
=item *
-L<Experimental "%s" subs not enabled|perldiag/"Experimental "%s" subs not enabled">
-
-(F) To use lexical subs, you must first enable them:
-
- no warnings 'experimental::lexical_subs';
- use feature 'lexical_subs';
- my sub foo { ... }
-
-=item *
-
L<Subroutine "&%s" is not available|perldiag/"Subroutine "&%s" is not available">
(W closure) During compilation, an inner named subroutine or eval is
--------------1.7.10.4--
|
From @Smylers0014-perldelta-continuation-of.patchFrom 86c6148fa3a2839dce41dd4e803e0ad3aecf176a Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 12:58:06 +0100
Subject: [PATCH 14/19] perldelta: "continuation of"
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
Not "for".
---
Porting/perl5180delta.pod | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0014-perldelta-continuation-of.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0014-perldelta-continuation-of.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index ca9c419..2e0d934 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -1219,7 +1219,7 @@ gibibytes of memory that may be safely used.
BeOS was an operating system for personal computers developed by Be Inc,
initially for their BeBox hardware. The OS Haiku was written as an open
-source replacement/continuation for BeOS, and its perl port is current and
+source replacement for/continuation of BeOS, and its perl port is current and
actively maintained.
=item UTS Global
--------------1.7.10.4--
|
From @Smylers0015-perldelta-code-marked-as-such.patchFrom caf288528f4427d6f1a6f9b743e9ee02ce78061f Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 13:06:17 +0100
Subject: [PATCH 15/19] perldelta: code marked as such
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
---
Porting/perl5180delta.pod | 44 ++++++++++++++++++++++----------------------
1 file changed, 22 insertions(+), 22 deletions(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0015-perldelta-code-marked-as-such.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0015-perldelta-code-marked-as-such.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index 2e0d934..c3416a5 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -339,7 +339,7 @@ global C<$_> an alias for its argument, just like C<foreach>. However, it
still uses lexical C<$_> if there is lexical C<$_> in scope (again, just like
C<foreach>) [perl #114020].
-=head2 Lexical $_ is now experimental
+=head2 Lexical C<$_> is now experimental
Since it was introduced in Perl 5.10, it has caused much confusion with no
obvious solution:
@@ -655,7 +655,7 @@ emailing C<perl5-porters@perl.org>.
=item *
-Swapping of $< and $>
+Swapping of C<$<> and C<< $> >>
For more information about this future deprecation, see L<the relevant RT
ticket|https://rt.perl.org/rt3/Ticket/Display.html?id=96212>.
@@ -1129,10 +1129,10 @@ reason.
The 'Can't use "my %s" in sort comparison' error has been downgraded to a
warning, '"my %s" used in sort comparison' (with 'state' instead of 'my'
for state variables). In addition, the heuristics for guessing whether
-lexical $a or $b has been misused have been improved to generate fewer
-false positives. Lexical $a and $b are no longer disallowed if they are
+lexical C<$a> or C<$b> has been misused have been improved to generate fewer
+false positives. Lexical C<$a> and C<$b> are no longer disallowed if they are
outside the sort block. Also, a named unary or list operator inside the
-sort block no longer causes the $a or $b to be ignored [perl #86136].
+sort block no longer causes the C<$a> or C<$b> to be ignored [perl #86136].
=back
@@ -1166,7 +1166,7 @@ specific files in "$install_base/lib/perl5/$archname". This makes
it difficult to use a common INSTALL_BASE library path with
multiple versions of perl.
-By setting -Duseversionedarchname, the $archname will be
+By setting C<-Duseversionedarchname>, the $archname will be
distinct for architecture *and* API version, allowing mixed use of
INSTALL_BASE.
@@ -1475,7 +1475,7 @@ A new op type, C<OP_PADRANGE> has been introduced. The perl peephole
optimiser will, where possible, substitute a single padrange op for a
pushmark followed by one or more pad ops, and possibly also skipping list
and nextstate ops. In addition, the op can carry out the tasks associated
-with the RHS of a my(...) = @_ assignment, so those ops may be optimised
+with the RHS of a C<my(...) = @_> assignment, so those ops may be optimised
away too.
=item *
@@ -1528,7 +1528,7 @@ The new C<RXf_MODIFIES_VARS> flag can be set by custom regular expression
engines to indicate that the execution of the regular expression may cause
variables to be modified. This lets C<s///> know to skip certain
optimisations. Perl's own regular expression engine sets this flag for the
-special backtracking verbs that set $REGMARK and $REGERROR.
+special backtracking verbs that set C<$REGMARK> and C<$REGERROR>.
=item *
@@ -1564,7 +1564,7 @@ just like C<&{...}> [perl #96872].
=item *
The C<SVf_AMAGIC> flag to indicate overloading is now on the stash, not the
-object. It is now set automatically whenever a method or @ISA changes, so
+object. It is now set automatically whenever a method or C<@ISA> changes, so
its meaning has changed, too. It now means "potentially overloaded". When
the overload table is calculated, the flag is automatically turned off if
there is no overloading, so there should be no noticeable slowdown.
@@ -1661,7 +1661,7 @@ they've finished using it.
=item *
-A trailing '/' on a path in @INC will no longer have an additional '/'
+A trailing '/' on a path in C<@INC> will no longer have an additional '/'
appended.
=item *
@@ -1930,8 +1930,8 @@ Line numbers at the end of a string eval are no longer off by one.
=item *
-@INC filters (subroutines returned by subroutines in @INC) that set $_ to a
-copy-on-write scalar no longer cause the parser to modify that string
+C<@INC> filters (subroutines returned by subroutines in C<@INC>) that set C<$_>
+to a copy-on-write scalar no longer cause the parser to modify that string
buffer in place.
=item *
@@ -2047,8 +2047,8 @@ line number.
=item *
-The %vd sprintf format does not support version objects for alpha versions.
-It used to output the format itself (%vd) when passed an alpha version, and
+The C<%vd> sprintf format does not support version objects for alpha versions.
+It used to output the format itself (C<%vd>) when passed an alpha version, and
also emit an "Invalid conversion in printf" warning. It no longer does,
but produces the empty string in the output. It also no longer leaks
memory in this case.
@@ -2061,7 +2061,7 @@ SUPER package had already been accessed by other means.
=item *
Stash aliasing (C<*foo:: = *bar::>) no longer causes SUPER calls to ignore
-changes to methods or @ISA or use the wrong package.
+changes to methods or C<@ISA> or use the wrong package.
=item *
@@ -2143,14 +2143,14 @@ Formats and C<use> statements are now permitted inside formats.
=item *
C<print $x> and C<sub { print $x }-E<gt>()> now always produce the same output.
-It was possible for the latter to refuse to close over $x if the variable was
-not active; e.g., if it was defined outside a currently running named
+It was possible for the latter to refuse to close over C<$x> if the variable
+was not active; e.g., if it was defined outside a currently running named
subroutine.
=item *
Similarly, C<print $x> and C<print eval '$x'> now produce the same output.
-This also allows "my $x if 0" variables to be seen in the debugger [perl
+This also allows C<my $x if 0> variables to be seen in the debugger [perl
#114018].
=item *
@@ -2278,7 +2278,7 @@ C<bless>.
Objects that were created before a class had any overloading used to remain
non-overloaded even if the class gained overloading through C<use overload>
-or @ISA changes, and even after C<bless>. This has been fixed
+or C<@ISA> changes, and even after C<bless>. This has been fixed
[perl #112708].
=item *
@@ -2745,8 +2745,8 @@ reference".
=item *
-Two bugs involving @ISA have been fixed. C<*ISA = *glob_without_array> and
-C<undef *ISA; @{*ISA}> would prevent future modifications to @ISA from
+Two bugs involving C<@ISA> have been fixed. C<*ISA = *glob_without_array> and
+C<undef *ISA; @{*ISA}> would prevent future modifications to C<@ISA> from
updating the internal caches used to look up methods. The
*glob_without_array case was a regression from Perl 5.12.
@@ -2848,7 +2848,7 @@ overloading was invoked.
=item *
-C<goto &sub> now uses the current value of @_, instead of using the array
+C<goto &sub> now uses the current value of C<@_>, instead of using the array
the subroutine was originally called with. This means
C<local @_ = (...); goto &sub> now works [perl #43077].
--------------1.7.10.4--
|
From @Smylers0016-perldelta-unwanted-comma-removed.patchFrom f57f2fb9872877d13e7e33f9278af8256806288f Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 13:07:14 +0100
Subject: [PATCH 16/19] perldelta: unwanted comma removed
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
The sense is "matching no longer excludes", which can't take a comma (even
though the qualifiers on "matching" are quite long)>
---
Porting/perl5180delta.pod | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0016-perldelta-unwanted-comma-removed.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0016-perldelta-unwanted-comma-removed.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index c3416a5..b0200e7 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -1481,7 +1481,7 @@ away too.
=item *
Case-insensitive matching inside a [bracketed] character class with a
-multi-character fold, no longer excludes one of the possibilities in the
+multi-character fold no longer excludes one of the possibilities in the
circumstances that it used to. [perl #89774].
=item *
--------------1.7.10.4--
|
From @Smylers0017-perldelta-no-missing.patchFrom 701728d8aae692df20f983dac52963a7026694c7 Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 13:55:04 +0100
Subject: [PATCH 17/19] perldelta: "no" missing
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
---
Porting/perl5180delta.pod | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0017-perldelta-no-missing.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0017-perldelta-no-missing.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index b0200e7..42c2fb8 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -2345,7 +2345,7 @@ braces: this now works:
/(?{ $x='{' })/
-This means that this error message is longer generated:
+This means that this error message is no longer generated:
Sequence (?{...}) not terminated or not {}-balanced in regex
--------------1.7.10.4--
|
From @Smylers0018-perldelta-singular-agreement.patchFrom 6bba0a83f0b83db47b39ff7eebd4f8b03072f191 Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 14:10:32 +0100
Subject: [PATCH 18/19] perldelta: singular agreement
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
---
Porting/perl5180delta.pod | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0018-perldelta-singular-agreement.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0018-perldelta-singular-agreement.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index 42c2fb8..be30db8 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -2694,7 +2694,7 @@ perl 5.10.0, if the format referenced lexical variables from the outer sub.
=item *
-Using a C<format> defined inside a closures, which format references
+Using a C<format> defined inside a closure, which format references
lexical variables from outside, never really worked unless the C<write>
call was directly inside the closure. In 5.10.0 it even started crashing.
Now the copy of that closure nearest the top of the call stack is used to
--------------1.7.10.4--
|
From @Smylers0019-perldelta-corrupts.patchFrom 49bcf6dbdbaec12ad4a43d5297a876ebd5a4373d Mon Sep 17 00:00:00 2001
From: Smylers <Smylers@stripey.com>
Date: Thu, 4 Apr 2013 14:14:30 +0100
Subject: [PATCH 19/19] perldelta: "corrupts"
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1.7.10.4"
This is a multi-part message in MIME format.
--------------1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
---
Porting/perl5180delta.pod | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--------------1.7.10.4
Content-Type: text/x-patch; name="0019-perldelta-corrupts.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0019-perldelta-corrupts.patch"
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index be30db8..b723071 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -2789,7 +2789,7 @@ C<"/\n\n" =~ m#\A(?:^/$)#im> would not match [perl #115242].
=item *
-Failed C<fork> in list context no longer currupts the stack.
+Failed C<fork> in list context no longer corrupts the stack.
C<@a = (1, 2, fork, 3)> used to gobble up the 2 and assign C<(1, undef, 3)>
if the C<fork> call failed.
--------------1.7.10.4--
|
From @rjbsThese largely got applied, thanks. -- |
From [Unknown Contact. See original ticket]These largely got applied, thanks. -- |
|
@rjbs - Status changed from 'new' to 'resolved' |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Migrated from rt.perl.org#117473 (status was 'resolved')
Searchable as RT117473$
The text was updated successfully, but these errors were encountered: