A mechanism for inlineable OP equivalents of XSUBs is a TODO.

[p5sagit/p5-mst-13.2.git] / pod / perlvar.pod

diff --git a/pod/perlvar.pod b/pod/perlvar.pod
index 7c61a05..834a880 100644 (file)
--- a/pod/perlvar.pod
+++ b/pod/perlvar.pod
@@ -214,11 +214,11 @@ able to use them in the sort() comparison block or function.
 
 =over 8
 
-=item $<I<digits>>
+=item $<I<digits>> ($1, $2, ...)
 X<$1> X<$2> X<$3>
 
 Contains the subpattern from the corresponding set of capturing
-parentheses from the last pattern match, not counting patterns
+parentheses from the last successful pattern match, not counting patterns
 matched in nested blocks that have been exited already.  (Mnemonic:
 like \digits.)  These variables are all read-only and dynamically
 scoped to the current BLOCK.
@@ -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.