Re: Not *quite* there on ecpg fixes - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Not *quite* there on ecpg fixes
Date
Msg-id 26087.1191521534@sss.pgh.pa.us
Whole thread Raw
In response to Re: Not *quite* there on ecpg fixes  (Michael Meskes <meskes@postgresql.org>)
Responses Re: Not *quite* there on ecpg fixes
List pgsql-hackers
Michael Meskes <meskes@postgresql.org> writes:
> On Thu, Oct 04, 2007 at 12:35:29PM -0400, Alvaro Herrera wrote:
>> The libpq exports.txt has spaces, not tabs, as separators.  In fact, if
>> you see the .def files you notice that the generated files for ecpg are
>> all wrong.

> Right, that's it. 

I see that libpq manufactures three different .def files, whereas the
ecpg code is only making two.  Is this OK or an oversight?  I'm not
clear on the reason for the two different "MSVC" .def files in libpq.

Also, do we actually care about supporting Borland builds of ecpg ---
maybe we don't need the 'b' versions for ecpg?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Michael Meskes
Date:
Subject: Re: Not *quite* there on ecpg fixes
Next
From: Tom Lane
Date:
Subject: Re: Not *quite* there on ecpg fixes