[p5sagit/p5-mst-13.2.git] / pod / perl5130delta.pod

=encoding utf8

=head1 NAME

[ this is a template for a new perldelta file. Any text flagged as
XXX needs to be processed before release. ]

perldelta - what is new for perl v5.13.0

=head1 DESCRIPTION

This document describes differences between the 5.13.0 release and
the 5.13.0 elease.

If you are upgrading from an earlier release such as 5.10.0, first read
L<perl5120delta>, which describes differences between 5.10.0 and
5.12.0.

=head1 Notice

XXX Any important notices here

=head1 Incompatible Changes

XXX For a release on a stable branch, this section aspires to be:

    There are no changes intentionally incompatible with 5.XXX.XXX. If any
    exist, they are bugs and reports are welcome.


=head1 Core Enhancements

Signal dispatch has been moved from the runloop into control ops. This should
give a few percent speed increase, and eliminates almost all of the speed
penalty caused by the introduction of "safe signals" in 5.8.0. Signals should
still be dispatched within the same statement as they were previously - if
this is not the case, or it is possible to create uninterruptable loops, this
is a bug, and reports are encouraged of how to recreate such issues.

=head1 New Platforms

XXX List any platforms that this version of perl compiles on, that previous
versions did not. These will either be enabled by new files in the F<hints/>
directories, or new subdirectories and F<README> files at the top level of the
source tree.

=head1 Modules and Pragmata

XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
go here.  If Module::CoreList is updated, generate an initial draft of the
following sections using F<Porting/corelist-perldelta.pl>, which prints stub
entries to STDOUT.  Results can be pasted in place of the '=head2' entries
below.  A paragraph summary for important changes should then be added by hand.
In an ideal world, dual-life modules would have a F<Changes> file that could be
cribbed.

=head2 New Modules and Pragmata

=head2 Pragmata Changes

=head2 Updated Modules

=head2 Removed Modules and Pragmata

=head1 Utility Changes

XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
here. Most of these are built within the directories F<utils> and F<x2p>.

=over 4

=item F<XXX>

XXX

=back

=head1 New Documentation

XXX Changes which create B<new> files in F<pod/> go here.

=over 4

=item L<XXX>

XXX

=back

=head1 Changes to Existing Documentation

XXX Changes which significantly change existing files in F<pod/> go here.
Any changes to F<pod/perldiag.pod> should go in L</New or Changed Diagnostics>.


=head1 Performance Enhancements

XXX Changes which enhance performance without changing behaviour go here. There
may well be none in a stable release.

=over 4

=item *

XXX

=back

=head1 Installation and Configuration Improvements

XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
go here.

=head2 Configuration improvements

XXX

=head2 Compilation improvements

XXX

=head2 Platform Specific Changes

=over 4

=item XXX-some-platform

XXX

=back

=head1 Selected Bug Fixes

XXX Important bug fixes in the core language are summarised here.
Bug fixes in files in F<ext/> and F<lib/> are best summarised in
L</Modules and Pragmata>.

=over 4

=item *

XXX

=back

=head1 New or Changed Diagnostics

XXX New or changed warnings emitted by the core's C<C> code go here.

=over 4

=item C<XXX>

XXX

=back

=head1 Changed Internals

XXX Changes which affect the interface available to C<XS> code go here.

=over 4

=item *

XXX

=back

=head1 New Tests

XXX Changes which create B<new> files in F<t/> go here. Changes to
existing files in F<t/> aren't worth summarising, although the bugs that
they represent may be.

=over 4

=item F<XXX>

XXX

=back

=head1 Known Problems

XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
tests that had to be C<TODO>ed for the release would be noted here, unless
they were specific to a particular platform (see below).

This is a list of some significant unfixed bugs, which are regressions
from either 5.XXX.XXX or 5.XXX.XXX.

=over 4

=item *

XXX

=back

=head1 Deprecations

XXX Add any new known deprecations here.

The following items are now deprecated.

=over 4

=item *

XXX

=back

=head1 Platform Specific Notes

XXX Any changes specific to a particular platform. VMS and Win32 are the usual
stars here. It's probably best to group changes under the same section layout
as the main perldelta

=head1 Obituary

XXX If any significant core contributor has died, we've added a short obituary
here.

=head1 Acknowledgements

XXX The list of people to thank goes here.


=head1 Reporting Bugs

If you find what you think is a bug, you might check the articles
recently posted to the comp.lang.perl.misc newsgroup and the perl
bug database at http://rt.perl.org/perlbug/ .  There may also be
information at http://www.perl.org/ , the Perl Home Page.

If you believe you have an unreported bug, please run the B<perlbug>
program included with your release.  Be sure to trim your bug down
to a tiny but sufficient test case.  Your bug report, along with the
output of C<perl -V>, will be sent off to perlbug@perl.org to be
analysed by the Perl porting team.

If the bug you are reporting has security implications, which make it
inappropriate to send to a publicly archived mailing list, then please send
it to perl5-security-report@perl.org. This points to a closed subscription
unarchived mailing list, which includes all the core committers, who be able
to help assess the impact of issues, figure out a resolution, and help
co-ordinate the release of patches to mitigate or fix the problem across all
platforms on which Perl is supported. Please only use this address for
security issues in the Perl core, not for modules independently
distributed on CPAN.

=head1 SEE ALSO

The F<Changes> file for an explanation of how to view exhaustive details
on what changed.

The F<INSTALL> file for how to build Perl.

The F<README> file for general stuff.

The F<Artistic> and F<Copying> files for copyright information.

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