X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/89853d76c827c07a8cd0cb38bd1727e96afaadef..a3f3223ababd6599a29851d4023bb4f47b60d676:/pod/perldelta.pod diff --git a/pod/perldelta.pod b/pod/perldelta.pod index 3937542..ccaf480 100644 --- a/pod/perldelta.pod +++ b/pod/perldelta.pod @@ -18,7 +18,7 @@ This release includes two updates with widespread effects: =item * C<.> no longer in C<@INC> The current modules, and for the execution of scripts. See the section -L< from @INC>> for the full details. +L<< Removal of the current directory (C<.>) from C<@INC> >> for the full details. =item * C may now warn @@ -101,12 +101,6 @@ themselves. E.g. L sets it since loading modules from a relative path is a common idiom in test code. If you find that you have C<.> in C<@INC> on a perl built with default settings it's likely that your code is being invoked by a toolchain module of some sort. - -=head2 create a safer utf8_hop() called utf8_hop_safe() - -Unlike utf8_hop(), utf8_hop_safe() won't navigate before the beginning or after -the end of the supplied buffer. - =head2 @{^CAPTURE}, %{^CAPTURE}, and %{^CAPTURE_ALL} C<@{^CAPTURE}> exposes the capture buffers of the last match as an @@ -404,7 +398,6 @@ C<@INC>, since it introduces both a security risk and hides issues of accidentally requiring dot in C<@INC>, as explained above. =back ->>>>>>> Add more extensive information about @INC changes into perldelta (RT#131304) =head2 "Escaped" colons and relative paths in PATH @@ -1584,8 +1577,7 @@ the C pragma, is no longer supported as of Perl 5.26.0. Since C<.> is now removed from C<@INC> by default, C will now trigger a warning recommending to fix the C statement: -L +L%s"?> =back @@ -2778,12 +2770,6 @@ memory if the typeglob in question has never been accessed before. =item * -In 5.25.4 fchown() was changed not to accept negative one as an argument -because in some platforms that is an error. However, in some other platforms -that is an acceptable argument. This change has been reverted [perl #128967]. - -=item * - Mentioning the same constant twice in a row (which is a syntax error) no longer fails an assertion under debugging builds. This was a regression from 5.20. [perl #126482]