https://perl5.git.perl.org / perl5.git / blame
| Commit | Line | Data |
|---|---|---|
| 0302547a RS |
1 | =encoding utf8 |
| 2 | ||
| 3 | =head1 NAME | |
| 4 | ||
| 5 | [ this is a template for a new perldelta file. Any text flagged as XXX needs | |
| 6 | to be processed before release. ] | |
| 7 | ||
| 8 | perl5250delta - what is new for perl v5.25.0 | |
| 9 | ||
| 10 | =head1 DESCRIPTION | |
| 11 | ||
| 12 | This document describes differences between the 5.24.0 release and the 5.25.0 | |
| 13 | release. | |
| 14 | ||
| 15 | =head1 Known Problems | |
| 16 | ||
| 17 | =over 4 | |
| 18 | ||
| 19 | =item * | |
| 20 | ||
| 21 | Some modules have been broken by the L<context stack rework|/Internal Changes>. | |
| 22 | These modules were relying on non-guaranteed implementation details in perl. | |
| 23 | Their maintainers have been informed, and should contact perl5-porters for | |
| 24 | advice if needed. Below is a subset of these modules: | |
| 25 | ||
| 26 | =over 4 | |
| 27 | ||
| 28 | =item L<Algorithm::Permute> | |
| 29 | ||
| 30 | =item L<Coro> | |
| 31 | ||
| 32 | L<Coro> and perl v5.22.0 were already incompatible due to a change in the perl, | |
| 33 | and the reworking on the perl context stack creates a further incompatibility. | |
| 34 | perl5-porters has L<discussed the issue on the mailing | |
| 35 | list|http://www.nntp.perl.org/group/perl.perl5.porters/2016/05/msg236174.html>. | |
| 36 | ||
| 37 | =item L<Data::Alias> | |
| 38 | ||
| 39 | =item L<RPerl> | |
| 40 | ||
| 41 | =item L<Scope::Upper> | |
| 42 | ||
| 43 | =item L<TryCatch> | |
| 44 | ||
| 45 | =back | |
| 46 | ||
| 47 | =item * | |
| 48 | ||
| 49 | The module L<lexical::underscore> no longer works on perl v5.24.0, because perl | |
| 50 | no longer has a lexical C<$_>! | |
| 51 | ||
| 52 | =item * | |
| 53 | ||
| 54 | C<mod_perl> has been patched for compatibility for v5.22.0 and later but no | |
| 55 | release has been made. The relevant patch (and other changes) can be found in | |
| 56 | their source code repository, L<mirrored at | |
| 57 | GitHub|https://github.com/apache/mod_perl/commit/82827132efd3c2e25cc413c85af61bb63375da6e>. | |
| 58 | ||
| 59 | =back | |
| 60 | ||
| 61 | =head1 Acknowledgements | |
| 62 | ||
| 63 | XXX Generate this with: | |
| 64 | ||
| 65 | perl Porting/acknowledgements.pl v5.24.0..HEAD | |
| 66 | ||
| 67 | =head1 Reporting Bugs | |
| 68 | ||
| 69 | If you find what you think is a bug, you might check the articles recently | |
| 70 | posted to the comp.lang.perl.misc newsgroup and the perl bug database at | |
| 71 | L<https://rt.perl.org/> . There may also be information at | |
| 72 | L<http://www.perl.org/> , the Perl Home Page. | |
| 73 | ||
| 74 | If you believe you have an unreported bug, please run the L<perlbug> program | |
| 75 | included with your release. Be sure to trim your bug down to a tiny but | |
| 76 | sufficient test case. Your bug report, along with the output of C<perl -V>, | |
| 77 | will be sent off to perlbug@perl.org to be analysed by the Perl porting team. | |
| 78 | ||
| 79 | If the bug you are reporting has security implications which make it | |
| 80 | inappropriate to send to a publicly archived mailing list, then see | |
| 81 | L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION> | |
| 82 | for details of how to report the issue. | |
| 83 | ||
| 84 | =head1 SEE ALSO | |
| 85 | ||
| 86 | The F<Changes> file for an explanation of how to view exhaustive details on | |
| 87 | what changed. | |
| 88 | ||
| 89 | The F<INSTALL> file for how to build Perl. | |
| 90 | ||
| 91 | The F<README> file for general stuff. | |
| 92 | ||
| 93 | The F<Artistic> and F<Copying> files for copyright information. | |
| 94 | ||
| 95 | =cut |