From: Michael Glassford (glassfordm_at_[hidden])
Date: 2003-12-12 17:13:26
That's something I haven't looked into, but I intend to at some point.
Bronek Kozicki wrote:
> Michael Glassford <glassfordm_at_[hidden]> wrote:
>> Bronek Kozicki wrote:
>>> I guess that threads library is
>>> somewhere waiting for this thread to get started?
>> Yes, it does. If you look in thread.cpp, you'll see that the last
>> line of
>> the thread constructor (not the default constructor but the one that
>> takes a threadfunc parameter) calls param.wait(), which waits until
> Naiive solution would be to change constructor to:
> thread::thread(const function0<void>& threadfunc, bool wait = true)
> but is it safe ?
> 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