pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: John Naylor <john.naylor@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Move gramparse.h to src/backend/parser
Date: Wed, 14 Sep 2022 04:02:22 +0000
Message-ID: <E1oYJbR-000FbR-LP@gemulon.postgresql.org> (raw)

Move gramparse.h to src/backend/parser

This header is semi-private, being used only in files related to
raw parsing, so move to the backend directory where those files
live. This allows removal of Makefile rules that symlink gram.h to
src/include/parser, since gramparse.h can now include gram.h from
within the same directory. This has the side-effect of no longer
installing gram.h and gramparse.h, but there doesn't seem to be a
good reason to continue doing so.

Per suggestion from Andres Freund and Peter Eisentraut
Discussion: https://www.postgresql.org/message-id/20220904181759.px6uosll6zbxcum5%40awork3.anarazel.de

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/ecaf7c5df54f7fa9df2fdc7225d2bb4e283f0081

Modified Files
--------------
src/backend/Makefile                        | 7 +------
src/backend/parser/gram.y                   | 2 +-
src/{include => backend}/parser/gramparse.h | 4 ++--
src/backend/parser/parser.c                 | 2 +-
src/backend/parser/scan.l                   | 2 +-
src/include/Makefile                        | 4 ++--
src/include/parser/.gitignore               | 1 -
src/tools/msvc/Install.pm                   | 4 ----
src/tools/pginclude/cpluspluscheck          | 1 -
src/tools/pginclude/headerscheck            | 1 -
10 files changed, 8 insertions(+), 20 deletions(-)



view thread (13+ messages)  latest in thread

Message-ID: <E1oYJbR-000FbR-LP@gemulon.postgresql.org>
Permalink:  ../E1oYJbR-000FbR-LP@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1oYJbR-000FbR-LP@gemulon.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: john.naylor@postgresql.org, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Move gramparse.h to src/backend/parser
  In-Reply-To: <E1oYJbR-000FbR-LP@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox