Re: PL/Perl compilation error

From: Alex Pilosov <alex(at)pilosoft(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: gilles(at)darold(dot)net, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: PL/Perl compilation error
Date: 2000-10-17 15:11:32
Message-ID: Pine.BSO.4.10.10010171106190.22422-100000@spider.pilosoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Tue, 17 Oct 2000, Tom Lane wrote:

> Gilles DAROLD <gilles(at)darold(dot)net> writes:
> >> The problem is this will break on older copies of Perl.
>
> > This problem is solved by perl itself !
>
> Yeah, it is: there is a module called Devel::PPPort that isolates
> user C code from the incompatibilities of different Perl APIs. Until
> someone gets around to submitting a proper fix using PPPort, we'll stick
> with the POLLUTE=1 solution we have now. I see no reason to install an
> incomplete solution that will fail on older Perls --- we are not in the
> business of forcing people to update their Perls.
I believe that POLLUTE should be a default. People who are using perl5.004
are definitely a minority now. 5.004 is 3 years old now...

-alex

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adam Lang 2000-10-17 15:11:34 Re: off topic
Previous Message Adam Lang 2000-10-17 15:09:51 Re: pgsql and php 3.0.16 question

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2000-10-17 15:26:43 Re: incompatible changes of PQsetdbLogin()
Previous Message Peter Eisentraut 2000-10-17 15:10:42 Re: pgsql/doc (FAQ_MSWIN INSTALL_MSWIN)