diff options
| author | Peter Eisentraut | 2009-08-15 00:33:12 +0000 |
|---|---|---|
| committer | Peter Eisentraut | 2009-08-15 00:33:12 +0000 |
| commit | d7e4acf0000eee234bc0b243baf31bc09478da7b (patch) | |
| tree | 5941133063272069df9617ce220f60fa8e75646d | |
| parent | 4653b9bc3e881ac084d79920895bb7a7947945de (diff) | |
Clarify the documentation about PL/Perl nested subroutines, per Josh
Berkus.
| -rw-r--r-- | doc/src/sgml/plperl.sgml | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/src/sgml/plperl.sgml b/doc/src/sgml/plperl.sgml index 2f2e53bbf1..49631f27d9 100644 --- a/doc/src/sgml/plperl.sgml +++ b/doc/src/sgml/plperl.sgml @@ -72,8 +72,10 @@ $$ LANGUAGE plperl; 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 the <literal>perldiag</literal> - man page for more details. + which you call via a coderef. See <literal>Variable "%s" will not stay shared</literal> + and <literal>Variable "%s" is not available</literal> in the + <citerefentry><refentrytitle>perldiag</></citerefentry> man page for more + details. </para> </note> |