From: Michael Glassford (glassfordm_at_[hidden])
Date: 2004-02-18 06:58:00
"Russell Hind" <rhind_at_[hidden]> wrote in message
> Michael Glassford wrote:
> > It is no longer supported: the tss class requires Boost.Thread to
> > in a dll to be able to clean up after itself properly (i.e. to
> > leaks). It would be possible to build a version that doesn't
> > support for this, but in a future version of Boost.Thread
> > in the thread_dev branch of CVS), I believe several new features
> > depend on this support being available so it may not be worthwhile
> > do so.
> Hi Michael, I realise this wouldn't be recommended practice, but
> these leaks only occur when resources (by that I mean mutexes,
> conditions etc) deleted?
In current versions of the library, the leaks I'm referring to would
only happen if you actually used the boost::tss class.
> As I've said, I create all needed objects at
> application startup and free them at exit, so I'm not so worried
> leaks as they wouldn't be happening while the application is
> only at the end when the OS should clean up anyway? If so, then I
> willing to risk running the thread library as a static lib still.
Yes, this is certainly possible. I do something very similar myself in
one application I work on, and it works quite well.
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk