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

Re: leakproof

From: Noah Misch <noah(at)leadboat(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, marc(at)bloodnok(dot)com,pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>,Jeff Janes <jeff(dot)janes(at)gmail(dot)com>,Don Baccus <dhogaza(at)pacifier(dot)com>, Kevin(dot)Grittner(at)wicourts(dot)gov
Subject: Re: leakproof
Date: 2012-02-25 04:00:14
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Wed, Feb 22, 2012 at 06:30:37PM -0500, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > On 02/22/2012 04:29 PM, Marc Munro wrote:
> >> As the developer of veil I feel marginally qualified to bikeshed here:
> >> how about "silent"?  A silent function being one that will not blab.
> > I also made this suggestion later in the day.
> SILENT isn't a bad idea.  It seems to lead the mind in the right
> direction, or at least not encourage people to guess the wrong meaning.

+1 for SILENT.  I also liked Kevin's suggestion of DISCREET; it comes closer
than SILENT to denoting the property in question, but it also carries a social
undertone that feels out of place in a software function declaration.

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2012-02-25 05:46:09
Subject: Re: psql \i tab completion initialization problem on HEAD
Previous:From: Alvaro HerreraDate: 2012-02-25 03:29:53
Subject: Re: Patch for BUG #6480, psql incorrect indent for inherited tables names with UTF-8 NLS

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