| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, decibel <decibel(at)decibel(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Testing plperl<->plperlu interaction |
| Date: | 2010-01-09 02:43:34 |
| Message-ID: | 4B47ED56.7040509@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> Tom Lane wrote:
>>
>>> Also, some commentary connecting this test to plperl.c's support for
>>> two interpreters would be a good thing.
>>>
>
>
>> ITYM in the .sql file(s)?
>>
>
> No, the test in the makefile is what seems to need a comment. It
> doesn't have to be much. I was thinking something like
>
> # if Perl can support two interpreters, test plperl-and-plperlu cases
> ifeq ($(shell $(PERL) -V:usemultiplicity), usemultiplicity='define';)
>
OK
> BTW, what about the MSVC scripts?
>
Yes, I will fix vcregress.pl.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2010-01-09 02:47:01 | Re: Initial refactoring of plperl.c - updated |
| Previous Message | Andrew Dunstan | 2010-01-09 02:40:50 | pgsql: Tidy up and refactor plperl.c. |