=item * C<.> no longer in C<@INC>
The current modules, and for the execution of scripts. See the section
-L<<Removal of the current directory C<.> from @INC>> for the full details.
+L<< Removal of the current directory (C<.>) from C<@INC> >> for the full details.
=item * C<do> may now warn
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
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
Since C<.> is now removed from C<@INC> by default, C<do> will now trigger
a warning recommending to fix the C<do> statement:
-L<do "%s" failed, '.' is no longer in @INC|perldiag/do "%s" failed, '.' is no
-longer in @INC; did you mean do ".\/%s"?>
+L<do "%s" failed, '.' is no longer in @INC|perldiag/do "%s" failed, '.' is no longer in @INC; did you mean do ".E<sol>%s"?>
=back
=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]