Skip site navigation (1) Skip section navigation (2)

Re: libpgtcl

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Rudolf Weber <rfweber(at)bluewin(dot)de>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: libpgtcl
Date: 2000-06-14 16:32:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
I will back it out then.

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I am happy to back it out.  Comments?  [Let me give the author time to
> > respond.]
> >> I just looked at this yesterday and I wonder why one would want to do
> >> this. The libpgtcl build works perfectly fine and it doesn't even link
> >> with tcl, so there's little reason to "integrate the tcl-spec" into
> >> things.
> My thoughts were pretty much the same as Peter's.  We use the Tcl
> compiler and switches for pltcl because it was the path of least
> resistance for linking in  But the libpgtcl interface
> doesn't do that, and has not been a source of portability problems
> --- and it's been around for a lot longer than pltcl (we don't
> really know that pltcl's scheme works for everyone).  So changing
> the way we build libpgtcl seems to me to be a risky change for
> little or no benefit.
> My inclination is to sail along with the two different build
> approaches for a few releases and see what sort of portability
> problems we hear about.  Perhaps in a year or so it'll make sense to
> unify the handling of libpgtcl and pltcl, but right now I'm dubious.
> 			regards, tom lane

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2000-06-14 19:52:54
Subject: Re: libpgtcl
Previous:From: Tom LaneDate: 2000-06-14 16:14:49
Subject: Re: libpgtcl

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group