Re: libpq's pollution of application namespace - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: libpq's pollution of application namespace
Date
Msg-id 200606142223.k5EMNaq06230@candle.pha.pa.us
Whole thread Raw
In response to Re: libpq's pollution of application namespace  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: libpq's pollution of application namespace  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: libpq's pollution of application namespace  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Thread added to TODO:
> >         o Properly mark all libpq-exported functions with "PQ"
> 
> Is that still relevant?  I thought we'd done as much as we intended
> to do in that specific direction.  What would make sense to work on

Oh, OK.

> is making the build step that strips not-officially-exported symbols
> work on more platforms.

Uh, well, I had some patches in the patch queue to go in that direction,
but I thought the conclusion in that thread was that it wasn't worth it.

--  Bruce Momjian   http://candle.pha.pa.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: The argument for reinstating --as-needed
Next
From: Andrew Dunstan
Date:
Subject: Re: CSV mode option for pg_dump