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

Re: libpq++

From: Justin Banks <justinb(at)mr-boo(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: justinb(at)tricord(dot)com, PostgreSQL-interfaces <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: libpq++
Date: 2001-04-30 12:53:02
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
>>>>> "Bruce" == Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:

  Bruce> I am not so much the libpq++ maintainer as the one who applies
  Bruce> people's patches.  There is an interfaces list that would love to
  Bruce> hear about your work.  I am CC'ing them on this.  We certainly need
  Bruce> libpq++ improvements.  If you would prefer not to deal with the
  Bruce> interfaces list, send something to me and I will send it over there.

As one would have expected, I've found a problem. The c++ std. says that
Automatic objects are not destroyed as a result of calling exit(), and so, a
automatic PgDatabase in main() (or most anywhere, actually), would not have
it's destructor called during an exit(), thereby leaving junk shm. segments
around. I'm not sure that an atexit can be called on a member function with no 
argument, so I'll do some experimenting with macros and temporary block
insertion. Better ideas welcome ;)


Justin Banks @ home
'We have no intention of shipping another bloated operating system and 
forcing that down the throats of our Windows customers'
  -- Paul Maritz, Microsoft Group Vice President

In response to

  • Re: libpq++ at 2001-04-29 20:04:49 from Bruce Momjian


pgsql-interfaces by date

Next:From: Constantin TeodorescuDate: 2001-04-30 13:55:02
Subject: MULTIPLE OUTER JOIN SYNTAX :-( can't quess it
Previous:From: Sandro DentellaDate: 2001-04-30 08:56:00
Subject: function returning NULL?

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