summaryrefslogtreecommitdiff
path: root/pod/perlvar.pod
diff options
context:
space:
mode:
authorNicholas Clark <nick@ccl4.org>2009-10-13 16:04:18 +0100
committerJesse Vincent <jesse@bestpractical.com>2009-10-16 12:30:17 -0400
commitd1d15184c41c6ad4f16829561163cd118e5ae917 (patch)
tree65d9365479cc68a7c33c3388058bc9654e4a500b /pod/perlvar.pod
parent43b3daf05d64926950dcc26b6a3e77b7c8f513da (diff)
downloadperl-d1d15184c41c6ad4f16829561163cd118e5ae917.tar.gz
Enable deprecation warnings by default.
Diffstat (limited to 'pod/perlvar.pod')
-rw-r--r--pod/perlvar.pod3
1 files changed, 1 insertions, 2 deletions
diff --git a/pod/perlvar.pod b/pod/perlvar.pod
index f2e29e1e2e..834a880cc6 100644
--- a/pod/perlvar.pod
+++ b/pod/perlvar.pod
@@ -1038,8 +1038,7 @@ subscripting and when evaluating the index() and substr() functions.
As of release 5 of Perl, assignment to C<$[> is treated as a compiler
directive, and cannot influence the behavior of any other file.
(That's why you can only assign compile-time constants to it.) Its
-use is deprecated, and will trigger a warning (if the deprecation
-L<warnings> category is enabled. You did C<use warnings>, right?)
+use is deprecated, and by default will trigger a warning.
Note that, unlike other compile-time directives (such as L<strict>),
assignment to C<$[> can be seen from outer lexical scopes in the same file.