Message-ID: <35D0763C.C5D2DBF8@trust.ee>
Date: Tue, 11 Aug 1998 19:50:04 +0300
From: Hannu Krosing <hannu@trust.ee>
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: pgsql-interfaces@postgreSQL.org, Goran Thyni <goran@bildbasen.se>
Subject: Re: [INTERFACES] Re: thread-safe libpq and DBD::Pg
References: <26919.902847103@sss.pgh.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Tom Lane wrote:
> 
> Goran Thyni <goran@bildbasen.se> writes:
> > * A "pure perl"-interface is useful for
> >       - systems without decent C-compiler
> >       - systems not supported by libpq
> >           (there is already a pure TCL interface, isn't it?)
> 
> I agree that a "pure Perl" or "pure Tcl" front end would be more
> easily portable than what we have.  It'd probably be slower, but
> maybe not so much slower as to be a problem.

I once did an incomplete "pure Python" PgSQL (v6.2) interface, which ran 
on both Linux and Win32. It was not that much slower.

> The present libpgtcl is NOT pure Tcl --- it is a C-coded Tcl extension,
> besides which it is layered on top of libpq.
> 
> I think I remember someone speculating about writing a pure Tcl
> front end by programming directly to the socket-level FE/BE interface,
> but I haven't heard about any results.

I've got the impression that there is currently a pure Tcl interface 
as well that some use with pgAccess on win32.

Hannu