Skip site navigation (1) Skip section navigation (2)

Re: leakproof

From: "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: leakproof
Date: 2012-02-26 23:44:12
Message-ID: B061AFF1-D245-4562-A72B-C266DDD89322@themactionfaction.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Feb 26, 2012, at 10:39 AM, Peter Eisentraut wrote:

> On ons, 2012-02-22 at 10:56 -0500, Andrew Dunstan wrote:
>> The trouble with "leakproof" is that it 
>> doesn't point to what it is that's not leaking, which is information 
>> rather than memory, as many might imagine (and I did) without further 
>> hints. I'm not sure any single English word would be as descriptive as
>> I'd like. 
> 
> Well, we have RETURNS NULL ON NULL INPUT, so maybe DOES NOT LEAK
> INFORMATION. ;-)

If you are willing to go full length, then the computer science term is "referential transparency", no? 

http://en.wikipedia.org/wiki/Referential_transparency_(computer_science)

So a function could be described as "REFERENTIALLY TRANSPARENT".

Cheers,
M

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2012-02-27 00:10:03
Subject: Re: Misleading CREATE TABLE error
Previous:From: Thom BrownDate: 2012-02-26 23:24:31
Subject: Re: Command Triggers, patch v11

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group