pgsql: Prevent Perl from introducing a possibly-incompatible definition

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Prevent Perl from introducing a possibly-incompatible definition
Date: 2007-11-22 17:47:46
Message-ID: 20071122174746.F30617540F0@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Prevent Perl from introducing a possibly-incompatible definition of type
"bool" into plperl.c. This has always been a hazard since Perl allows a
platform-specific choice to define bool as int rather than char, but
evidently this didn't happen on any platform we support ... until OS X 10.5.
Per report from Brandon Maust.

Back-patch as far as 8.0 --- a bit arbitrary, but it seems unlikely anyone
will be trying to port 7.x onto new platforms.

Tags:
----
REL8_0_STABLE

Modified Files:
--------------
pgsql/src/pl/plperl:
plperl.c (r1.67.4.7 -> r1.67.4.8)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/plperl.c?r1=1.67.4.7&r2=1.67.4.8)
spi_internal.h (r1.4 -> r1.4.4.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/spi_internal.h?r1=1.4&r2=1.4.4.1)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2007-11-22 17:51:39 pgsql: Add more comments about thousands separator handling.
Previous Message Tom Lane 2007-11-22 17:47:40 pgsql: Prevent Perl from introducing a possibly-incompatible definition