From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <maillist@candle.pha.pa.us>
Cc: pgsql-interfaces@postgreSQL.org
Cc: pgsql-hackers@postgreSQL.org
Subject: Re: [INTERFACES] Re: [HACKERS] Convert PGconn, PGresult to opaque types?
Date: Mon, 24 Aug 1998 17:52:20 -0400
Message-ID: <25056.903995540@sss.pgh.pa.us> (raw)
In-Reply-To: <199808241534.LAA00982@candle.pha.pa.us>
Bruce Momjian <maillist@candle.pha.pa.us> writes:
> I am convinced. Hide the structure members, and lets go through beta
> like that. If we have problems, we can supply a patch to expose the
> structure members, with the knowledge there will be no workaround patch
> for 6.5. They have to fix it by then.
Actually, the "patch" will just be to #include libpq-int.h along with
lipq-fe.h. I arranged for libpq-int.h to be one of the installed header
files, with the idea that some people would rather do that than fix
their code properly. It's their choice: if they want to depend on libpq
internals and have a greater risk of their code breaking across
releases, they can. I just want to discourage that a little bit, and
make it real clear what's considered supported API and what's considered
internal detail.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, maillist@candle.pha.pa.us, pgsql-hackers@postgreSQL.org
Subject: Re: [INTERFACES] Re: [HACKERS] Convert PGconn, PGresult to opaque types?
In-Reply-To: <25056.903995540@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox