From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-docs(at)postgresql(dot)org |
Subject: | pl/perl doc correction: subroutines |
Date: | 2009-08-08 01:00:48 |
Message-ID: | 4A7CCE40.8030504@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
All,
From 40.1. PL/Perl Functions and Arguments
"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 the perldiag man page for
more details."
The reference to the "perldiag" doc is confusing because it's a
dictionary of errors. We need to be specific about what part of the page:
"See "Variable %s Will Not Stay Shared" and "Variable %s is not
available" in the perldiag man page for more details."
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Wenk | 2009-08-14 21:07:29 | wording for 38.6.2.4. Simple CASE and 38.6.2.5. Searched CASE |
Previous Message | decibel | 2009-08-07 05:06:10 | Re: What happens when syslog gets blocked? |