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