This is a live mirror of the Perl 5 development currently hosted at
https://github.com/perl/perl5
https://perl5.git.perl.org
/
perl5.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
PerlIO::Via: check arg is non-NULL before using it.
[perl5.git]
/
pod
/
perl56delta.pod
diff --git
a/pod/perl56delta.pod
b/pod/perl56delta.pod
index
fc0d668
..
8b6272b
100644
(file)
--- a/
pod/perl56delta.pod
+++ b/
pod/perl56delta.pod
@@
-1,6
+1,6
@@
=head1 NAME
=head1 NAME
-perldelta - what's new for perl v5.6.0
+perl
56
delta - what's new for perl v5.6.0
=head1 DESCRIPTION
=head1 DESCRIPTION
@@
-112,16
+112,14
@@
to check if you're running a particular version of Perl:
# new features supported
}
# new features supported
}
-C<require> and C<use> also have some special magic to support such literals.
-They will be interpreted as a version rather than as a module name:
+C<require> and C<use> also have some special magic to support such
+literals, but this particular usage should be avoided because it leads to
+misleading error messages under versions of Perl which don't support vector
+strings. Using a true version number will ensure correct behavior in all
+versions of Perl:
- require v5.6.0; # croak if $^V lt v5.6.0
- use v5.6.0; # same, but croaks at compile-time
-
-Alternatively, the C<v> may be omitted if there is more than one dot:
-
- require 5.6.0;
- use 5.6.0;
+ require 5.006; # run time check for v5.6
+ use 5.006_001; # compile time check for v5.6.1
Also, C<sprintf> and C<printf> support the Perl-specific format flag C<%v>
to print ordinals of characters in arbitrary strings:
Also, C<sprintf> and C<printf> support the Perl-specific format flag C<%v>
to print ordinals of characters in arbitrary strings:
@@
-148,7
+146,7
@@
than C<$]> (a numeric value). (This is a potential incompatibility.
Send us a report via perlbug if you are affected by this.)
The v1.2.3 syntax is also now legal in Perl.
Send us a report via perlbug if you are affected by this.)
The v1.2.3 syntax is also now legal in Perl.
-See L<Support for strings represented as a vector of ordinals> for more on that.
+See L<
/
Support for strings represented as a vector of ordinals> for more on that.
To cope with the new versioning system's use of at least three significant
digits for each version component, the method used for incrementing the
To cope with the new versioning system's use of at least three significant
digits for each version component, the method used for incrementing the
@@
-167,13
+165,13
@@
as requiring an automatic lock() when it is entered, you had to declare
that with a C<use attrs> pragma in the body of the subroutine.
That can now be accomplished with declaration syntax, like this:
that with a C<use attrs> pragma in the body of the subroutine.
That can now be accomplished with declaration syntax, like this:
- sub mymethod : locked method
;
+ sub mymethod : locked method;
...
sub mymethod : locked method {
...
}
...
sub mymethod : locked method {
...
}
- sub othermethod :locked :method
;
+ sub othermethod :locked :method;
...
sub othermethod :locked :method {
...
...
sub othermethod :locked :method {
...
@@
-457,7
+455,7
@@
When the last non-weak reference to an object is deleted, the object
is destroyed and all the weak references to the object are
automatically undef-ed.
is destroyed and all the weak references to the object are
automatically undef-ed.
-To use this feature, you need the WeakRef package from CPAN, which
+To use this feature, you need the
Devel::
WeakRef package from CPAN, which
contains additional documentation.
NOTE: This is an experimental feature. Details are subject to change.
contains additional documentation.
NOTE: This is an experimental feature. Details are subject to change.
@@
-789,9
+787,15
@@
already. The fatal error has been downgraded to an optional warning:
This warns you that C<"fred@example.com"> is going to turn into
C<fred.com> if you don't backslash the C<@>.
This warns you that C<"fred@example.com"> is going to turn into
C<fred.com> if you don't backslash the C<@>.
-See http://
www.plover.com/~mjd/perl
/at-error.html for more details
+See http://
perl.plover.com
/at-error.html for more details
about the history here.
about the history here.
+=head2 @- and @+ provide starting/ending offsets of regex matches
+
+The new magic variables @- and @+ provide the starting and ending
+offsets, respectively, of $&, $1, $2, etc. See L<perlvar> for
+details.
+
=head1 Modules and Pragmata
=head2 Modules
=head1 Modules and Pragmata
=head2 Modules
@@
-807,7
+811,7
@@
See L<attributes>.
=item B
The Perl Compiler suite has been extensively reworked for this
=item B
The Perl Compiler suite has been extensively reworked for this
-release. More of the standard Perl testsuite passes when run
+release. More of the standard Perl test
suite passes when run
under the Compiler, but there is still a significant way to
go to achieve production quality compiled executables.
under the Compiler, but there is still a significant way to
go to achieve production quality compiled executables.
@@
-1013,7
+1017,7
@@
messages. For example:
=head1 NAME
=head1 NAME
- sample - Using Get
O
pt::Long and Pod::Usage
+ sample - Using Get
o
pt::Long and Pod::Usage
=head1 SYNOPSIS
=head1 SYNOPSIS
@@
-1490,7
+1494,7
@@
capabilities. In other words: if your operating system has the
necessary APIs and datatypes, you should be able just to go ahead and
use them, for threads by Configure -Dusethreads, and for 64 bits
either explicitly by Configure -Duse64bitint or implicitly if your
necessary APIs and datatypes, you should be able just to go ahead and
use them, for threads by Configure -Dusethreads, and for 64 bits
either explicitly by Configure -Duse64bitint or implicitly if your
-system has 64-bit wide datatypes. See also L<"64-bit support">.
+system has 64-bit wide datatypes. See also L<
/
"64-bit support">.
=head2 Long Doubles
=head2 Long Doubles
@@
-1501,7
+1505,7
@@
Perl's scalars, use -Duselongdouble.
=head2 -Dusemorebits
You can enable both -Duse64bitint and -Duselongdouble with -Dusemorebits.
=head2 -Dusemorebits
You can enable both -Duse64bitint and -Duselongdouble with -Dusemorebits.
-See also L<"64-bit support">.
+See also L<
/
"64-bit support">.
=head2 -Duselargefiles
=head2 -Duselargefiles
@@
-1509,7
+1513,7
@@
Some platforms support system APIs that are capable of handling large files
(typically, files larger than two gigabytes). Perl will try to use these
APIs if you ask for -Duselargefiles.
(typically, files larger than two gigabytes). Perl will try to use these
APIs if you ask for -Duselargefiles.
-See L<"Large file support"> for more information.
+See L<
/
"Large file support"> for more information.
=head2 installusrbinperl
=head2 installusrbinperl
@@
-2368,7
+2372,6
@@
You should use the new declaration syntax instead.
The C<use attrs> pragma is now obsolete, and is only provided for
backward-compatibility. See L<perlsub/"Subroutine Attributes">.
The C<use attrs> pragma is now obsolete, and is only provided for
backward-compatibility. See L<perlsub/"Subroutine Attributes">.
-
=item Premature end of script headers
See Server error.
=item Premature end of script headers
See Server error.
@@
-2755,7
+2758,8
@@
Note that the above issue is not relevant to the default build of
Perl, whose interfaces continue to match those of prior versions
(but subject to the other options described here).
Perl, whose interfaces continue to match those of prior versions
(but subject to the other options described here).
-See L<perlguts/"The Perl API"> for detailed information on the
+
+See L<perlguts/Background and PERL_IMPLICIT_CONTEXT> for detailed information on the
ramifications of building Perl with this option.
NOTE: PERL_IMPLICIT_CONTEXT is automatically enabled whenever Perl is built
ramifications of building Perl with this option.
NOTE: PERL_IMPLICIT_CONTEXT is automatically enabled whenever Perl is built
@@
-2989,7
+2993,7
@@
warning. And in Perl 5.005, this special treatment will cease.
If you find what you think is a bug, you might check the
articles recently posted to the comp.lang.perl.misc newsgroup.
If you find what you think is a bug, you might check the
articles recently posted to the comp.lang.perl.misc newsgroup.
-There may also be information at http://www.perl.com/perl/, the Perl
+There may also be information at http://www.perl.com/perl/
, the Perl
Home Page.
If you believe you have an unreported bug, please run the B<perlbug>
Home Page.
If you believe you have an unreported bug, please run the B<perlbug>