MIME-Version: 1.0
References: 
 <CAGECzQR21OnnKiZO_1rLWO0-16kg1JBxnVq-wymYW0-_1cUNtg@mail.gmail.com>
 <2844370.1765136707@sss.pgh.pa.us>
 <e3213d37-f28c-4836-9daa-5e2ba20a7c49@eisentraut.org>
 <2998351.1765205466@sss.pgh.pa.us>
In-Reply-To: <2998351.1765205466@sss.pgh.pa.us>
From: Jelte Fennema-Nio <postgres@jeltef.nl>
Date: Mon, 8 Dec 2025 16:31:30 +0100
Message-ID: 
 <CAGECzQS6pD+HZs7avaAtp6NmzCNWV+WBC=x0P+RxstDMC4J3-w@mail.gmail.com>
Subject: Re: Make copyObject work in C++
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter@eisentraut.org>,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
 Thomas Munro <thomas.munro@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CAGECzQS6pD%2BHZs7avaAtp6NmzCNWV%2BWBC%3Dx0P%2BRxstDMC4J3-w%40mail.gmail.com>
Precedence: bulk

On Mon, 8 Dec 2025 at 15:51, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Peter Eisentraut <peter@eisentraut.org> writes:
> > AFAICT, both gcc and clang support typeof in C++ mode as well.  So this
> > kind of renaming could be confusing.
>
> Hm, if that's true then we should not have to do anything ...
> so why is Jelte reporting a problem?

Seems it's related to -std=c++17 vs -std=gnu++17. I was compiling my
code with the former, which throws the error in question[1]. Compiling
with the latter works fine[2].

So I guess it depends what we want to require from C++ extensions.
Should we require them to compile with gnu extensions? My opinion on
that would be no.

[1]: https://godbolt.org/z/fz567hs1r
[2]: https://godbolt.org/z/cq1se55bn