Re: libpq++ - Mailing list pgsql-interfaces

From Justin Banks
Subject Re: libpq++
Date
Msg-id 15085.24280.868910.556829@dervish.mr-boo.com
Whole thread Raw
In response to Re: libpq++  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Re: libpq++
List pgsql-interfaces
>>>>> "Bruce" == Bruce Momjian <pgman@candle.pha.pa.us> writes:
 Bruce> I am not so much the libpq++ maintainer as the one who applies Bruce> people's patches.  There is an interfaces
listthat 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
overthere.
 

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 ;)

-justinb

-- 
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




pgsql-interfaces by date:

Previous
From: Justin Banks
Date:
Subject: Re: libpq++
Next
From: Sanjay Arora
Date:
Subject: Null values where they should not be...HELP Please!!