[perl5.git] / pod / perl5131delta.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.1

=head1 DESCRIPTION

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

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

=head1 Notice

XXX Any important notices here

=head1 Incompatible Changes

=head2 "C<\cI<X>>"

The backslash-c construct was designed as a way of specifying
non-printable characters, but there were no restrictions (on ASCII
platforms) on what the character following the C<c> could be.  Now, that
character must be one of the ASCII characters.

=head2 localised tied hashes, arrays and scalars are no longed tied

In the following:

    tie @a, ...;
    {
	local @a;
	# here, @a is a now a new, untied array
    }
    # here, @a refers again to the old, tied array

The new local array used to be made tied too, which was fairly pointless,
and has now been fixed. This fix could however potentially cause a change
in behaviour of some code.

=head1 Core Enhancements

XXX New core language features go here. Summarise user-visible core language
enhancements. Particularly prominent performance optimisations could go
here, but most should go in the L</Performance Enhancements> section.

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