[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.

=head2 Unicode properties

C<\p{XDigit}> now matches the same characters as C<\p{Hex_Digit}>.  This
means that in addition to the characters it currently matches,
C<[A-Fa-f0-9]>, it will also match their fullwidth equivalent forms, for
example U+FF10: FULLWIDTH DIGIT ZERO.

=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

The following items are now deprecated.

=over 4

=item C<< UNIVERSAL-E<gt>import() >>

The method C<< UNIVERSAL-E<gt>import() >> is now deprecated.
Attempting to pass import arguments to a C<use UNIVERSAL>
statement will result in a deprecation warning. (This is
a less noisy version of the full deprecation warning
added in 5.11.0.)

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