Re: Add some const decorations to prototypes

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Add some const decorations to prototypes
Date: 2017-11-10 14:05:49
Message-ID: c8c19fad-0379-5721-9cbe-fc793eabdc79@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/4/17 16:50, Fabien COELHO wrote:
>>> Just leave it as char*. If you change the endptr argument you're going to
>>> force every call site to change their return variable, and some of them
>>> would end up having to cast away the const on their end.
>>
>> OK, here is an updated patch with the controversial bits removed.
>
> I'm in general favor in helping compilers, but if you have to cheat.
>
> ISTM That there is still at least one strange cast:
>
> +static const char **LWLockTrancheArray = NULL;
> + LWLockTrancheArray = (const char **) // twice

These are not cases of "cheating". This is just the return value of a
memory allocation function being cast from void * to the appropriate
result type. That is an orthogonal style decision that I have
maintained in these cases.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2017-11-10 14:49:28 Re: Variable substitution in psql backtick expansion
Previous Message Pavel Stehule 2017-11-10 13:40:21 Re: Transform for pl/perl