GitHub's mirror is now at mirrors/perl, not github/perl
[p5sagit/p5-mst-13.2.git] / pod / perl5130delta.pod
CommitLineData
20d57231 1=encoding utf8
2
3=head1 NAME
4
5[ this is a template for a new perldelta file. Any text flagged as
6XXX needs to be processed before release. ]
7
8perldelta - what is new for perl v5.13.0
9
10=head1 DESCRIPTION
11
12This document describes differences between the 5.13.0 release and
13the 5.13.0 elease.
14
15If you are upgrading from an earlier release such as 5.10.0, first read
16L<perl5120delta>, which describes differences between 5.10.0 and
175.12.0.
18
19=head1 Notice
20
21XXX Any important notices here
22
23=head1 Incompatible Changes
24
25XXX For a release on a stable branch, this section aspires to be:
26
27 There are no changes intentionally incompatible with 5.XXX.XXX. If any
28 exist, they are bugs and reports are welcome.
29
30
31=head1 Core Enhancements
32
4207d19c 33=head2 "safe signals" optimization
34
da76b859 35Signal dispatch has been moved from the runloop into control ops. This should
36give a few percent speed increase, and eliminates almost all of the speed
37penalty caused by the introduction of "safe signals" in 5.8.0. Signals should
38still be dispatched within the same statement as they were previously - if
39this is not the case, or it is possible to create uninterruptable loops, this
40is a bug, and reports are encouraged of how to recreate such issues.
20d57231 41
3506daea 42=head2 Assignment to C<$0> sets the legacy process name with C<prctl()> on Linux
43
44On Linux the legacy process name will be set with L<prctl(2)>, in
45addition to altering the POSIX name via C<argv[0]> as perl has done
46since version 4.000. Now system utilities that read the legacy process
47name such as ps, top and killall will recognize the name you set when
48assigning to C<$0>. The string you supply will be cut off at 16 bytes,
49this is a limitation imposed by Linux.
50
20d57231 51=head1 New Platforms
52
53XXX List any platforms that this version of perl compiles on, that previous
54versions did not. These will either be enabled by new files in the F<hints/>
55directories, or new subdirectories and F<README> files at the top level of the
56source tree.
57
58=head1 Modules and Pragmata
59
60XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
61go here. If Module::CoreList is updated, generate an initial draft of the
62following sections using F<Porting/corelist-perldelta.pl>, which prints stub
63entries to STDOUT. Results can be pasted in place of the '=head2' entries
64below. A paragraph summary for important changes should then be added by hand.
65In an ideal world, dual-life modules would have a F<Changes> file that could be
66cribbed.
67
68=head2 New Modules and Pragmata
69
70=head2 Pragmata Changes
71
72=head2 Updated Modules
73
74=head2 Removed Modules and Pragmata
75
76=head1 Utility Changes
77
78XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
79here. Most of these are built within the directories F<utils> and F<x2p>.
80
81=over 4
82
83=item F<XXX>
84
85XXX
86
87=back
88
89=head1 New Documentation
90
91XXX Changes which create B<new> files in F<pod/> go here.
92
93=over 4
94
95=item L<XXX>
96
97XXX
98
99=back
100
101=head1 Changes to Existing Documentation
102
103XXX Changes which significantly change existing files in F<pod/> go here.
104Any changes to F<pod/perldiag.pod> should go in L</New or Changed Diagnostics>.
105
106
107=head1 Performance Enhancements
108
109XXX Changes which enhance performance without changing behaviour go here. There
110may well be none in a stable release.
111
112=over 4
113
114=item *
115
116XXX
117
118=back
119
120=head1 Installation and Configuration Improvements
121
122XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
123go here.
124
125=head2 Configuration improvements
126
127XXX
128
129=head2 Compilation improvements
130
131XXX
132
133=head2 Platform Specific Changes
134
135=over 4
136
137=item XXX-some-platform
138
139XXX
140
141=back
142
143=head1 Selected Bug Fixes
144
145XXX Important bug fixes in the core language are summarised here.
146Bug fixes in files in F<ext/> and F<lib/> are best summarised in
147L</Modules and Pragmata>.
148
149=over 4
150
151=item *
152
153XXX
154
155=back
156
157=head1 New or Changed Diagnostics
158
159XXX New or changed warnings emitted by the core's C<C> code go here.
160
161=over 4
162
163=item C<XXX>
164
165XXX
166
167=back
168
169=head1 Changed Internals
170
171XXX Changes which affect the interface available to C<XS> code go here.
172
173=over 4
174
175=item *
176
177XXX
178
179=back
180
181=head1 New Tests
182
183XXX Changes which create B<new> files in F<t/> go here. Changes to
184existing files in F<t/> aren't worth summarising, although the bugs that
185they represent may be.
186
187=over 4
188
189=item F<XXX>
190
191XXX
192
193=back
194
195=head1 Known Problems
196
197XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
198tests that had to be C<TODO>ed for the release would be noted here, unless
199they were specific to a particular platform (see below).
200
201This is a list of some significant unfixed bugs, which are regressions
202from either 5.XXX.XXX or 5.XXX.XXX.
203
204=over 4
205
206=item *
207
208XXX
209
210=back
211
212=head1 Deprecations
213
214XXX Add any new known deprecations here.
215
216The following items are now deprecated.
217
218=over 4
219
220=item *
221
222XXX
223
224=back
225
226=head1 Platform Specific Notes
227
228XXX Any changes specific to a particular platform. VMS and Win32 are the usual
229stars here. It's probably best to group changes under the same section layout
230as the main perldelta
231
232=head1 Obituary
233
234XXX If any significant core contributor has died, we've added a short obituary
235here.
236
237=head1 Acknowledgements
238
239XXX The list of people to thank goes here.
240
241
242=head1 Reporting Bugs
243
244If you find what you think is a bug, you might check the articles
245recently posted to the comp.lang.perl.misc newsgroup and the perl
246bug database at http://rt.perl.org/perlbug/ . There may also be
247information at http://www.perl.org/ , the Perl Home Page.
248
249If you believe you have an unreported bug, please run the B<perlbug>
250program included with your release. Be sure to trim your bug down
251to a tiny but sufficient test case. Your bug report, along with the
252output of C<perl -V>, will be sent off to perlbug@perl.org to be
253analysed by the Perl porting team.
254
255If the bug you are reporting has security implications, which make it
256inappropriate to send to a publicly archived mailing list, then please send
257it to perl5-security-report@perl.org. This points to a closed subscription
258unarchived mailing list, which includes all the core committers, who be able
259to help assess the impact of issues, figure out a resolution, and help
260co-ordinate the release of patches to mitigate or fix the problem across all
261platforms on which Perl is supported. Please only use this address for
262security issues in the Perl core, not for modules independently
263distributed on CPAN.
264
265=head1 SEE ALSO
266
267The F<Changes> file for an explanation of how to view exhaustive details
268on what changed.
269
270The F<INSTALL> file for how to build Perl.
271
272The F<README> file for general stuff.
273
274The F<Artistic> and F<Copying> files for copyright information.
275
276=cut