From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: mb and ecpg regression tests |
Date: | 2007-05-17 16:40:30 |
Message-ID: | 895.1179420030@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Back when we were thinking of supporting MSVC builds, we thought that
> everything would need to be a C program, and so we rewrote the main
> regression script in C, for example. However, now we have a build system
> for MSVC we can see that its main infrastructure is in fact perl, so I
> think what we need to do is to convert the MBCS and ECPG regression
> drivers to perl rather than C - which should be far, far simpler task.
I disagree with this for ecpg because (a) it would be a capability
regression from the point of view of anyone building a non-perl-enabled
build on Unix, and (b) we already have the C regression driver, why
can't we re-use or adapt it for ecpg instead of writing and debugging
and maintaining an entirely new set of test infrastructure?
For the MBCS stuff I don't care, since no one runs that on a regular
basis anyway (or should need to...)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-05-17 16:56:55 | Re: UTF8MatchText |
Previous Message | Cui Shijun | 2007-05-17 16:33:11 | Re: Lack of urgency in 8.3 reviewing |