Provice virtual $Config{ccflags_nolargefiles} etc.

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

diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index e5cf5f6..d0c8113 100644 (file)
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -25,13 +25,13 @@ are safe.
 
 The exploit attempt reporting feature has been completely removed from
 the Perl 5.7.0 release, so that particular vulnerability isn't there
-anymore.  However, further security vulnerabilities are, unfortunately,
-always possible.  The suidperl code is being reviewed and if deemed too
-risky to continue to support it may be completely removed from future
-releases.  In any case, suidperl should only be used by security
-experts who know exactly what they are doing and why they are using
-suidperl instead of some other solution such as sudo (see
-http://www.courtesan.com/sudo/).
+anymore.  However, further security vulnerabilities are,
+unfortunately, always possible.  The suidperl code is being reviewed
+and if deemed too risky to continue to be supported, it may be
+completely removed from future releases.  In any case, suidperl should
+only be used by security experts who know exactly what they are doing
+and why they are using suidperl instead of some other solution such as
+sudo (see http://www.courtesan.com/sudo/).
 
 =head1 Incompatible Changes
 
@@ -155,8 +155,9 @@ the podlators bundle, Pod::LaTeX, Pod::Parser, Term::ANSIColor, Test.
 =item *
 
 Bug fixes and minor enhancements have been applied to B::Deparse,
-Data::Dumper, IO::Poll, IO::Socket::INET, Math::BigFloat, Math::Complex,
-re, SelfLoader, Sys::SysLog, Test::Harness, Text::Wrap, UNIVERSAL.
+Data::Dumper, IO::Poll, IO::Socket::INET, Math::BigFloat,
+Math::Complex, Math::Trig, re, SelfLoader, Sys::SysLog, Test::Harness,
+Text::Wrap, UNIVERSAL.
 
 =item *
 
@@ -217,12 +218,6 @@ The Emacs perl mode (emacs/cperl-mode.el) has been updated to version 4.31.
 
 =item *
 
-The long-dormant perl bytecompiler has been added to the list of
-installed utilities since the bytecompiler backend has been improved.
-The bytecompiler is still very much experimental, though.
-
-=item *
-
 Perlbug is now much more robust.  It also sends the bug report to perl.org,
 not perl.com.
 
@@ -265,7 +260,7 @@ perlnewmod tells about writing and submitting a new module.
 =item *
 
 perlposix-bc explains using Perl on the POSIX-BC platform
-(a mainframe platform).
+(an EBCDIC mainframe platform).
 
 =item *
 
@@ -285,8 +280,14 @@ distribution.
 
 =head1 Performance Enhancements
 
+=over 4
+
+=item *
+
 map() that changes the size of the list should now work faster.
 
+=back
+
 =head1 Installation and Configuration Improvements
 
 =head2 Generic Improvements
@@ -413,7 +414,7 @@ C<q(a\\b)> now parses correctly as C<'a\\b'>.
 =item *
 
 Printing quads (64-bit integers) with printf/sprintf now works
-without q L ll prefixes (assuming you are on a quad-capable platform).
+without the q L ll prefixes (assuming you are on a quad-capable platform).
 
 =item *
 
@@ -682,7 +683,7 @@ marked.
 
 The various "opened only for", "on closed", "never opened" warnings
 drop the C<main::> prefix for filehandles in the C<main> package,
-for example C<STDIN> instead of <main::STDIN>.
+for example C<STDIN> instead of <main::STDIN>. 
 
 The "Unrecognized escape" warning has been extended to include C<\8>,
 C<\9>, and C<\_>.  There is no need to escape any of the C<\w> characters.
@@ -737,12 +738,17 @@ The plan is to bring them back.
 
 Certain extensions like mod_perl and BSD::Resource are known to have
 issues with `largefiles', a change brought by Perl 5.6.0 in which file
-offsets default to 64 bits wide where supported.  Modules may fail to
+offsets default to 64 bits wide, where supported.  Modules may fail to
 compile at all or compile and work incorrectly.  Currently there is no
-good solution for the problem, but Configure now stores the relevant
-flags and libraries in the %Config hash so the extensions that are having
-problems can try configuring themselves without the largefileness.
-This is admittedly not a clean solution.
+good solution for the problem, but Configure now provides appropriate
+non-largefile ccflags, ldflags, libswanted, and libs in the %Config
+hash (e.g., $Config{ccflags_nolargefiles}) so the extensions that are
+having problems can try configuring themselves without the
+largefileness.  This is admittedly not a clean solution, and the
+solution may not even work at all.  One potential failure is whether
+one can (or, if one can, whether it's a good idea) link together at
+all binaries with different ideas about file offsets, all this is
+platform-dependent.
 
 =over 4