Artyom Beilis wrote
I want to add my $0.02
Boost Thread is on the one hand one of the center pices of the Boost library as threading is very important part of many applications, on the other hand it is one of the libraries that had broken the interfaces, APIs semantics so many times that to be honest I'm not sure how can I recommend it for any organization or product to use.
I remember that I had severe problems in one of my project because of some API that was broken between 1.33 and 1.35 and later (IIRC) 1.38
For this reason I had brought my own threading library for one of my projects that is sufficient subset of Boost.Thread but I at least know that it works as I expect.
Now I'm quite surprised that terminate is used instead of detach...
If I was continue to use Boost.Thread it would clearly broke one
of my applications as I relay on this behavior at several points.
So please... do us a favor - stop breaking Boost libraries.
Boost developers tend to forget that there are actually users who relay on these libraries and they finally got stuck with prehistoric/unsupported boost versions.
This is not my case. I have taken in consideration the users and provide a smooth transition for them. Maybe my approach was wrong, but not my intention. Best, Vicente -- View this message in context: http://boost.2283326.n4.nabble.com/thread-to-std-or-not-to-std-tp4640499p464... Sent from the Boost - Dev mailing list archive at Nabble.com.