Re: automating pg_config.h.win32 maintenance

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Michael Paquier <michael@paquier.xyz>, Heikki Linnakangas <hlinnaka@iki.fi>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-12-13T14:05:46Z
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



Commits

  1. Generate pg_config.h from pg_config.h.in on Windows