sharpetronics/PostgreSQL
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-02 00:01:40 -04:00
Code Issues Projects Releases Wiki Activity

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

Browse Source 
Berkus.
This commit is contained in:
Peter Eisentraut 2009-08-15 00:33:12 +00:00
parent efc1aeb85a
commit 1a6d678f00
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/src/sgml/plperl.sgml
View File

@ -1,4 +1,4 @@
<!-- $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;
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>