Re: automating pg_config.h.win32 maintenance

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: automating pg_config.h.win32 maintenance
Date: 2019-12-13 14:05:46
Message-ID: 9e0f3866-6dd6-b90b-81cd-800df50393b5@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-12-13 14:44, Michael Paquier wrote:
> It would be nice to put a comment close to FLEXIBLE_ARRAY_MEMBER,
> where you use "/* */" as a way to emulate an empty value which is
> still defined. Or would it be cleaner to just use an empty string?

That's just the way Autoconf does it. I haven't pondered why it's done
that way, only focusing on making the resulting files match.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2019-12-13 14:32:58 Re: disable only nonparallel seq scan.
Previous Message Tom Lane 2019-12-13 13:56:32 Re: automating pg_config.h.win32 maintenance