+=encoding utf8
+
=head1 NAME
-perldelta - what is new for perl v5.9.0
+[ 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.6
=head1 DESCRIPTION
-This document describes differences between the 5.8.0 release and
-the 5.9.0 release.
+This document describes differences between the 5.13.5 release and
+the 5.13.6 release.
-=head1 Incompatible Changes
+If you are upgrading from an earlier release such as 5.13.4, first read
+L<perl5135delta>, which describes differences between 5.13.4 and
+5.13.5.
-=head2 Hash Randomisation
-
-Mainly due to security reasons, the "random ordering" of hashes
-has been made even more random. Previously while the order of hash
-elements from keys(), values(), and each() was essentially random,
-it was still repeatable. Now, however, the order varies between
-different runs of Perl.
+=head1 Notice
-B<Perl has never guaranteed any ordering of the hash keys>, and the
-ordering has already changed several times during the lifetime of
-Perl 5. Also, the ordering of hash keys has always been, and
-continues to be, affected by the insertion order.
+XXX Any important notices here
-The added randomness may affect applications.
+=head1 Core Enhancements
-One possible scenario is when output of an application has included
-hash data. For example, if you have used the Data::Dumper module to
-dump data into different files, and then compared the files to see
-whether the data has changed, now you will have false positives since
-the order in which hashes are dumped will vary. In general the cure
-is to sort the keys (or the values); in particular for Data::Dumper to
-use the C<Sortkeys> option. If some particular order is really
-important, use tied hashes: for example the Tie::IxHash module
-which by default preserves the order in which the hash elements
-were added.
+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.
-More subtle problem is reliance on the order of "global destruction".
-That is what happens at the end of execution: Perl destroys all data
-structures, including user data. If your destructors (the DESTROY
-subroutines) have assumed any particular ordering to the global
-destruction, there might be problems ahead. For example, in a
-destructor of one object you cannot assume that objects of any other
-class are still available, unless you hold a reference to them.
-If the environment variable PERL_DESTRUCT_LEVEL is set to a non-zero
-value, or if Perl is exiting a spawned thread, it will also destruct
-the ordinary references and the symbol tables that are no longer in use.
-You can't call a class method or an ordinary function on a class that
-has been collected that way.
+[ List each enhancement as a =head2 entry ]
-The hash randomisation is certain to reveal hidden assumptions about
-some particular ordering of hash elements, and outright bugs: it
-revealed a few bugs in the Perl core and core modules.
+=head2 C<(?^...)> regex construct added to signify default modifiers
-To disable the hash randomisation in runtime, set the environment
-variable PERL_HASH_SEED to 0 (zero) before running Perl (for more
-information see L<perlrun/PERL_HASH_SEED>), or to disable the feature
-completely in compile time, compile with C<-DNO_HASH_SEED> (see F<INSTALL>).
+A caret (also called a "cirumflex accent") C<"^"> immediately following
+a C<"(?"> in a regular expression now means that the subexpression is to
+not inherit the surrounding modifiers such as C</i>, but to revert to the
+Perl defaults. Any modifiers following the caret override the defaults.
-See L<perlsec/"Algorithmic Complexity Attacks"> for the original
-rationale behind this change.
+The stringification of regular expressions now uses this notation. The
+main purpose of this is to allow tests that rely on the stringification
+to not have to change when new modifiers are added. See
+L<perlre/Extended Patterns>.
-=head2 UTF-8 On Filehandles No Longer Activated By Locale
+=head2 C<"d">, C<"l">, and C<"u"> regex modifiers added
-In Perl 5.8.0 all filehandles, including the standard filehandles,
-were implicitly set to be in Unicode UTF-8 if the locale settings
-indicated the use of UTF-8. This feature caused too many problems,
-so the feature was turned off and redesigned: see L</"Core Enhancements">.
+These modifiers are currently only available within a C<(?...)> construct.
-=head2 Single-number v-strings are no longer v-strings before "=>"
+The C<"l"> modifier says to compile the regular expression as if it were
+in the scope of C<use locale>, even if it is not.
-The version strings or v-strings (see L<perldata/"Version Strings">)
-feature introduced in Perl 5.6.0 has been a source of some confusion--
-especially when the user did not want to use it, but Perl thought it
-knew better. Especially troublesome has been the feature that before
-a "=>" a version string (a "v" followed by digits) has been interpreted
-as a v-string instead of a string literal. In other words:
+The C<"u"> modifier currently does nothing.
- %h = ( v65 => 42 );
+The C<"d"> modifier is used in the scope of C<use locale> to compile the
+regular expression as if it were not in that scope.
+See L<perlre/(?dlupimsx-imsx)>.
-has meant since Perl 5.6.0
+=head2 C<\N{...}> now handles Unicode named character sequences
- %h = ( 'A' => 42 );
+Unicode has a number of named character sequences, in which particular sequences
+of code points are given names. C<\N{...}> now recognizes these.
+See L<charnames>.
-(at least in platforms of ASCII progeny) Perl 5.8.1 restored the
-more natural interpretation
+=head2 New function C<charnames::string_vianame()>
- %h = ( 'v65' => 42 );
+This function is a run-time version of C<\N{...}>, returning the string
+of characters whose Unicode name is its parameter. It can handle
+Unicode named character sequences, whereas the pre-existing
+C<charnames::vianame()> cannot, as the latter returns a single code
+point.
+See L<charnames>.
-The multi-number v-strings like v65.66 and 65.66.67 still continue to
-be v-strings in Perl 5.8.
+=head2 Custom per-subroutine check hooks
-=head2 (Win32) The -C Switch Has Been Repurposed
+XS code in an extension module can now annotate a subroutine (whether
+implemented in XS or in Perl) so that nominated XS code will be called
+at compile time (specifically as part of op checking) to change the op
+tree of that subroutine. The compile-time check function (supplied by
+the extension module) can implement argument processing that can't be
+expressed as a prototype, generate customised compile-time warnings,
+perform constant folding for a pure function, inline a subroutine
+consisting of sufficiently simple ops, replace the whole call with a
+custom op, and so on. This was previously all possible by hooking the
+C<entersub> op checker, but the new mechanism makes it easy to tie the
+hook to a specific subroutine. See L<perlapi/cv_set_call_checker>.
-The -C switch has changed in an incompatible way. The old semantics
-of this switch only made sense in Win32 and only in the "use utf8"
-universe in 5.6.x releases, and do not make sense for the Unicode
-implementation in 5.8.0. Since this switch could not have been used
-by anyone, it has been repurposed. The behavior that this switch
-enabled in 5.6.x releases may be supported in a transparent,
-data-dependent fashion in a future release.
+To help in writing custom check hooks, several subtasks within standard
+C<entersub> op checking have been separated out and exposed in the API.
-For the new life of this switch, see L<"UTF-8 no longer default under
-UTF-8 locales">, and L<perlrun/-C>.
+=head1 Security
-=head2 (Win32) The /d Switch Of cmd.exe
+XXX Any security-related notices go here. In particular, any security
+vulnerabilities closed should be noted here rather than in the
+L</Selected Bug Fixes> section.
-Since version 5.8.1, perl uses the /d switch when running the cmd.exe shell
-internally for system(), backticks, and when opening pipes to external
-programs. The extra switch disables the execution of AutoRun commands
-from the registry, which is generally considered undesirable when
-running external programs. If you wish to retain compatibility with
-the older behavior, set PERL5SHELL in your environment to C<cmd /x/c>.
-
-=head2 The C<$*> variable has been removed
-
-C<$*>, which was deprecated in favor of the C</s> and C</m> regexp
-modifiers, has been removed.
+[ List each security issue as a =head2 entry ]
-=head1 Core Enhancements
+=head1 Incompatible Changes
-=head2 Assertions
+=head2 Stringification of regexes has changed
-Perl 5.9.0 has experimental support for assertions. Note that hhe user
-interface is not fully stabilized yet, and it may change until the 5.10.0
-release. A new command-line switch, B<-A>, is used to activate
-assertions, which are declared with the C<assertions> pragma. See
-L<assertions>.
+Default regular expression modifiers are now notated by using
+C<(?^...)>. Code relying on the old stringification will fail. The
+purpose of this is so that when new modifiers are added, such code will
+not have to change (after this one time), as the stringification will
+automatically incorporate the new modifiers.
-=head2 Defined-or operators
+Code that needs to work properly with both old- and new-style regexes
+can avoid the whole issue by using (for Perls since 5.9.5):
-A new operator C<//> (defined-or) has been implemented.
-The following statement:
+ use re qw(regexp_pattern);
+ my ($pat, $mods) = regexp_pattern($re_ref);
- $a // $b
+where C<$re_ref> is a reference to a compiled regular expression. Upon
+return, C<$mods> will be a string containing all the non-default
+modifiers used when the regular expression was compiled, and C<$pattern>
+the actual pattern.
-is merely equivalent to
+If the actual stringification is important, or older Perls need to be
+supported, you can use something like the following:
- defined $a ? $a : $b
+ # Accept both old and new-style stringification
+ my $modifiers = (qr/foobar/ =~ /\Q(?^/) ? '^' : '-xism';
-and
+And then use C<$modifiers> instead of C<-xism>.
- $c //= $d;
+=head2 Regular expressions retain their localeness when interpolated
-can be used instead of
+Regular expressions compiled under C<"use locale"> now retain this when
+interpolated into a new regular expression compiled outside a
+C<"use locale">, and vice-versa.
- $c = $d unless defined $c;
+Previously, a regular expression interpolated into another one inherited
+the localeness of the surrounding one, losing whatever state it
+originally had. This is considered a bug fix, but may trip up code that
+has come to rely on the incorrect behavior.
-This operator has the same precedence and associativity as C<||>.
-It has a low-precedence counterpart, C<err>, which has the same precedence
-and associativity as C<or>. Special care has been taken to ensure that
-those operators Do What You Mean while not breaking old code, but some
-edge cases involving the empty regular expression may now parse
-differently. See L<perlop> for details.
+=head2 Directory handles not copied to threads
-=head2 UTF-8 no longer default under UTF-8 locales
+On systems that do not have a C<fchdir> function, newly-created threads no
+longer inherit directory handles from their parent threads. Such programs
+would probably have crashed anyway
+L<[perl #75154]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=75154>.
-In Perl 5.8.0 many Unicode features were introduced. One of them
-was found to be of more nuisance than benefit: the automagic
-(and silent) "UTF-8-ification" of filehandles, including the
-standard filehandles, if the user's locale settings indicated
-use of UTF-8.
+=head2 Negation treats strings differently from before
-For example, if you had C<en_US.UTF-8> as your locale, your STDIN and
-STDOUT were automatically "UTF-8", in other words an implicit
-binmode(..., ":utf8") was made. This meant that trying to print, say,
-chr(0xff), ended up printing the bytes 0xc3 0xbf. Hardly what
-you had in mind unless you were aware of this feature of Perl 5.8.0.
-The problem is that the vast majority of people weren't: for example
-in RedHat releases 8 and 9 the B<default> locale setting is UTF-8, so
-all RedHat users got UTF-8 filehandles, whether they wanted it or not.
-The pain was intensified by the Unicode implementation of Perl 5.8.0
-(still) having nasty bugs, especially related to the use of s/// and
-tr///. (Bugs that have been fixed in 5.8.1)
+The unary negation operator C<-> now treats strings that look like numbers
+as numbers
+L<[perl #57706]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=57706>.
-Therefore a decision was made to backtrack the feature and change it
-from implicit silent default to explicit conscious option. The new
-Perl command line option C<-C> and its counterpart environment
-variable PERL_UNICODE can now be used to control how Perl and Unicode
-interact at interfaces like I/O and for example the command line
-arguments. See L<perlrun/-C> and L<perlrun/PERL_UNICODE> for more
-information.
+=head2 Negative zero
-=head2 Unsafe signals again available
+Negative zero (-0.0), when converted to a string, now becomes "0" on all
+platforms. It used to become "-0" on some, but "0" on others.
-In Perl 5.8.0 the so-called "safe signals" were introduced. This
-means that Perl no longer handles signals immediately but instead
-"between opcodes", when it is safe to do so. The earlier immediate
-handling easily could corrupt the internal state of Perl, resulting
-in mysterious crashes.
+If you still need to determine whether a zero is negative, use
+C<sprintf("%g", $zero) =~ /^-/> or the L<Data::Float> module on CPAN.
-However, the new safer model has its problems too. Because now an
-opcode, a basic unit of Perl execution, is never interrupted but
-instead let to run to completion, certain operations that can take a
-long time now really do take a long time. For example, certain
-network operations have their own blocking and timeout mechanisms, and
-being able to interrupt them immediately would be nice.
+=head1 Deprecations
-Therefore perl 5.8.1 introduced a "backdoor" to restore the pre-5.8.0
-(pre-5.7.3, really) signal behaviour. Just set the environment variable
-PERL_SIGNALS to C<unsafe>, and the old immediate (and unsafe)
-signal handling behaviour returns. See L<perlrun/PERL_SIGNALS>
-and L<perlipc/"Deferred Signals (Safe Signals)">.
+XXX Any deprecated features, syntax, modules etc. should be listed here.
+In particular, deprecated modules should be listed here even if they are
+listed as an updated module in the L</Modules and Pragmata> section.
-In completely unrelated news, you can now use safe signals with
-POSIX::SigAction. See L<POSIX/POSIX::SigAction>.
+[ List each deprecation as a =head2 entry ]
-=head2 Tied Arrays with Negative Array Indices
+=head1 Performance Enhancements
-Formerly, the indices passed to C<FETCH>, C<STORE>, C<EXISTS>, and
-C<DELETE> methods in tied array class were always non-negative. If
-the actual argument was negative, Perl would call FETCHSIZE implicitly
-and add the result to the index before passing the result to the tied
-array method. This behaviour is now optional. If the tied array class
-contains a package variable named C<$NEGATIVE_INDICES> which is set to
-a true value, negative values will be passed to C<FETCH>, C<STORE>,
-C<EXISTS>, and C<DELETE> unchanged.
+XXX Changes which enhance performance without changing behaviour go here. There
+may well be none in a stable release.
-=head2 Tied hashes in scalar context
+[ List each enhancement as a =item entry ]
-As of perl 5.8.2, tied hashes did not return anything useful in scalar
-context, for example when used as boolean tests:
+=over 4
- if (%tied_hash) { ... }
+=item *
-The old nonsensical behaviour was always to return false,
-regardless of whether the hash is empty or has elements.
+XXX
-There is now an interface for the implementors of tied hashes to implement
-the behaviour of a hash in scalar context, via the SCALAR method (see
-L<perltie>). Without a SCALAR method, perl will try to guess whether
-the hash is empty, by testing if it's inside an iteration (in this case
-it can't be empty) or by calling FIRSTKEY.
+=back
-=head2 local ${$x}
+=head1 Modules and Pragmata
-The syntaxes
+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.
- local ${$x}
- local @{$x}
- local %{$x}
+[ Within each section, list entries as a =item entry ]
-now do localise variables, given that the $x is a valid variable name.
+=head2 New Modules and Pragmata
-=head2 Unicode Character Database 4.0.0
+=over 4
-The copy of the Unicode Character Database included in Perl 5.8 has
-been updated to 4.0.0 from 3.2.0. This means for example that the
-Unicode character properties are as in Unicode 4.0.0.
+=item *
-=head2 Miscellaneous Enhancements
+XXX
-C<unpack()> now defaults to unpacking the C<$_>.
+=back
-C<map> in void context is no longer expensive. C<map> is now context
-aware, and will not construct a list if called in void context.
+=head2 Updated Modules and Pragmata
-If a socket gets closed by the server while printing to it, the client
-now gets a SIGPIPE. While this new feature was not planned, it fell
-naturally out of PerlIO changes, and is to be considered an accidental
-feature.
+=over 4
-PerlIO::get_layers(FH) returns the names of the PerlIO layers
-active on a filehandle.
+=item *
-PerlIO::via layers can now have an optional UTF8 method to
-indicate whether the layer wants to "auto-:utf8" the stream.
+C<Archive::Extract> has been upgraded from version 0.42 to 0.44
-utf8::is_utf8() has been added as a quick way to test whether
-a scalar is encoded internally in UTF-8 (Unicode).
+=item *
-=head1 Modules and Pragmata
+C<Carp> has been upgraded from version 1.18 to 1.19.
-=head2 Updated Modules And Pragmata
+It no longer autovivifies the C<*CORE::GLOBAL::caller> glob, something it
+started doing in 1.18, which was released with perl 5.13.4
+L<[perl #78082]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=78082>
-The following modules and pragmata have been updated since Perl 5.8.0:
+=item *
-=over 4
+C<Data::Dumper> has been upgraded from version 2.128 to 2.129.
-=item base
+C<Dumpxs> no longer crashes with globs returned by C<*$io_ref>
+L<[perl #72332]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=72332>.
-=item B::Bytecode
+=item *
-In much better shape than it used to be. Still far from perfect, but
-maybe worth a try.
+C<Digest::MD5> has been upgraded from version 2.40 to 2.51.
-=item B::Concise
+It is now safe to use this module in combination with threads.
-=item B::Deparse
+=item *
-=item Benchmark
+C<File::DosGlob> has been upgraded from version 1.02 to 1.03.
-An optional feature, C<:hireswallclock>, now allows for high
-resolution wall clock times (uses Time::HiRes).
+It allows patterns containing literal parentheses (they no longer need to
+be escaped). On Windows, it no longer adds an extra F<./> to the file names
+returned when the pattern is a relative glob with a drive specification,
+like F<c:*.pl>
+L<[perl #71712]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71712>.
-=item ByteLoader
+=item *
-See B::Bytecode.
+C<File::Find> has been upgraded from version 1.17 to 1.18.
-=item bytes
+It improves handling of backslashes on Windows, so that paths such as
+F<c:\dir\/file> are no longer generated
+L<[perl #71710]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71710>.
-Now has bytes::substr.
+=item *
-=item CGI
+C<if> has been upgraded from version 0.05 to 0.06
-=item charnames
+=item *
-One can now have custom character name aliases.
+C<IPC::Open3> has been upgraded from version 1.06 to 1.07.
-=item CPAN
+The internal C<xclose> routine now knows how to handle file descriptors, as
+documented, so duplicating STDIN in a child process using its file
+descriptor now works
+L<[perl #76474]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71710>.
-There is now a simple command line frontend to the CPAN.pm
-module called F<cpan>.
+=item *
-=item Data::Dumper
+C<Locale::Maketext> has been upgraded from version 1.15 to 1.16.
-A new option, Pair, allows choosing the separator between hash keys
-and values.
+It fixes an infinite loop in C<Locale::Maketext::Guts::_compile()> when
+working with tainted values
+(L<CPAN RT #40727|https://rt.cpan.org/Public/Bug/Display.html?id=40727>).
-=item DB_File
+C<< ->maketext >> calls will now backup and restore C<$@> so that error
+messages are not supressed
+(L<CPAN RT #34182|https://rt.cpan.org/Public/Bug/Display.html?id=34182>).
-=item Devel::PPPort
+=item *
-=item Digest::MD5
+C<Math::BigInt> has been upgraded from version 1.95 to 1.97.
-=item Encode
+This prevents C<sqrt($int)> from crashing under C<use bigrat;>
+L<[perl #73534]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=73534>.
-Significant updates on the encoding pragma functionality
-(tr/// and the DATA filehandle, formats).
+=item *
-If a filehandle has been marked as to have an encoding, unmappable
-characters are detected already during input, not later (when the
-corrupted data is being used).
+C<NEXT> has been upgraded from version 0.64 to 0.65.
-The ISO 8859-6 conversion table has been corrected (the 0x30..0x39
-erroneously mapped to U+0660..U+0669, instead of U+0030..U+0039). The
-GSM 03.38 conversion did not handle escape sequences correctly. The
-UTF-7 encoding has been added (making Encode feature-complete with
-Unicode::String).
+=item *
-=item fields
+C<overload> has been upgraded from version 1.10 to 1.11.
-=item libnet
+C<overload::Method> can now handle subroutines that are themselves blessed
+into overloaded classes
+L<[perl #71998]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71998>.
-=item Math::BigInt
+=item *
-A lot of bugs have been fixed since v1.60, the version included in Perl
-v5.8.0. Especially noteworthy are the bug in Calc that caused div and mod to
-fail for some large values, and the fixes to the handling of bad inputs.
+C<PathTools> has been upgraded from version 3.31_01 to 3.34.
-Some new features were added, e.g. the broot() method, you can now pass
-parameters to config() to change some settings at runtime, and it is now
-possible to trap the creation of NaN and infinity.
+=item *
-As usual, some optimizations took place and made the math overall a tad
-faster. In some cases, quite a lot faster, actually. Especially alternative
-libraries like Math::BigInt::GMP benefit from this. In addition, a lot of the
-quite clunky routines like fsqrt() and flog() are now much much faster.
+C<sigtrap> has been upgraded from version 1.04 to 1.05.
-=item MIME::Base64
+It no longer tries to modify read-only arguments when generating a
+backtrace
+L<[perl #72340]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=72340>.
-=item NEXT
+=item *
-Diamond inheritance now works.
+C<threads> has been upgraded from version 1.77_03 to 1.81
-=item Net::Ping
+=item *
-=item PerlIO::scalar
+C<threads::shared> has been upgrade from version 1.33_03 to 1.34
-Reading from non-string scalars (like the special variables, see
-L<perlvar>) now works.
+=item *
-=item podlators
+C<Unicode::Collate> has been upgraded from version 0.59 to 0.62
-=item Pod::LaTeX
+U::C::Locale newly supports locales: ar, de__phonebook, hu, hy, nso, om,
+tn, vi, hr, ig, sq, se to and uk
-=item PodParsers
+=item *
-=item Pod::Perldoc
+C<Unicode::Normalize> has been upgraded from version 1.06 to 1.07
-Complete rewrite. As a side-effect, no longer refuses to startup when
-run by root.
+=back
-=item Scalar::Util
+=head2 Removed Modules and Pragmata
-New utilities: refaddr, isvstring, looks_like_number, set_prototype.
+=over 4
-=item Storable
+=item *
-Can now store code references (via B::Deparse, so not foolproof).
+XXX
-=item strict
+=back
-Earlier versions of the strict pragma did not check the parameters
-implicitly passed to its "import" (use) and "unimport" (no) routine.
-This caused the false idiom such as:
+=head1 Documentation
- use strict qw(@ISA);
- @ISA = qw(Foo);
+XXX Changes to files in F<pod/> go here. Consider grouping entries by
+file and be sure to link to the appropriate page, e.g. L<perlfunc>.
-This however (probably) raised the false expectation that the strict
-refs, vars and subs were being enforced (and that @ISA was somehow
-"declared"). But the strict refs, vars, and subs are B<not> enforced
-when using this false idiom.
+=head2 New Documentation
-Starting from Perl 5.8.1, the above B<will> cause an error to be
-raised. This may cause programs which used to execute seemingly
-correctly without warnings and errors to fail when run under 5.8.1.
-This happens because
+XXX Changes which create B<new> files in F<pod/> go here.
- use strict qw(@ISA);
+=head3 L<XXX>
-will now fail with the error:
+XXX Description of the purpose of the new file here
- Unknown 'strict' tag(s) '@ISA'
+=head2 Changes to Existing Documentation
-The remedy to this problem is to replace this code with the correct idiom:
+XXX Changes which significantly change existing files in F<pod/> go here.
+However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
+section.
- use strict;
- use vars qw(@ISA);
- @ISA = qw(Foo);
+=head3 L<XXX>
-=item Term::ANSIcolor
+=over 4
-=item Test::Harness
+=item *
-Now much more picky about extra or missing output from test scripts.
+The documentation for the C<SvTRUE> macro was simply wrong in stating that
+get-magic is not processed. It has been corrected.
-=item Test::More
+=back
-=item Test::Simple
+=head1 Diagnostics
-=item Text::Balanced
+The following additions or changes have been made to diagnostic output,
+including warnings and fatal error messages. For the complete list of
+diagnostic messages, see L<perldiag>.
-=item Time::HiRes
+XXX New or changed warnings emitted by the core's C<C> code go here. Also
+include any changes in L<perldiag> that reconcile it to the C<C> code.
-Use of nanosleep(), if available, allows mixing subsecond sleeps with
-alarms.
+[ Within each section, list entries as a =item entry ]
-=item threads
+=head2 New Diagnostics
-Several fixes, for example for join() problems and memory
-leaks. In some platforms (like Linux) that use glibc the minimum memory
-footprint of one ithread has been reduced by several hundred kilobytes.
+XXX Newly added diagnostic messages go here
-=item threads::shared
+=over 4
-Many memory leaks have been fixed.
+=item *
-=item Unicode::Collate
+XXX
-=item Unicode::Normalize
+=back
-=item Win32::GetFolderPath
+=head2 Changes to Existing Diagnostics
-=item Win32::GetOSVersion
+XXX Changes (i.e. rewording) of diagnostic messages go here
-Now returns extra information.
+=over 4
-=back
+=item *
-=head1 Utility Changes
+The 'Layer does not match this perl' error message has been replaced with
+these more helpful messages:
+
+=over 4
-The C<h2xs> utility now produces a more modern layout:
-F<Foo-Bar/lib/Foo/Bar.pm> instead of F<Foo/Bar/Bar.pm>.
-Also, the boilerplate test is now called F<t/Foo-Bar.t>
-instead of F<t/1.t>.
+=item *
-The Perl debugger (F<lib/perl5db.pl>) has now been extensively
-documented and bugs found while documenting have been fixed.
+PerlIO layer function table size (%d) does not match size expected by this
+perl (%d)
-C<perldoc> has been rewritten from scratch to be more robust and
-featureful.
+=item *
-C<perlcc -B> works now at least somewhat better, while C<perlcc -c>
-is rather more broken. (The Perl compiler suite as a whole continues
-to be experimental.)
+PerlIO layer instance size (%d) does not match size expected by this perl
+(%d)
-C<find2perl> now assumes C<-print> as a default action. It needed to be
-specified explicitly.
+=back
-=head1 New Documentation
+L<[perl #73754]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=73754>
-perl573delta has been added to list the differences between the
-(now quite obsolete) development releases 5.7.2 and 5.7.3.
+=back
-perl58delta and perl581delta have been added: these are the perldeltas
-of 5.8.0 and 5.8.1, detailing the differences respectively between
-5.6.0 and 5.8.0, and between 5.8.0 and 5.8.1.
+=head1 Utility Changes
-perlartistic has been added: it is the Artistic License in pod format,
-making it easier for modules to refer to it.
+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>.
-perlcheat has been added: it is a Perl cheat sheet.
+[ List utility changes as a =head3 entry for each utility and =item
+entries for each change
+Use L<XXX> with program names to get proper documentation linking. ]
-perlgpl has been added: it is the GNU General Public License in pod
-format, making it easier for modules to refer to it.
+=head3 L<XXX>
-perlmacosx has been added to tell about the installation and use
-of Perl in Mac OS X.
+=over 4
-perlos400 has been added to tell about the installation and use
-of Perl in OS/400 PASE.
+=item *
-perlreref has been added: it is a regular expressions quick reference.
+XXX
-=head1 Performance Enhancements
+=back
-=head1 Installation and Configuration Improvements
+=head1 Configuration and Compilation
-The UNIX standard Perl location, F</usr/bin/perl>, is no longer
-overwritten by default if it exists. This change was very prudent
-because so many UNIX vendors already provide a F</usr/bin/perl>,
-but simultaneously many system utilities may depend on that
-exact version of Perl, so better not to overwrite it.
+XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
+go here. Any other changes to the Perl build process should be listed here.
+However, any platform-specific changes should be listed in the
+L</Platform Support> section, instead.
-One can now specify installation directories for site and vendor man
-and HTML pages, and site and vendor scripts. See F<INSTALL>.
+[ List changes as a =item entry ].
-One can now specify a destination directory for Perl installation
-by specifying the DESTDIR variable for C<make install>. (This feature
-is slightly different from the previous C<Configure -Dinstallprefix=...>.)
-See F<INSTALL>.
+=over 4
-gcc versions 3.x introduced a new warning that caused a lot of noise
-during Perl compilation: C<gcc -Ialreadyknowndirectory (warning:
-changing search order)>. This warning has now been avoided by
-Configure weeding out such directories before the compilation.
+=item *
-One can now build subsets of Perl core modules by using the
-Configure flags C<-Dnoextensions=...> and C<-Donlyextensions=...>,
-see F<INSTALL>.
+XXX
-=head2 Platform-specific enhancements
+=back
-In Cygwin Perl can now be built with threads (C<Configure -Duseithreads>).
-This works with both Cygwin 1.3.22 and Cygwin 1.5.3.
+=head1 Testing
-In newer FreeBSD releases Perl 5.8.0 compilation failed because of
-trying to use F<malloc.h>, which in FreeBSD is just a dummy file, and
-a fatal error to even try to use. Now F<malloc.h> is not used.
+XXX Any significant changes to the testing of a freshly built perl should be
+listed here. Changes which create B<new> files in F<t/> go here as do any
+large changes to the testing harness (e.g. when parallel testing was added).
+Changes to existing files in F<t/> aren't worth summarising, although the bugs
+that they represent may be covered elsewhere.
-Perl is now known to build also in Hitachi HI-UXMPP.
+[ List each test improvement as a =item entry ]
-Perl is now known to build again in LynxOS.
+=over 4
-Mac OS X now installs with Perl version number embedded in
-installation directory names for easier upgrading of user-compiled
-Perl, and the installation directories in general are more standard.
-In other words, the default installation no longer breaks the
-Apple-provided Perl. On the other hand, with C<Configure -Dprefix=/usr>
-you can now really replace the Apple-supplied Perl (B<please be careful>).
+=item *
-Mac OS X now builds Perl statically by default. This change was done
-mainly for faster startup times. The Apple-provided Perl is still
-dynamically linked and shared, and you can enable the sharedness for
-your own Perl builds by C<Configure -Duseshrplib>.
+The script F<t/op/threads-dirh.t> has been added, which tests interaction
+of threads and directory handles.
-Perl has been ported to IBM's OS/400 PASE environment. The best way
-to build a Perl for PASE is to use an AIX host as a cross-compilation
-environment. See README.os400.
+=back
-Yet another cross-compilation option has been added: now Perl builds
-on OpenZaurus, an Linux distribution based on Mandrake + Embedix for
-the Sharp Zaurus PDA. See the Cross/README file.
+=head1 Platform Support
-Tru64 when using gcc 3 drops the optimisation for F<toke.c> to C<-O2>
-because of gigantic memory use with the default C<-O3>.
+XXX Any changes to platform support should be listed in the sections below.
-Tru64 can now build Perl with the newer Berkeley DBs.
+[ Within the sections, list each platform as a =item entry with specific
+changes as paragraphs below it. ]
-Building Perl on WinCE has been much enhanced, see F<README.ce>
-and F<README.perlce>.
+=head2 New Platforms
-=head1 Selected Bug Fixes
+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.
-=head2 Closures, eval and lexicals
+=over 4
-There have been many fixes in the area of anonymous subs, lexicals and
-closures. Although this means that Perl is now more "correct", it is
-possible that some existing code will break that happens to rely on
-the faulty behaviour. In practice this is unlikely unless your code
-contains a very complex nesting of anonymous subs, evals and lexicals.
+=item XXX-some-platform
-=head2 Generic fixes
+XXX
-If an input filehandle is marked C<:utf8> and Perl sees illegal UTF-8
-coming in when doing C<< <FH> >>, if warnings are enabled a warning is
-immediately given - instead of being silent about it and Perl being
-unhappy about the broken data later. (The C<:encoding(utf8)> layer
-also works the same way.)
+=back
-binmode(SOCKET, ":utf8") only worked on the input side, not on the
-output side of the socket. Now it works both ways.
+=head2 Discontinued Platforms
-For threaded Perls certain system database functions like getpwent()
-and getgrent() now grow their result buffer dynamically, instead of
-failing. This means that at sites with lots of users and groups the
-functions no longer fail by returning only partial results.
+XXX List any platforms that this version of perl no longer compiles on.
-Perl 5.8.0 had accidentally broken the capability for users
-to define their own uppercase<->lowercase Unicode mappings
-(as advertised by the Camel). This feature has been fixed and
-is also documented better.
+=over 4
-In 5.8.0 this
+=item XXX-some-platform
- $some_unicode .= <FH>;
+XXX
-didn't work correctly but instead corrupted the data. This has now
-been fixed.
+=back
-Tied methods like FETCH etc. may now safely access tied values, i.e.
-resulting in a recursive call to FETCH etc. Remember to break the
-recursion, though.
+=head2 Platform-Specific Notes
-At startup Perl blocks the SIGFPE signal away since there isn't much
-Perl can do about it. Previously this blocking was in effect also for
-programs executed from within Perl. Now Perl restores the original
-SIGFPE handling routine, whatever it was, before running external
-programs.
+XXX List any changes for specific platforms. This could include configuration
+and compilation changes or changes in portability/compatibility. However,
+changes within modules for platforms should generally be listed in the
+L</Modules and Pragmata> section.
-Linenumbers in Perl scripts may now be greater than 65536, or 2**16.
-(Perl scripts have always been able to be larger than that, it's just
-that the linenumber for reported errors and warnings have "wrapped
-around".) While scripts that large usually indicate a need to rethink
-your code a bit, such Perl scripts do exist, for example as results
-from generated code. Now linenumbers can go all the way to
-4294967296, or 2**32.
+=over 4
-=head2 Platform-specific fixes
+=item IRIX
-Linux
+Conversion of strings to floating-point numbers is now more accurate on
+IRIX systems
+L<[perl #32380]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=32380>.
-=over 4
+=item Mac OS X
-=item *
+Early versions of Mac OS X (Darwin) had buggy implementations of the
+C<setregid>, C<setreuid>, C<setrgid> and C<setruid> functions, so perl
+would pretend they did not exist.
-Setting $0 works again (with certain limitations that
-Perl cannot do much about: see L<perlvar/$0>)
+These functions are now recognised on Mac OS 10.5 (Leopard; Darwin 9) and
+higher, as they have been fixed
+L<[perl #72990]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=72990>.
-=back
+=item OpenVOS
-HP-UX
+perl now builds again with OpenVOS (formerly known as Stratus VOS)
+L<[perl #78132]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=78132>.
-=over 4
+=item Windows
-=item *
+C<$Config{gccversion}> is now set correctly when perl is built using the
+mingw64 compiler from L<http://mingw64.org>
+L<[perl #73754]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=73754>.
-Setting $0 now works.
+The build process proceeds more smoothly with mingw and dmake when
+F<C:\MSYS\bin> is in the PATH, due to a C<Cwd> fix.
=back
-VMS
+=head1 Internal Changes
-=over 4
+XXX Changes which affect the interface available to C<XS> code go here.
+Other significant internal changes for future core maintainers should
+be noted as well.
-=item *
+[ List each test improvement as a =item entry ]
-Configuration now tests for the presence of C<poll()>, and IO::Poll
-now uses the vendor-supplied function if detected.
+=over 4
=item *
-A rare access violation at Perl start-up could occur if the Perl image was
-installed with privileges or if there was an identifier with the
-subsystem attribute set in the process's rightslist. Either of these
-circumstances triggered tainting code that contained a pointer bug.
-The faulty pointer arithmetic has been fixed.
+See L</Regular expressions retain their localeness when interpolated>,
+above.
=item *
-The length limit on values (not keys) in the %ENV hash has been raised
-from 255 bytes to 32640 bytes (except when the PERL_ENV_TABLES setting
-overrides the default use of logical names for %ENV). If it is
-necessary to access these long values from outside Perl, be aware that
-they are implemented using search list logical names that store the
-value in pieces, each 255-byte piece (up to 128 of them) being an
-element in the search list. When doing a lookup in %ENV from within
-Perl, the elements are combined into a single value. The existing
-VMS-specific ability to access individual elements of a search list
-logical name via the $ENV{'foo;N'} syntax (where N is the search list
-index) is unimpaired.
+The C<sv_cmp_flags>, C<sv_cmp_locale_flags>, C<sv_eq_flags> and
+C<sv_collxfrm_flags> functions have been added. These are like their
+non-_flags counterparts, but allow one to specify whether get-magic is
+processed.
-=item *
-
-The piping implementation now uses local rather than global DCL
-symbols for inter-process communication.
+The C<sv_cmp>, C<sv_cmp_locale>, C<sv_eq> and C<sv_collxfrm> functions have
+been replaced with wrappers around the new functions.
=item *
-File::Find could become confused when navigating to a relative
-directory whose name collided with a logical name. This problem has
-been corrected by adding directory syntax to relative path names, thus
-preventing logical name translation.
+A new C<sv_2bool_flags> function has been added.
-=back
-
-Win32
-
-=over 4
+This is like C<sv_2bool>, but it lets the calling code decide whether
+get-magic is handled. C<sv_2bool> is now a macro that calls the new
+function.
=item *
-A memory leak in the fork() emulation has been fixed.
+A new macro, C<SvTRUE_nomg>, has been added.
-=item *
-
-The return value of the ioctl() built-in function was accidentally
-broken in 5.8.0. This has been corrected.
+This is like C<SvTRUE>, except that it does not process magic. It uses the
+new C<sv_2bool_flags> function.
=item *
-The internal message loop executed by perl during blocking operations
-sometimes interfered with messages that were external to Perl.
-This often resulted in blocking operations terminating prematurely or
-returning incorrect results, when Perl was executing under environments
-that could generate Windows messages. This has been corrected.
+C<sv_catsv_flags> no longer calls C<mg_get> on its second argument (the
+source string) if the flags passed to it do not include SV_GMAGIC. So it
+now matches what the documentation says it does.
=item *
-Pipes and sockets are now automatically in binary mode.
+A new interface has been added for custom check hooks on subroutines. See
+L/Custom per-subroutine check hooks>, above.
=item *
-The four-argument form of select() did not preserve $! (errno) properly
-when there were errors in the underlying call. This is now fixed.
+List op building functions have been added to the
+API. See L<op_append_elem|perlapi/op_append_elem>,
+L<op_append_list|perlapi/op_append_list>, and
+L<op_prepend_elem|perlapi/op_prepend_elem>.
=item *
-The "CR CR LF" problem of has been fixed, binmode(FH, ":crlf")
-is now effectively a no-op.
+The L<LINKLIST|perlapi/LINKLIST> macro, part of op building that
+constructs the execution-order op chain, has been added to the API.
=back
-=head1 New or Changed Diagnostics
-
-All the warnings related to pack() and unpack() were made more
-informative and consistent.
+=head1 Selected Bug Fixes
-=head2 Changed "A thread exited while %d threads were running"
+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>.
-The old version
+[ List each fix as a =item entry ]
- A thread exited while %d other threads were still running
+=over 4
-was misleading because the "other" included also the thread giving
-the warning.
+=item *
-=head2 Removed "Attempt to clear a restricted hash"
+A regular expression match in the right-hand side of a global substitution
+(C<s///g>) that is in the same scope will no longer cause match variables
+to have the wrong values on subsequent iterations. This can happen when an
+array or hash subscript is interpolated in the right-hand side, as in
+C<s|(.)|@a{ print($1), /./ }|g>
+L<[perl #19078]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=19078>.
-It is not illegal to clear a restricted hash, so the warning
-was removed.
+=item *
-=head2 New "Illegal declaration of anonymous subroutine"
+Constant-folding used to cause
-You must specify the block of code for C<sub>.
+ $text =~ ( 1 ? /phoo/ : /bear/)
-=head2 Changed "Invalid range "%s" in transliteration operator"
+to turn into
-The old version
+ $text =~ /phoo/
- Invalid [] range "%s" in transliteration operator
+at compile time. Now it correctly matches against C<$_>
+L<[perl #20444]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=20444>.
-was simply wrong because there are no "[] ranges" in tr///.
+=item *
-=head2 New "Missing control char name in \c"
+Parsing Perl code (either with string C<eval> or by loading modules) from
+within a C<UNITCHECK> block no longer causes the interpreter to crash
+L<[perl #70614]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=70614>.
-Self-explanatory.
+=item *
-=head2 New "Newline in left-justified string for %s"
+When C<-d> is used on the shebang (C<#!>) line, the debugger now has access
+to the lines of the main program. In the past, this sometimes worked and
+sometimes did not, depending on what order things happened to be arranged
+in memory
+L<[perl #71806]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71806>.
-The padding spaces would appear after the newline, which is
-probably not what you had in mind.
+=item *
-=head2 New "Possible precedence problem on bitwise %c operator"
+The C<y///> or C<tr///> operator now calls get-magic (e.g., the C<FETCH>
+method of a tie) on its left-hand side just once, not twice
+L<[perl #76814]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=76814>.
-If you think this
+=item *
- $x & $y == 0
+String comparison (C<eq>, C<ne>, C<lt>, C<gt>, C<le>, C<ge> and
+C<cmp>) and logical not (C<not> and C<!>) operators no longer call magic
+(e.g., tie methods) twice on their operands
+L<[perl #76814]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=76814>.
-tests whether the bitwise AND of $x and $y is zero,
-you will like this warning.
+This bug was introduced in an earlier 5.13 release, and does not affect
+perl 5.12.
-=head2 New "read() on %s filehandle %s"
+=item *
-You cannot read() (or sysread()) from a closed or unopened filehandle.
+When a tied (or other magic) variable is used as, or in, a regular
+expression, it no longer has its C<FETCH> method called twice
+L<[perl #76814]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=76814>.
-=head2 New "Tied variable freed while still in use"
+This bug was introduced in an earlier 5.13 release, and does not affect
+perl 5.12.
-Something pulled the plug on a live tied variable, Perl plays
-safe by bailing out.
+=item *
-=head2 New "To%s: illegal mapping '%s'"
+The C<-C> command line option can now be followed by other options
+L<[perl #72434]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=72434>.
-An illegal user-defined Unicode casemapping was specified.
+=item *
-=head2 New "Use of freed value in iteration"
+Assigning a glob to a PVLV used to convert it to a plain string. Now it
+works correctly, and a PVLV can hold a glob. This would happen when a
+nonexistent hash or array element was passed to a subroutine:
-Something modified the values being iterated over. This is not good.
+ sub { $_[0] = *foo }->($hash{key});
+ # $_[0] would have been the string "*main::foo"
-=head1 Changed Internals
+It also happened when a glob was assigned to, or returned from, an element
+of a tied array or hash
+L<[perl #36051]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=36051>.
-These news matter to you only if you either write XS code or like to
-know about or hack Perl internals (using Devel::Peek or any of the
-C<B::> modules counts), or like to run Perl with the C<-D> option.
+=item *
-The embedding examples of L<perlembed> have been reviewed to be
-uptodate and consistent: for example, the correct use of
-PERL_SYS_INIT3() and PERL_SYS_TERM().
+Creating a new thread when directory handles were open used to cause a
+crash, because the handles were not cloned, but simply passed to the new
+thread, resulting in a double free.
-Extensive reworking of the pad code (the code responsible
-for lexical variables) has been conducted by Dave Mitchell.
+Now directory handles are properly, on systems that have a C<fchdir>
+function. On other systems, new threads simply do not inherit directory
+handles from their parent threads
+L<[perl #75154]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=75154>.
-Extensive work on the v-strings by John Peacock.
+=item *
-UTF-8 length and position cache: to speed up the handling of Unicode
-(UTF-8) scalars, a cache was introduced. Potential problems exist if
-an extension bypasses the official APIs and directly modifies the PV
-of an SV: the UTF-8 cache does not get cleared as it should.
+The regular expression parser no longer hangs when parsing C<\18> and
+C<\88>.
-APIs obsoleted in Perl 5.8.0, like sv_2pv, sv_catpvn, sv_catsv,
-sv_setsv, are again available.
+This bug was introduced in version 5.13.5 and did not affect earlier
+versions
+L<[perl #78058]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=78058>.
-Certain Perl core C APIs like cxinc and regatom are no longer
-available at all to code outside the Perl core of the Perl core
-extensions. This is intentional. They never should have been
-available with the shorter names, and if you application depends on
-them, you should (be ashamed and) contact perl5-porters to discuss
-what are the proper APIs.
+=item *
-Certain Perl core C APIs like C<Perl_list> are no longer available
-without their C<Perl_> prefix. If your XS module stops working
-because some functions cannot be found, in many cases a simple fix is
-to add the C<Perl_> prefix to the function and the thread context
-C<aTHX_> as the first argument of the function call. This is also how
-it should always have been done: letting the Perl_-less forms to leak
-from the core was an accident. For cleaner embedding you can also
-force this for all APIs by defining at compile time the cpp define
-PERL_NO_SHORT_NAMES.
+Subroutine redefinition works once more in the debugger
+L<[perl #48332]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=48332>.
-Perl_save_bool() has been added.
+=item *
-Regexp objects (those created with C<qr>) now have S-magic rather than
-R-magic. This fixed regexps of the form /...(??{...;$x})/ to no
-longer ignore changes made to $x. The S-magic avoids dropping
-the caching optimization and making (??{...}) constructs obscenely
-slow (and consequently useless). See also L<perlguts/"Magic Variables">.
-Regexp::Copy was affected by this change.
+The C<&> C<|> C<^> bitwise operators no longer coerce read-only arguments
+L<[perl #20661]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=20661>.
-The Perl internal debugging macros DEBUG() and DEB() have been renamed
-to PERL_DEBUG() and PERL_DEB() to avoid namespace conflicts.
+=item *
-C<-DL> removed (the leaktest had been broken and unsupported for years,
-use alternative debugging mallocs or tools like valgrind and Purify).
+Stringifying a scalar containing -0.0 no longer has the affect of turning
+false into true
+L<[perl #45133]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=45133>.
-Verbose modifier C<v> added for C<-DXv> and C<-Dsv>, see L<perlrun>.
+=item *
-=head1 New Tests
+Aliasing packages by assigning to globs or deleting packages by deleting
+their containing stash elements used to have erratic effects on method
+resolution, because the internal 'isa' caches were not reset. This has been
+fixed.
-In Perl 5.8.0 there were about 69000 separate tests in about 700 test files,
-in Perl 5.9.0 there are about 77000 separate tests in about 780 test files.
-The exact numbers depend on the Perl configuration and on the operating
-system platform.
+=back
=head1 Known Problems
-The hash randomisation mentioned in L</Incompatible Changes> is definitely
-problematic: it will wake dormant bugs and shake out bad assumptions.
-
-Many of the rarer platforms that worked 100% or pretty close to it
-with perl 5.8.0 have been left a little bit untended since their
-maintainers have been otherwise busy lately, and therefore there will
-be more failures on those platforms. Such platforms include Mac OS
-Classic, IBM z/OS (and other EBCDIC platforms), and NetWare. The most
-common Perl platforms (Unix and Unix-like, Microsoft platforms, and
-VMS) have large enough testing and expert population that they are
-doing well.
-
-=head2 Net::Ping 450_service and 510_ping_udp failures
-
-The subtests 9 and 18 of lib/Net/Ping/t/450_service.t, and the
-subtest 2 of lib/Net/Ping/t/510_ping_udp.t might fail if you have
-an unusual networking setup. For example in the latter case the
-test is trying to send a UDP ping to the IP address 127.0.0.1.
-
-=head2 B::C
-
-The C-generating compiler backend B::C (the frontend being
-C<perlcc -c>) is even more broken than it used to be because of
-the extensive lexical variable changes. (The good news is that
-B::Bytecode and ByteLoader are better than they used to be.)
-
-=head1 Platform Specific Problems
-
-=head2 EBCDIC Platforms
-
-IBM z/OS and other EBCDIC platforms continue to be problematic
-regarding Unicode support. Many Unicode tests are skipped when
-they really should be fixed.
-
-=head2 Cygwin 1.5 problems
-
-In Cygwin 1.5 the F<io/tell> and F<op/sysio> tests have failures for
-some yet unknown reason. In 1.5.5 the threads tests stress_cv,
-stress_re, and stress_string are failing unless the environment
-variable PERLIO is set to "perlio" (which makes also the io/tell
-failure go away).
-
-Perl 5.8.1 does build and work well with Cygwin 1.3: with (uname -a)
-C<CYGWIN_NT-5.0 ... 1.3.22(0.78/3/2) 2003-03-18 09:20 i686 ...>
-a 100% "make test" was achieved with C<Configure -des -Duseithreads>.
-
-=head2 HP-UX: HP cc warnings about sendfile and sendpath
-
-With certain HP C compiler releases (e.g. B.11.11.02) you will
-get many warnings like this (lines wrapped for easier reading):
-
- cc: "/usr/include/sys/socket.h", line 504: warning 562:
- Redeclaration of "sendfile" with a different storage class specifier:
- "sendfile" will have internal linkage.
- cc: "/usr/include/sys/socket.h", line 505: warning 562:
- Redeclaration of "sendpath" with a different storage class specifier:
- "sendpath" will have internal linkage.
+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).
-The warnings show up both during the build of Perl and during certain
-lib/ExtUtils tests that invoke the C compiler. The warning, however,
-is not serious and can be ignored.
+This is a list of some significant unfixed bugs, which are regressions
+from either 5.XXX.XXX or 5.XXX.XXX.
-=head2 IRIX: t/uni/tr_7jis.t falsely failing
-
-The test t/uni/tr_7jis.t is known to report failure under 'make test'
-or the test harness with certain releases of IRIX (at least IRIX 6.5
-and MIPSpro Compilers Version 7.3.1.1m), but if run manually the test
-fully passes.
-
-=head2 Mac OS X: no usemymalloc
-
-The Perl malloc (C<-Dusemymalloc>) does not work at all in Mac OS X.
-This is not that serious, though, since the native malloc works just
-fine.
-
-=head2 Tru64: No threaded builds with GNU cc (gcc)
-
-In the latest Tru64 releases (e.g. v5.1B or later) gcc cannot be used
-to compile a threaded Perl (-Duseithreads) because the system
-C<< <pthread.h> >> file doesn't know about gcc.
-
-=head2 Win32: sysopen, sysread, syswrite
-
-As of the 5.8.0 release, sysopen()/sysread()/syswrite() do not behave
-like they used to in 5.6.1 and earlier with respect to "text" mode.
-These built-ins now always operate in "binary" mode (even if sysopen()
-was passed the O_TEXT flag, or if binmode() was used on the file
-handle). Note that this issue should only make a difference for disk
-files, as sockets and pipes have always been in "binary" mode in the
-Windows port. As this behavior is currently considered a bug,
-compatible behavior may be re-introduced in a future release. Until
-then, the use of sysopen(), sysread() and syswrite() is not supported
-for "text" mode operations.
-
-=head1 TODO
-
-Here are some things that are planned for perl 5.10.0 :
+[ List each fix as a =item entry ]
=over 4
=item *
-Various Copy-On-Write techniques will be investigated in hopes
-of speeding up Perl.
+XXX
-=item *
-
-CPANPLUS, Inline, and Module::Build will become core modules.
+=back
-=item *
+=head1 Obituary
-The ability to write true lexically scoped pragmas will be introduced,
-perhaps via a C<pragma> pragma.
+XXX If any significant core contributor has died, we've added a short obituary
+here.
-=item *
+=head1 Errata
-Work will continue on the bytecompiler and byteloader.
+=over 4
=item *
-v-strings as they currently exist are scheduled to be deprecated. The
-v-less form (1.2.3) will become a "version object" when used with C<use>,
-C<require>, and C<$VERSION>. $^V will also be a "version object" so the
-printf("%vd",...) construct will no longer be needed. The v-ful version
-(v1.2.3) will become obsolete. The equivalence of strings and v-strings (e.g.
-that currently 5.8.0 is equal to "\5\8\0") will go away. B<There may be no
-deprecation warning for v-strings>, though: it is quite hard to detect when
-v-strings are being used safely, and when they are not.
+Fixed a typo in L<perl5135delta> regarding array slices and smart matching
=back
+=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 F<http://bugs.perl.org/>. There may also be
-information at F<http://www.perl.com/>, the Perl Home Page.
+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. You can browse and search
-the Perl 5 bugs at F<http://bugs.perl.org/>.
+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 exhaustive details on what changed.
+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.
https://perl5.git.perl.org / perl5.git / blobdiff