|
Boost : |
From: Michael Glassford (glassfordm_at_[hidden])
Date: 2004-02-18 06:58:00
"Russell Hind" <rhind_at_[hidden]> wrote in message
news:c0v6vs$5mu$1_at_sea.gmane.org...
> Michael Glassford wrote:
> > It is no longer supported: the tss class requires Boost.Thread to
be
> > in a dll to be able to clean up after itself properly (i.e. to
prevent
> > leaks). It would be possible to build a version that doesn't
include
> > support for this, but in a future version of Boost.Thread
(currently
> > in the thread_dev branch of CVS), I believe several new features
> > depend on this support being available so it may not be worthwhile
to
> > do so.
> >
>
> Hi Michael, I realise this wouldn't be recommended practice, but
would
> these leaks only occur when resources (by that I mean mutexes,
threads,
> 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
about
> leaks as they wouldn't be happening while the application is
running,
> only at the end when the OS should clean up anyway? If so, then I
am
> 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.
> Thanks
>
> Russell
>
> _______________________________________________
> Unsubscribe & other changes:
http://lists.boost.org/mailman/listinfo.cgi/boost
>
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk