Mention version.pm and new v-string portability warning in

perldelta. Better wording for this warning in perldiag by
Tom Wyant.

p4raw-id: //depot/perl@32204

diff --git a/pod/perl5100delta.pod b/pod/perl5100delta.pod
index e518b40..32a763c 100644 (file)
--- a/pod/perl5100delta.pod
+++ b/pod/perl5100delta.pod
@@ -623,6 +623,10 @@ The C<base> pragma now warns if a class tries to inherit from itself.
 C<strict> and C<warnings> will now complain loudly if they are loaded via
 incorrect casing (as in C<use Strict;>). (Johan Vromans)
 
+=item C<version>
+
+The C<version> module provides support for version objects.
+
 =item C<warnings>
 
 The C<warnings> pragma doesn't load C<Carp> anymore. That means that code
@@ -1373,6 +1377,11 @@ Two deprecation warnings have been added: (Rafael)
 
 Perl's command-line switch C<-P> is now deprecated.
 
+=item v-string in use/require is non-portable
+
+Perl will warn you against potential backwards compatibility problems with
+the C<use VERSION> syntax.
+
 =item perl -V
 
 C<perl -V> has several improvements, making it more useable from shell

diff --git a/pod/perldiag.pod b/pod/perldiag.pod
index 21a3891..1dd79a3 100644 (file)
--- a/pod/perldiag.pod
+++ b/pod/perldiag.pod
@@ -4940,10 +4940,9 @@ are being ignored.
 (W portable) The use of v-strings is non-portable to older, pre-5.6, Perls.
 If you want your scripts to be backward portable, use the floating
 point version number: for example, instead of C<use 5.6.1> say
-C<use 5.006_001>.  This of course won't help: the older Perls
-won't suddenly start understanding newer features, but at least
-they will show a sensible error message indicating the required
-minimum version.
+C<use 5.006_001>. This of course won't make older Perls suddenly start
+understanding newer features, but at least they will show a sensible
+error message indicating the required minimum version.
 
 This warning is suppressed if the C<use 5.x.y> is preceded by a
 C<use 5.006> (see C<use VERSION> in L<perlfunc/use>).