document plperl argument and return value representation

Andrew Dunstan wrote:

The attached docs patch makes clearer how arguments and return values in
pl/perl are escaped. This is to clarify the situation that Theo
Schlossnagle recently reported on -bugs.

I find the mix of arguments and results a bit confusing. Maybe you
could put them in separate paragraphs.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Alvaro Herrera wrote:

Andrew Dunstan wrote:

The attached docs patch makes clearer how arguments and return values in
pl/perl are escaped. This is to clarify the situation that Theo
Schlossnagle recently reported on -bugs.

I find the mix of arguments and results a bit confusing. Maybe you
could put them in separate paragraphs.

Is this better?

I also took the opportunity to replace an unbalanced quote mark that was
screwing up the syntax highlighting.

cheers

andrew

Andrew Dunstan <andrew@dunslane.net> writes:

Is this better?

I suggest bytea -> <type>bytea</>, otherwise seems fine.

regards, tom lane

Andrew Dunstan wrote:

Alvaro Herrera wrote:

Andrew Dunstan wrote:

The attached docs patch makes clearer how arguments and return values in
pl/perl are escaped. This is to clarify the situation that Theo
Schlossnagle recently reported on -bugs.

I find the mix of arguments and results a bit confusing. Maybe you
could put them in separate paragraphs.

Is this better?

Yup, looks very nice.

This message also serves to test whether I removed the annoying
Mail-Followup-To header. It was actually a _feature_ of mutt
(followup_to, which fired when I replied to a list to which I'm
subscribed), which I disabled. Sorry about that.

ETOOMANYWHICH, sorry about that as well :-)

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.