From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Payman <payman@Club-Internet.fr>
Cc: Michael Klatt <mdklatt@ou.edu>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: PQcmdTuples() declaration
Date: Fri, 08 Nov 2002 10:15:12 -0500
Message-ID: <5860.1036768512@sss.pgh.pa.us> (raw)
In-Reply-To: <200211080511.gA85B2K11157@candle.pha.pa.us>
References: <200211080511.gA85B2K11157@candle.pha.pa.us>
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> The issue with PQcmdTuples() and PQcmdStatus() are that they return
> *result structure member pointers. The patch makes the *result a const,
> then we have to return the values as const's. The code compiled OK, so
> I assume that is fine. How does that sound to others, or should we keep
> the result non-const?
Adding a const to the result type will break client applications that
aren't expecting it. I don't think we can get away with that.
We could still declare the input type as const if we were willing to
cast away const inside the functions, but that seems pretty ugly.
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, pgman@candle.pha.pa.us, payman@Club-Internet.fr, mdklatt@ou.edu
Subject: Re: PQcmdTuples() declaration
In-Reply-To: <5860.1036768512@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