Improve warning about creating nested named subroutines in plperl.

Per discussion.

diff --git a/doc/src/sgml/plperl.sgml b/doc/src/sgml/plperl.sgml
index 549359f58f3d3e7d9f487d245333e98b3e529e54..bb25ab1380b7a9e3221cc657b4ecf24c00dc70a3 100644 (file)
--- a/doc/src/sgml/plperl.sgml
+++ b/doc/src/sgml/plperl.sgml
@@ -1,4 +1,4 @@
-
+
 
  
   PL/Perl - Perl Procedural Language
@@ -85,12 +85,13 @@ $$ LANGUAGE plperl;
    
     The use of named nested subroutines is dangerous in Perl, especially if
     they refer to lexical variables in the enclosing scope. Because a PL/Perl
-    function is wrapped in a subroutine, any named subroutine you create will
-    be nested. In general, it is far safer to create anonymous subroutines
-    which you call via a coderef. See Variable "%s" will not stay shared
-    and Variable "%s" is not available in the
-    perldiag man page for more
-    details.
+    function is wrapped in a subroutine, any named subroutine you place inside
+    one will be nested. In general, it is far safer to create anonymous
+    subroutines which you call via a coderef. For more information, see the
+    entries for Variable "%s" will not stay shared and
+    Variable "%s" is not available in the
+    perldiag man page, or
+    search the Internet for perl nested named subroutine.