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

=head1 NAME

perldelta - what is new for perl v5.11.4

=head1 DESCRIPTION

This document describes differences between the 5.11.3 release and
the 5.11.4 release.

If you are upgrading from an earlier release such as 5.11.2, first read
L<perl5113delta>, which describes differences between 5.11.2 and
5.11.3.

=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

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

=over 4

=item New warning category C<illegalproto>

The two warnings :

  Illegal character in prototype for %s : %s
  Prototype after '%c' for %s : %s

have been moved from the C<syntax> top-level warnings category into a new
first-level category, C<illegalproto>. These two warnings are currently the
only ones emitted during parsing of an invalid/illegal prototype, so one
can now do

  no warnings 'illegalproto';

to suppress only those, but not other syntax-related warnings. Warnings where
prototypes are changed, ignored, or not met are still in the C<prototype>
category as before. (Matt S. Trout)

=item lvalue attribute ignored after the subroutine has been defined

This new warning is issued when one attempts to mark a subroutine as
lvalue after it has been defined.

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