X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperldata.pod;h=5ff97d4bffee347c87283bcc18798b75e0c9cf18;hb=0dfdcd8a63a82bd61087d84a6f130e03a4b20ed9;hp=0aeffc39e3a8498b18603315e8d4b02b05a203f4;hpb=15ecd4aee763c5eef4038c286267fe051c148238;p=p5sagit%2Fp5-mst-13.2.git

diff --git a/pod/perldata.pod b/pod/perldata.pod
index 0aeffc3..5ff97d4 100644
--- a/pod/perldata.pod
+++ b/pod/perldata.pod
@@ -341,6 +341,11 @@ an expression.
 
 =head3 Version Strings
 
+B<Note:> Version Strings (v-strings) have been deprecated.  They will
+be removed in some future release after Perl 5.8.1.  The marginal
+benefits of v-strings were greatly outweighed by the potential for
+Surprise and Confusion.
+
 A literal of the form C<v1.20.300.4000> is parsed as a string composed
 of characters with the specified ordinals.  This form, known as
 v-strings, provides an alternative, more readable way to construct
@@ -361,8 +366,8 @@ Note that using the v-strings for IPv4 addresses is not portable unless
 you also use the inet_aton()/inet_ntoa() routines of the Socket package.
 
 Note that since Perl 5.8.1 the single-number v-strings (like C<v65>)
-are not v-strings before the C<< => >> operator (which is used to
-separate a hash key from a hash value), instead they are interpreted
+are not v-strings before the C<< => >> operator (which is usually used
+to separate a hash key from a hash value), instead they are interpreted
 as literal strings ('v65').  They were v-strings from Perl 5.6.0 to
 Perl 5.8.0, but that caused more confusion and breakage than good.
 Multi-number v-strings like C<v65.66> and C<65.66.67> continue to