Clean up PL/Perl's handling of the _() macro.
Perl likes to redefine the _() macro:
#ifdef CAN_PROTOTYPE
#define _(args) args
#else ...
There was lots not to like about the way we dealt with this before:
1. Instead of taking care of the conflict centrally in plperl.h, we
expected every one of its ever-growing number of includers to do so.
This is duplicative and error-prone in itself, plus it means that
plperl.h fails to meet the expectation of being compilable standalone,
resulting in macro-redefinition warnings in cpluspluscheck.
2. We left _() with its Perl definition, meaning that if someone tried
to use it in any Perl-related extension, it would silently fail to
provide run-time translation. I don't see any live bugs of this ilk,
but it's clearly a hard-to-notice bug waiting to happen.
So fix that by centralizing the cleanup logic, making it match what
we're already doing for other macro conflicts with Perl. Since we only
expect plperl.h to be included by extensions not core code, we should
redefine _() as dgettext() not gettext().
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/032627ee7837f0baa539df7247e003dbaded2c90
Modified Files
--------------
contrib/hstore_plperl/hstore_plperl.c | 4 +---
contrib/jsonb_plperl/jsonb_plperl.c | 3 ---
src/pl/plperl/SPI.xs | 3 ---
src/pl/plperl/Util.xs | 4 +---
src/pl/plperl/plperl.c | 3 ---
src/pl/plperl/plperl.h | 15 +++++++++++++++
6 files changed, 17 insertions(+), 15 deletions(-)