Re: Change copyObject() to use typeof_unqual

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Peter Eisentraut <peter@eisentraut.org>

Cc: pgsql-hackers <pgsql-hackers@postgresql.org>, Andres Freund <andres@anarazel.de>

Date: 2026-02-04T15:38:29Z

Lists: pgsql-hackers

Peter Eisentraut <peter@eisentraut.org> writes:
> Another attempt was to switch the order of the configure test to check 
> for __typeof_unqual__ before typeof_unqual.  This works, but it seems 
> totally unprincipled.

Seems perfectly reasonable from here.

			regards, tom lane

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add some const qualifiers enabled by typeof_unqual change on copyObject
- 7724cb9935a9 19 (unreleased) landed
Hardcode typeof_unqual to __typeof_unqual__ for clang
- 2eb6cd327cae 19 (unreleased) landed
Clean up postgres_fdw/t/010_subscription.pl.
- f4af7849b3db 19 (unreleased) cited
Hardcode override of typeof_unqual for clang-for-bitcode
- 63275ce84d2f 19 (unreleased) landed
Make typeof and typeof_unqual fallback definitions work on C++11
- cd083b54bd67 19 (unreleased) landed
Change copyObject() to use typeof_unqual
- 59292f7aac72 19 (unreleased) landed
- 4cfce4e62c8f 19 (unreleased) landed
Fixes for C++ typeof implementation
- 9c05f152b5dd 19 (unreleased) landed
Support using copyObject in standard C++
- 1887d822f142 19 (unreleased) cited