Date: Wed, 14 May 2008 12:47:27 -0700
From: daveg <daveg@sonic.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: Merlin Moncure <mmoncure@gmail.com>, Andrew Dunstan <andrew@dunslane.net>,
	Alvaro Herrera <alvherre@commandprompt.com>,
	"Patches (PostgreSQL)" <pgsql-patches@postgresql.org>,
	Andrew Chernow <ac@esilo.com>
Subject: Re: libpq object hooks
Message-ID: <20080514194727.GT5673@sonic.net>
References: <b42b73150805140723y71d0a6e2mc325e64d1a0df9f7@mail.gmail.com>
	<200805141452.m4EEqh814039@momjian.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200805141452.m4EEqh814039@momjian.us>
User-Agent: Mutt/1.4.2.1i

On Wed, May 14, 2008 at 10:52:43AM -0400, Bruce Momjian wrote:
> 
> One idea would be to add the libpq hooks but not document them.  This
> way, we can modify or remove the API as needed in the future.  As
> libpqtypes matures and we are sure what the API should be, we can
> document it as stable and permanent.

-1

Perhaps it is just me, but undocumented interface are evil. Simply document
it with the changable bits labled as such.

-dg

-- 
David Gould       daveg@sonic.net      510 536 1443    510 282 0869
If simplicity worked, the world would be overrun with insects.