diff options
author | Smylers <Smylers@stripey.com> | 2018-06-07 16:21:11 +0100 |
---|---|---|
committer | David Mitchell <davem@iabyn.com> | 2018-06-18 14:10:29 +0100 |
commit | 0ba4cd08e0edda2938e982938c9ac520e86a8302 (patch) | |
tree | 943ab83cccc7a17a34d1794a526494e76b17eb80 | |
parent | 4d31efb6c54b7fc01111d262a523c115d3ff533d (diff) | |
download | perl-0ba4cd08e0edda2938e982938c9ac520e86a8302.tar.gz |
Clarify that /({...)/ is deprecated
Previously this was just a noun phrase, describing the thing that is
deprecated. Turn that into a statement, explicitly saying it is
deprecated.
Admittedly, the noun phrase is in a section headed ‘Deprecations’, but
some of the items in the list are about changes to deprecations, and
everything else in the list is a full sentence, so make this be one too.
-rw-r--r-- | pod/perldelta.pod | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perldelta.pod b/pod/perldelta.pod index 70aa8e26bf..abe941968e 100644 --- a/pod/perldelta.pod +++ b/pod/perldelta.pod @@ -394,7 +394,7 @@ where the C<"{"> will not be repurposed. Note that these uses continue to raise a deprecation message. -=head2 Use of unescaped C<"{"> immediately after a C<"("> in regular expression patterns +=head2 Use of unescaped C<"{"> immediately after a C<"("> in regular expression patterns is deprecated Using unescaped left braces is officially deprecated everywhere, but it is not enforced in contexts where their use does not interfere with |