From: Anthony Williams (anthony.ajw_at_[hidden])
Date: 2008-05-28 06:47:31
Johan Torp <johan.torp_at_[hidden]> writes:
> Peter Dimov-5 wrote:
>>> IIRC, windows thread ids can be re-used. That is, if you stop a thread X
>>> later start a thread Y they might get the same thread id. Is this the
>>> with boost.thread? What about the standard? It states:
>>> "An object of type thread::id provides a unique identifier for each
>>> of execution and a single distinct value for all thread objects that do
>>> represent a thread of execution ([thread.threads.class]). Each thread of
>>> execution has a thread::id that is not equal to the thread::id of other
>>> threads of execution and that is not equal to the thread::id of
>>> objects that do not represent threads of execution."
> I also expect re-use will mean users have to re-implement "unique_thread_id"
> and some really difficult-to-fix bugs for people who do not think about it.
> OTOH, I see some value in that std::thread::id are the same as window's
> thread ids when you're debugging and post-mortem debugging.
> Since issue #783 is marked as ready, does it mean it is closed and the
> proposed text has been added to the standard? I was hoping re-use would be
> disallowed :/
No, it means it will be voted on at the June meeting.
-- Anthony Williams | Just Software Solutions Ltd Custom Software Development | http://www.justsoftwaresolutions.co.uk Registered in England, Company Number 5478976. Registered Office: 15 Carrallack Mews, St Just, Cornwall, TR19 7UL
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk