From: Daniel James (daniel_at_[hidden])
Date: 2005-03-13 12:31:08
Jeff Garland wrote:
>>However, the fact remains that the date_time library
>>uses non-thread safe functions in a way that cannot be
>>controlled by the user.
> Yes, as I said earlier it's on the todo list for 1.33. BTW, worst case is
> that we could make our own localtime_r function in the clock classes.
I'm not sure about this, but I think that the windows multi-threaded C
libraries use thread specific storage for functions like 'localtime'. So
on that platfrom, they're okay.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk