Fix a couple URLs in perlhack

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

=head1 NAME

perldelta - what is new for perl v5.9.4

=head1 DESCRIPTION

This document describes differences between the 5.9.3 and the 5.9.4
developement releases. See L<perl590delta>, L<perl591delta>, L<perl592delta>
and L<perl593delta> for the differences between 5.8.0 and 5.9.3.

=head1 Incompatible Changes

=head2 chdir FOO

A bareword argument to chdir() is now recognized as a file handle.
Earlier releases interpreted the bareword as a directory name.

=head2 Handling of pmc files

And old feature of perl is that before C<require> or C<use> look for a
file with a F<.pm> extension, they will first look for a similar filename
with a F<.pmc> extension. If this file is found, it will be loaded in
place of any potentially existing file ending in a F<.pm> extension.

Previously, F<.pmc> files were loaded only if more recent than the
matching F<.pm> file. Starting with 5.9.4, they'll be always loaded if
they exist. (This trick is used by Pugs.)

=head2 @- and @+ in patterns

The special arrays C<@-> and C<@+> are no longer interpolated in regular
expressions.

=head2 $AUTOLOAD can now be tainted

If you call a subroutine by a tainted name, and if it defers to an
AUTOLOAD function, then $AUTOLOAD will be (correctly) tainted.

=head1 Core Enhancements

=head2 state() variables

=head2 UNIVERSAL:DOES()

=head1 Modules and Pragmata

C<encoding::warnings> is now a lexical pragma. (Although on older perls,
which don't have support for lexical pragmas, it keeps its global
behaviour.)

C<threads>

=head2 New Core Modules

=over 4

=item *

C<Module::Build> has been added. It's an alternative to
C<ExtUtils::MakeMaker> to build and install perl modules.

=item *

C<Module::Load> has been added. It's used to load indistinctively modules
and files.

=item *

C<Hash::Util::FieldHash> has been added. This module provides support for
I<field hashes>: hashes that maintain an association of a reference with a
value, in a thread-safe garbage-collected way.

=item *

C<Win32API::File> has been added (for Windows builds). This module
provides low-level access to Win32 system API calls for files/dirs.

=back

=head1 Utility Changes

=head1 Documentation

=head2 New manpage, perlpragma

The L<perlpragma> manpage documents how to write one's own lexical
pragmas in pure Perl.

=head2 New manpage, perlreguts

The L<perlreguts> manpage, due to Yves Orton, describes internals of the
Perl regular expression engine.

=head2 New manpage, perlunitut

The L<perlunitut> manpage is an tutorial for programming with Unicode and
string encodings in Perl, due to Juerd Waalboer.

=head1 Performance Enhancements

Constants (Nicholas)

Regular expressions (Yves)

=head1 Installation and Configuration Improvements

=head2 Ports

Perl has been reported to work on DragonFlyBSD.

Many improvements have been made towards making Perl work correctly on
z/OS.

=head2 Compilation improvements

All F<ppport.h> files in the XS modules bundled with perl are now
autogenerated at build time.

=head2 New probes

The configuration process now detects whether strlcat and strlcpy are
available.  When they are not available, perl's own version is used (from
Russ Allbery's public domain implementation).  Various places in the perl
interpreter now uses them.

=head1 Selected Bug Fixes

=head2 PERL5SHELL and tainting

On Windows, PERL5SHELL is now checked for taintedness.

=head2 Using *FILE{IO}

C<stat()> and C<-X> filetests now treat *FILE{IO} filehandles like *FILE
filehandles.

=head1 New or Changed Diagnostics

=head1 Changed Internals

Arenas

Mathoms and factorizations (many PP functions are now shared for several ops)

=head1 Known Problems

=head2 Platform Specific Problems

=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://bugs.perl.org/ .  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.

=head1 SEE ALSO

The F<Changes> file for 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