From: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Get ride of pqbool artifact (src/interfaces/libpq/libpq-fe.h) |
Date: | 2025-09-02 19:53:10 |
Message-ID: | CAEudQAreHGCmsSJ8An8vMNG5T_7DaB34rDM+9NEWdv-Td2Nacg@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Em ter., 2 de set. de 2025 às 16:44, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> escreveu:
> Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> writes:
> > In libpq-fe.h has an artifact pre C99, pqbool.
> > IMO this is not more necessary, once Postgres supports C99
> > and bool becomes standard.
>
> > So get ride of pqbool and use bool instead.
>
> We can't really remove that typedef ever, because application code
> might be using it. Unlikely I concede, but nonetheless it's part
> of libpq's exposed API.
>
> We might be able to s/pqbool/bool/ in the struct, but I kind of
> wonder if that wouldn't be an ABI break: at the very least it
> would lead to subtle changes in code compiled to use the struct.
> On the whole I see little value in taking any risk here.
>
Thanks Tom, for the explanation.
best regards,
Ranier Vilela
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2025-09-02 20:07:17 | Re: plan shape work |
Previous Message | Jacob Champion | 2025-09-02 19:51:50 | Re: Get ride of pqbool artifact (src/interfaces/libpq/libpq-fe.h) |