This is a live mirror of the Perl 5 development currently hosted at https://github.com/perl/perl5
Note in delta an incompatibility for \cX
[perl5.git] / pod / perl5131delta.pod
CommitLineData
d4438f94
LB
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.1
9
10=head1 DESCRIPTION
11
12This document describes differences between the 5.13.0 release and
13the 5.13.1 release.
14
15If you are upgrading from an earlier release such as 5.10, first read
16L<perl5120delta>, which describes differences between 5.10 and
175.12.
18
19=head1 Notice
20
21XXX Any important notices here
22
23=head1 Incompatible Changes
24
df5278db 25=head2 "C<\cI<X>>"
d4438f94 26
df5278db
KW
27The backslash-c construct was designed as a way of specifying
28non-printable characters, but there were no restrictions (on ASCII
29platforms) on what the character following the C<c> could be. Now, that
30character must be one of the ASCII characters.
d4438f94
LB
31
32=head1 Core Enhancements
33
34XXX New core language features go here. Summarise user-visible core language
35enhancements. Particularly prominent performance optimisations could go
36here, but most should go in the L</Performance Enhancements> section.
37
38=head1 New Platforms
39
40XXX List any platforms that this version of perl compiles on, that previous
41versions did not. These will either be enabled by new files in the F<hints/>
42directories, or new subdirectories and F<README> files at the top level of the
43source tree.
44
45=head1 Modules and Pragmata
46
47XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
48go here. If Module::CoreList is updated, generate an initial draft of the
49following sections using F<Porting/corelist-perldelta.pl>, which prints stub
50entries to STDOUT. Results can be pasted in place of the '=head2' entries
51below. A paragraph summary for important changes should then be added by hand.
52In an ideal world, dual-life modules would have a F<Changes> file that could be
53cribbed.
54
55=head2 New Modules and Pragmata
56
57=head2 Pragmata Changes
58
59=head2 Updated Modules
60
61=head2 Removed Modules and Pragmata
62
63=head1 Utility Changes
64
65XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
66here. Most of these are built within the directories F<utils> and F<x2p>.
67
68=over 4
69
70=item F<XXX>
71
72XXX
73
74=back
75
76=head1 New Documentation
77
78XXX Changes which create B<new> files in F<pod/> go here.
79
80=over 4
81
82=item L<XXX>
83
84XXX
85
86=back
87
88=head1 Changes to Existing Documentation
89
90XXX Changes which significantly change existing files in F<pod/> go here.
91Any changes to F<pod/perldiag.pod> should go in L</New or Changed Diagnostics>.
92
93
94=head1 Performance Enhancements
95
96XXX Changes which enhance performance without changing behaviour go here. There
97may well be none in a stable release.
98
99=over 4
100
101=item *
102
103XXX
104
105=back
106
107=head1 Installation and Configuration Improvements
108
109XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
110go here.
111
112=head2 Configuration improvements
113
114XXX
115
116=head2 Compilation improvements
117
118XXX
119
120=head2 Platform Specific Changes
121
122=over 4
123
124=item XXX-some-platform
125
126XXX
127
128=back
129
130=head1 Selected Bug Fixes
131
132XXX Important bug fixes in the core language are summarised here.
133Bug fixes in files in F<ext/> and F<lib/> are best summarised in
134L</Modules and Pragmata>.
135
136=over 4
137
138=item *
139
140XXX
141
142=back
143
144=head1 New or Changed Diagnostics
145
146XXX New or changed warnings emitted by the core's C<C> code go here.
147
148=over 4
149
150=item C<XXX>
151
152XXX
153
154=back
155
156=head1 Changed Internals
157
158XXX Changes which affect the interface available to C<XS> code go here.
159
160=over 4
161
162=item *
163
164XXX
165
166=back
167
168=head1 New Tests
169
170XXX Changes which create B<new> files in F<t/> go here. Changes to
171existing files in F<t/> aren't worth summarising, although the bugs that
172they represent may be.
173
174=over 4
175
176=item F<XXX>
177
178XXX
179
180=back
181
182=head1 Known Problems
183
184XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
185tests that had to be C<TODO>ed for the release would be noted here, unless
186they were specific to a particular platform (see below).
187
188This is a list of some significant unfixed bugs, which are regressions
189from either 5.XXX.XXX or 5.XXX.XXX.
190
191=over 4
192
193=item *
194
195XXX
196
197=back
198
199=head1 Deprecations
200
201XXX Add any new known deprecations here.
202
203The following items are now deprecated.
204
205=over 4
206
207=item *
208
209XXX
210
211=back
212
213=head1 Platform Specific Notes
214
215XXX Any changes specific to a particular platform. VMS and Win32 are the usual
216stars here. It's probably best to group changes under the same section layout
217as the main perldelta
218
219=head1 Obituary
220
221XXX If any significant core contributor has died, we've added a short obituary
222here.
223
224=head1 Acknowledgements
225
226XXX The list of people to thank goes here.
227
228
229=head1 Reporting Bugs
230
231If you find what you think is a bug, you might check the articles
232recently posted to the comp.lang.perl.misc newsgroup and the perl
233bug database at http://rt.perl.org/perlbug/ . There may also be
234information at http://www.perl.org/ , the Perl Home Page.
235
236If you believe you have an unreported bug, please run the B<perlbug>
237program included with your release. Be sure to trim your bug down
238to a tiny but sufficient test case. Your bug report, along with the
239output of C<perl -V>, will be sent off to perlbug@perl.org to be
240analysed by the Perl porting team.
241
242If the bug you are reporting has security implications, which make it
243inappropriate to send to a publicly archived mailing list, then please send
244it to perl5-security-report@perl.org. This points to a closed subscription
245unarchived mailing list, which includes all the core committers, who be able
246to help assess the impact of issues, figure out a resolution, and help
247co-ordinate the release of patches to mitigate or fix the problem across all
248platforms on which Perl is supported. Please only use this address for
249security issues in the Perl core, not for modules independently
250distributed on CPAN.
251
252=head1 SEE ALSO
253
254The F<Changes> file for an explanation of how to view exhaustive details
255on what changed.
256
257The F<INSTALL> file for how to build Perl.
258
259The F<README> file for general stuff.
260
261The F<Artistic> and F<Copying> files for copyright information.
262
263=cut