Re: Make copyObject work in C++

From: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Make copyObject work in C++
Date: 2026-03-23 09:58:34
Message-ID: CAGECzQSB=rBZ2n1WeCRAQ09xHzHSpyVBk-+NWEAcLsegsRXPzA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 23 Mar 2026 at 10:27, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> I think we should commit the pg_list.h changes, since the C-style
> compound literals are not a C++ feature at all, and so without this MSVC
> would never get supported. (Or you couldn't use PostgreSQL lists, which
> would be very limiting.)

Sounds good to me.

> The other changes deal with designated initializers and flexible array
> members. These are not a blocker, since extension authors could deal
> with them themselves by adding appropriate compiler options or similar.

I think we should add these flags to CXXFLAGS for MSVC by default,
similar to how we add -std=gnu++11/-std=c++11 for other compilers. We
can then document on the C++ extension docs page, that MSVC compilers
require C++20 support.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Antonin Houska 2026-03-23 10:20:03 Re: Adding REPACK [concurrently]
Previous Message Antonin Houska 2026-03-23 09:58:00 Re: Race conditions in logical decoding