Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 425A41336DB6 for ; Thu, 28 Oct 2010 14:03:33 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 36258-04 for ; Thu, 28 Oct 2010 17:03:26 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from cdptpa-omtalb.mail.rr.com (cdptpa-omtalb.mail.rr.com [75.180.132.123]) by mail.postgresql.org (Postfix) with ESMTP id CF82E13364DE for ; Thu, 28 Oct 2010 14:03:25 -0300 (ADT) X-Authority-Analysis: v=1.1 cv=Inhw+Jdt7z1D3BivGPfn2aw54OvUEJw5lAn/booRZkE= c=1 sm=0 a=8nJEP1OIZ-IA:10 a=qCTYjJJ2g1SgQhsHZAUATw==:17 a=HZRpa_jdXoI8A9SKLTIA:9 a=pzViarLXP1bhHoGEAPUXRbVyo-oA:4 a=wPNLvfGTeEIA:10 a=qCTYjJJ2g1SgQhsHZAUATw==:117 X-Cloudmark-Score: 0 X-Originating-IP: 98.27.48.207 Received: from [98.27.48.207] ([98.27.48.207:47057] helo=[192.168.10.104]) by cdptpa-oedge04.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id 39/0E-13137-DDCA9CC4; Thu, 28 Oct 2010 17:03:25 +0000 Message-ID: <4CC9ACDC.9090508@dunslane.net> Date: Thu, 28 Oct 2010 13:03:24 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100907 Fedora/3.1.3-1.fc13 Lightning/1.0b3pre Thunderbird/3.1.3 MIME-Version: 1.0 To: Tom Lane CC: Pavel Stehule , PostgreSQL-development , Tim Bunce Subject: Re: plperl arginfo References: <4CC995C2.3000704@dunslane.net> <16686.1288280351@sss.pgh.pa.us> <4CC9A4E2.9050604@dunslane.net> <20300.1288283668@sss.pgh.pa.us> In-Reply-To: <20300.1288283668@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201010/1996 X-Sequence-Number: 173036 On 10/28/2010 12:34 PM, Tom Lane wrote: > > BTW, maybe we could have the best of both worlds? Dunno about Perl, > but in some languages it would be possible to instantiate the hash > only if it's actually touched. Passing the data as a hash definitely > seems to fit with the spirit of things otherwise, so as long as it > didn't cost cycles when not needed, I'd be in favor of that API. Maybe, but I think that's getting rather beyond my perlguts-fu. I think we'd need to do that via PERL_MAGIC_tied, but it's new territory for me. Anyone else want to chime in? cheers andrew