Re: Inconsistencies around defining FRONTEND

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

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

To: Robert Haas <robertmhaas@gmail.com>

Cc: Andres Freund <andres@anarazel.de>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, Noah Misch <noah@leadboat.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, samay sharma <smilingsamay@gmail.com>, Nazir Bilal Yavuz <byavuz81@gmail.com>

Date: 2022-08-23T21:56:23Z

Lists: pgsql-hackers

Robert Haas <robertmhaas@gmail.com> writes:
> Actually, I think we could fix these pretty easily too. See attached.

Hmm, do these headers still pass headerscheck/cpluspluscheck?

I might quibble a bit with the exact placement of the #ifndef FRONTEND
tests, but overall this looks pretty plausible.

			regards, tom lane

Commits

Don't define FRONTEND for ecpg libraries
- 9352d5cf128a 16.0 landed
Don't define FRONTEND for initdb
- 06e3559bade1 16.0 landed
Don't define FRONTEND for libpq
- 1d77afefbd1d 16.0 landed