summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRicardo Signes <rjbs@cpan.org>2013-05-10 13:26:22 -0400
committerRicardo Signes <rjbs@cpan.org>2013-05-10 13:26:22 -0400
commit1ea0ff56fd90fb8cc156624c60327204fb07d433 (patch)
treec303bbd2afe7b5f1b7785a322e17584f40f823a6
parent9863976f6583b7475498d326ddb6659771bfa96b (diff)
downloadperl-1ea0ff56fd90fb8cc156624c60327204fb07d433.tar.gz
perldelta: add "how to disable" to experimental warnings
-rw-r--r--pod/perldelta.pod6
1 files changed, 6 insertions, 0 deletions
diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index 0d6ad9eb89..2214e6f000 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -37,6 +37,12 @@ By saying
you are taking responsibility for any breakage that future changes to, or
removal of, the feature may cause.
+Since some features (like C<~~> or C<my $_>) now emit experimental warnings,
+and you may want to disable them in code that is also run on perls that do not
+recognize these warning categories, consider using the C<if> pragma like this:
+
+ no if $] >= 5.018, "experimental::feature_name";
+
Existing experimental features may begin emitting these warnings, too. Please
consult L<perlexperiment> for information on which features are considered
experimental.