From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Cc: | Тарасов Георгий Витальевич <Tarasov-G(at)gaz-is(dot)ru> |
Subject: | Re: compiling PL/pgSQL plugin with C++ |
Date: | 2019-05-30 21:46:28 |
Message-ID: | 74481.1559252788@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
I wrote:
> I propose that we change src/tools/pginclude/cpluspluscheck so that
> it searches basically everywhere:
> -for f in `find src/include src/interfaces/libpq/libpq-fe.h src/interfaces/libpq/libpq-events.h -name '*.h' -print | \
> +for f in `find src contrib -name '*.h' -print | \
After further experimentation with that, it seems like we'll have
to continue to exclude src/bin/pg_dump/*.h from the C++ check.
pg_dump uses "public" and "namespace" as field names in various
structs, both of which are C++ keywords. Changing these names
would be quite invasive, and at least in the short run I see no
payoff for doing so.
ecpg/preproc/type.h is also using "new" as a field name, but it
looks like there are few enough references that renaming that
field isn't unreasonable.
There are various other minor issues, but they generally look
fixable with little consequence.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter J. Holzer | 2019-05-31 08:11:36 | Re: Questions about btree_gin vs btree_gist for low cardinality columns |
Previous Message | Lu, Dan | 2019-05-30 19:38:21 | Postgresql backup via LVM snapshot? |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-05-30 21:54:23 | Re: coverage additions |
Previous Message | Andres Freund | 2019-05-30 21:31:54 | Re: Ought to use heap_multi_insert() for pg_attribute/depend insertions? |