Skip to content

P
Postgres FD Implementation
Commit 1a6d678f authored by Peter Eisentraut's avatar Peter Eisentraut
Browse files
Options

Clarify the documentation about PL/Perl nested subroutines, per Josh 

Berkus.
parent efc1aeb8
Hide whitespace changes
Inline Side-by-side
Showing with 5 additions and 3 deletions
doc/src/sgml/plperl.sgml
View file @ 1a6d678f
<!-- $PostgreSQL: pgsql/doc/src/sgml/plperl.sgml,v 2.69 2008/04/10 15:16:46 alvherre Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/plperl.sgml,v 2.70 2009/08/15 00:33:12 petere Exp $ -->
<chapter id="plperl"> <chapter id="plperl">
<title>PL/Perl - Perl Procedural Language</title> <title>PL/Perl - Perl Procedural Language</title>
...@@ -72,8 +72,10 @@ $$ LANGUAGE plperl; ...@@ -72,8 +72,10 @@ $$ LANGUAGE plperl;
they refer to lexical variables in the enclosing scope. Because a PL/Perl 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 function is wrapped in a subroutine, any named subroutine you create will
be nested. In general, it is far safer to create anonymous subroutines be nested. In general, it is far safer to create anonymous subroutines
which you call via a coderef. See the <literal>perldiag</literal> which you call via a coderef. See <literal>Variable "%s" will not stay shared</literal>
man page for more details. and <literal>Variable "%s" is not available</literal> in the
<citerefentry><refentrytitle>perldiag</></citerefentry> man page for more
details.
</para> </para>
</note> </note>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment