boost:thread documentation for 1.50 does not mention BOOST_THREAD_WAIT_BUG

[Viatcheslav.Sysoltsev@…]

As I understood from the trac ticket ​https://svn.boost.org/trac/boost/ticket/7089 and sources for boost 1.50, boost::thread 1.50 implicitly adds 100 ms to the sleep time of boost::this_thread::sleep and boost::thread_sleep on linux. If the fix for 7089 cannot be backported into 1.50, the warning about broken functionality must be present in the documentation for 1.50.

[viboes]

I don't remember which problem BOOST_THREAD_WAIT_BUG tried to fix. Currently this is not used any more. If you know of a problem please, be free to signal it here.

[anonymous]

BOOST_THREAD_WAIT_BUG was a workaround for the ticket 6130, which describes some strange OS problem. If possible, please remove the workaround from 1.50 issue/branch (and where else it has been applied), it breaks the functionality.

[viboes]

Replying to anonymous:

BOOST_THREAD_WAIT_BUG was a workaround for the ticket #6130, which describes some strange OS problem. If possible, please remove the workaround from 1.50 issue/branch (and where else it has been applied), it breaks the functionality.

Thanks for the ticket number. What do you mean by "remove the workaround from 1.50 issue/branch"? Boost doesn't maintain specific release branches.

[anonymous]

I mean the people, which distribution happens to have 1.50 release should be aware, that the mentioned functionality is broken in this release. That's why the problem report was filed agains documentation.

[viboes]

Replying to anonymous:

I mean the people, which distribution happens to have 1.50 release should be aware, that the mentioned functionality is broken in this release. That's why the problem report was filed agains documentation.

Thanks for the clarification. I didn't know that the documentation for a release could be updated.

[anonymous]

Bugs in a library's documentation should be filed against the library, not Documentation. 'Documentation' is for general documentation bugs.

If you want to update website documentation, you need to add files to the appropriate location under ​https://svn.boost.org/svn/boost/website/public_html/live/doc/fixes/

[viboes]

Replying to anonymous:

Bugs in a library's documentation should be filed against the library, not Documentation. 'Documentation' is for general documentation bugs.

If you want to update website documentation, you need to add files to the appropriate location under ​https://svn.boost.org/svn/boost/website/public_html/live/doc/fixes/

I didn't know that we could add patches to the library documentation. Please, could you point me to a link where the procedure is explained? Should I generate the html documentation or it is enough to provide the qbk and Jamfile files?

[Daniel James]

It isn't explained anywhere because I make it up as I go along. Maintaining documentation would be too much work. Basically, I have a directory on the website (the fixes directory I linked to), and if you place a html file in the appropriate location within it, it will be served instead of the one from the distribution. If you look in the directory I linked to, the layout should be obvious. But if you get it wrong, I'll fix it up.

But if that's too hard for you, can you let me know what you want to change (giving full text).