agora inbox for [email protected]
help / color / mirror / Atom feedFrom: Zdenek Kotala <[email protected]>
To: Kris Jurka <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Stefan Kaltenbrunner <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Cc: [email protected]
Subject: Re: compiler warnings on the buildfarm
Date: Fri, 13 Jul 2007 15:35:14 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
Kris Jurka wrote:
>
>
> On Fri, 13 Jul 2007, Zdenek Kotala wrote:
>
>> Tom Lane wrote:
>>> Kris Jurka <[email protected]> writes:
>>>> So pam_message ** isn't const.
>>>
>>> Ah, thanks. I see luna_moth is giving the same warning, so it's still
>>> not const in Solaris 11 either.
>>>
>>> Is it worth working around this? It's strictly cosmetic AFAICS.
>>>
>>> The main issue in my mind would be how to determine whether to use
>>> const or not. If all Solaris releases are like this, and can be
>>> expected to stay that way,
>>
>> I think yes. It is defined as X/Open standard says.
>>
>
> Not according to the link you sent earlier. My reading says that
> Solaris has it defined wrong and pg has it right.
If I look there
http://www.opengroup.org/onlinepubs/008329799/chap5.htm#tagcjh_06
in "Call Back Information" section. The structure is defined as
struct pam_conv{ int (*conv) (int, struct pam_message **, struct
pam_response **, void *); void *appdata_ptr; };
I don't see any "const" keyword there.
Zdenek
view thread (67+ messages) latest in thread
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: compiler warnings on the buildfarm
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox