5.002 beta 1

If you're adventurous, have a look at

    ftp://ftp.sems.com/pub/outgoing/perl5.0/perl5.002beta1.tar.gz

Many thanks to Andy for doing the integration.

Obviously, if you consult the bugs database, you'll note there are
still plenty of buglets that need fixing, and several enhancements that
I've intended to put in still haven't made it in (Hi, Tim and Ilya).
But I think it'll be pretty stable.  And you can start to fiddle around
with prototypes (which are, of course, still totally undocumented).

Packrats, don't worry too much about readvertising this widely.
Nowadays we're on a T1 here, so our bandwidth is okay.

Have the appropriate amount of jollity.

Larry

1 files changed, 8 insertions, 7 deletions

diff --git a/pod/perlre.pod b/pod/perlre.pod
index 295b6bd518..2f2d79b492 100644
--- a/pod/perlre.pod
+++ b/pod/perlre.pod
@@ -19,12 +19,13 @@ in question might not actually be a slash.  In fact, any of these
 modifiers may also be embedded within the regular expression itself using
 the new C<(?...)> construct.  See below.
 
-The C</x> modifier itself needs a little more explanation.  It tells the
-regular expression parser to ignore whitespace that is not backslashed
-or within a character class.  You can use this to break up your regular
-expression into (slightly) more readable parts.  Together with the
-capability of embedding comments described later, this goes a long
-way towards making Perl 5 a readable language.  See the C comment
+The C</x> modifier itself needs a little more explanation.  It tells
+the regular expression parser to ignore whitespace that is not
+backslashed or within a character class.  You can use this to break up
+your regular expression into (slightly) more readable parts.  The C<#>
+character is also treated as a metacharacter introducing a comment,
+just as in ordinary Perl code.  Taken together, these features go a
+long way towards making Perl 5 a readable language.  See the C comment
 deletion code in L<perlop>.
 
 =head2 Regular Expressions
@@ -147,7 +148,7 @@ When the bracketing construct C<( ... )> is used, \<digit> matches the
 digit'th substring.  (Outside of the pattern, always use "$" instead of
 "\" in front of the digit.  The scope of $<digit> (and C<$`>, C<$&>, and C<$')>
 extends to the end of the enclosing BLOCK or eval string, or to the
-next pattern match with subexpressions.  
+next successful pattern match, whichever comes first.
 If you want to
 use parentheses to delimit subpattern (e.g. a set of alternatives) without
 saving it as a subpattern, follow the ( with a ?.