Horton
Menu

Re: C11 / VS 2019

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

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Nazir Bilal Yavuz <byavuz81@gmail.com>, Andrew Dunstan <andrew@dunslane.net>, Michael Paquier <michael@paquier.xyz>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-07-07T16:01:19Z
Lists: pgsql-hackers 
Peter Eisentraut <peter@eisentraut.org> writes:
> On 07.07.25 16:13, Tom Lane wrote:
>> Huh.  Can we trawl the release notes for VS and see if this was
>> acknowledged as a bug fix, and if so when did it happen?

> But this one [0] seems to indicate you might need at least 16.5 for this.

Ah, that says

    Starting in Visual Studio 2019 version 16.5, preprocessor support
    for the C++20 standard is feature-complete. These changes are
    available by using the /Zc:preprocessor compiler switch.

The reference to C++20 is a bit confusing in this context; does C++
really have a different preprocessor?  But anyway, the support matrix
seems like a convincing argument that we don't have to support 16.3.
If Andrew is willing to update drongo, I'm content to leave it at
that.

			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 →

  1. Raise C requirement to C11

  2. meson: Move C99 test earlier

  3. Enable MSVC conforming preprocessor

  4. Make parseNodeString() C idiom compatible with Visual Studio 2015.