November 2013 - Boost - lists.preview.boost.org

[1.55] PDF Documentation build available.
by John Maddock 14 Nov '13

14 Nov '13

The final PDF documentation build for Boost-1.55 is now available at https://sourceforge.net/projects/boost/files/boost-docs/1.55.0/ As ever this only contains documentation for the subset of Boost libraries that use quickbook/boostbook/docbook based documentation. Enjoy! John.

1 0

Is there any interest in a library which provides Application Environment using Aspect Based Design?
by Renato Forti 13 Nov '13

13 Nov '13

Hello everyone, I already asked that question, but how the library has changed a lot since the last inquiry. "Is there any interest in a library which provides Application Environment using Aspect Based Design?" Docs: <http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/index.html> http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/index.html Code: https://github.com/retf/Boost.Application Please expose your interest!

2 1

[range] fat iterators?
by Eric Niebler 13 Nov '13

13 Nov '13

I wrote an article describing the "fat" std::istream_iterator and how it can be slimmed down by giving it an owning istream_range[1]. I see there already is an istream_range in Boost.Range, but it suffers from the fat-iterator problem I describe there. Is there a compelling reason why the implementation of boost::istream_range shouldn't be changed to be more like the one I describe? Also, as a commented pointed out, the same problem exists for the filtered range and the transformed range, too. The trick, of course, will be keeping intermediate temporary ranges alive long enough to avoid lifetime issues when we chain adaptors and assign the result to a local variable. I think a range library that's sensitive to the value category of range objects and makes copies of rvalue ranges would solve this problem. Thoughts? Is it time for Boost.Range 3.0? [1]: http://ericniebler.com/2013/11/07/input-iterators-vs-input-ranges -- Eric Niebler Boost.org http://www.boost.org

11 27

Re: [boost] [Functional/Factory] Value factory not accepts rvalues?
by THOMAS JORDAN 13 Nov '13

13 Nov '13

Lin, Yi-Li wrote: > I found that boost::value_factory did not accept rvalues > in some case. > In my case, temporary value is produced and passed to > value factory directly. The documentation for Boost Functional/Factory states: 'For technical reasons the arguments to the function objects have to be LValues. A factory that also accepts RValues can be composed using the boost::forward_adapter or boost::bind.' Your suggestion of using const lvalue (passing in non-const reference wrappers where needed) seems to be the workaround for the C++03 perfect forwarding problem that was employed by Boost smart_ptr::make_shared, not sure why Functional/Factory took a different approach? Tom.

1 0

forget delete detail/limits.hpp ?
by Akira Takahashi 13 Nov '13

13 Nov '13

Hi, I found boost/detail/limits.hpp file in Boost 1.55.0. However, already deleted from trunk. forget delete the file? -- >>======================== Akira Takahashi mailto:faithandbrave@gmail.com site: https://sites.google.com/site/faithandbrave/about/en

1 0

compile thread(boost1.55) fail on vc7.1
by shada 13 Nov '13

13 Nov '13

*bjam toolset=msvc-7.1 link=static threading=multi runtime-link=static --with-thread --with-chrono --with-date_time --includedir=hpp stage*>err.txt Component configuration: - atomic : not building - chrono : building - context : not building - coroutine : not building - date_time : building - exception : not building - filesystem : not building - graph : not building - graph_parallel : not building - iostreams : not building - locale : not building - log : not building - math : not building - mpi : not building - program_options : not building - python : not building - random : not building - regex : not building - serialization : not building - signals : not building - system : not building - test : not building - thread : building - timer : not building - wave : not building ...patience... ...patience... ...found 1497 targets... ...updating 6 targets... compile-c-c++ bin.v2\libs\thread\build\msvc-7.1\debug\link-static\runtime-link-static\threading-multi\win32\thread.obj thread.cpp boost\functional\hash\hash.hpp(32) : warning C4616: #pragma warning : 警告编号“6295”超出范围，必须在“4001”和“4999“之间 boost\thread\future.hpp(1488) : error C2039: “make_future_async_shared_state” : 不是“boost::detail”的成员 boost\thread\future.hpp(1638) : 参见对正在编译的类模板实例化“boost::unique_future<R>”的引用 boost\thread\future.hpp(1492) : error C2039: “make_future_deferred_shared_state” : 不是“boost::detail”的成员 boost\thread\future.hpp(1683) : error C2039: “make_future_async_shared_state” : 不是“boost::detail”的成员 boost\thread\future.hpp(1807) : 参见对正在编译的类模板实例化“boost::unique_future<boost::unique_future<R2>>”的引用 boost\thread\future.hpp(1687) : error C2039: “make_future_deferred_shared_state” : 不是“boost::detail”的成员 boost\thread\future.hpp(1490) : error C2951: 模板声明只能在全局或者命名空间范围内使用 boost\thread\future.hpp(3695) : 参见对正在编译的类模板实例化“boost::unique_future<R>”的引用 with [ R=void ] boost\thread\future.hpp(1497) : error C2955: “boost::unique_future” : 使用类模板需要模板参数列表 boost\thread\future.hpp(1638) : 参见“boost::unique_future”的声明 boost\thread\future.hpp(1497) : error C2955: “boost::unique_future” : 使用类模板需要模板参数列表 boost\thread\future.hpp(1638) : 参见“boost::unique_future”的声明 boost\thread\future.hpp(1497) : error C2146: 语法错误 : 缺少“)”(在标识符“a_future”的前面) boost\thread\future.hpp(1497) : error C2146: 语法错误 : 缺少“;”(在标识符“a_future”的前面) boost\thread\future.hpp(1497) : error C2377: “boost::unique_future<R>::future_ptr” : 重定义；typedef 不能由任何其他符号重载 with [ R=void ] boost\thread\future.hpp(1454) : 参见“boost::unique_future<R>::future_ptr”的声明 with [ R=void ] boost\thread\future.hpp(1497) : error C2059: 语法错误 : “)” boost\thread\future.hpp(1498) : error C2065: “a_future” : 未声明的标识符 boost\thread\future.hpp(1499) : fatal error C1903: 无法从以前的错误中恢复；正在停止编译 call "C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\vc7\bin\vcvars32.bat" >nul cl /Zm800 -nologo @"bin.v2\libs\thread\build\msvc-7.1\debug\link-static\runtime-link-static\threading-multi\win32\thread.obj.rsp" ...failed compile-c-c++ bin.v2\libs\thread\build\msvc-7.1\debug\link-static\runtime-link-static\threading-multi\win32\thread.obj... ...skipped <pbin.v2\libs\thread\build\msvc-7.1\debug\link-static\runtime-link-static\threading-multi>libboost_thread-vc71-mt-sgd-1_55.lib for lack of <pbin.v2\libs\thread\build\msvc-7.1\debug\link-static\runtime-link-static\threading-multi>win32\thread.obj... ...skipped <pstage\lib>libboost_thread-vc71-mt-sgd-1_55.lib for lack of <pbin.v2\libs\thread\build\msvc-7.1\debug\link-static\runtime-link-static\threading-multi>libboost_thread-vc71-mt-sgd-1_55.lib... compile-c-c++ bin.v2\libs\thread\build\msvc-7.1\release\link-static\runtime-link-static\threading-multi\win32\thread.obj thread.cpp boost\functional\hash\hash.hpp(32) : warning C4616: #pragma warning : 警告编号“6295”超出范围，必须在“4001”和“4999“之间 boost\thread\future.hpp(1488) : error C2039: “make_future_async_shared_state” : 不是“boost::detail”的成员 boost\thread\future.hpp(1638) : 参见对正在编译的类模板实例化“boost::unique_future<R>”的引用 boost\thread\future.hpp(1492) : error C2039: “make_future_deferred_shared_state” : 不是“boost::detail”的成员 boost\thread\future.hpp(1683) : error C2039: “make_future_async_shared_state” : 不是“boost::detail”的成员 boost\thread\future.hpp(1807) : 参见对正在编译的类模板实例化“boost::unique_future<boost::unique_future<R2>>”的引用 boost\thread\future.hpp(1687) : error C2039: “make_future_deferred_shared_state” : 不是“boost::detail”的成员 boost\thread\future.hpp(1490) : error C2951: 模板声明只能在全局或者命名空间范围内使用 boost\thread\future.hpp(3695) : 参见对正在编译的类模板实例化“boost::unique_future<R>”的引用 with [ R=void ] boost\thread\future.hpp(1497) : error C2955: “boost::unique_future” : 使用类模板需要模板参数列表 boost\thread\future.hpp(1638) : 参见“boost::unique_future”的声明 boost\thread\future.hpp(1497) : error C2955: “boost::unique_future” : 使用类模板需要模板参数列表 boost\thread\future.hpp(1638) : 参见“boost::unique_future”的声明 boost\thread\future.hpp(1497) : error C2146: 语法错误 : 缺少“)”(在标识符“a_future”的前面) boost\thread\future.hpp(1497) : error C2146: 语法错误 : 缺少“;”(在标识符“a_future”的前面) boost\thread\future.hpp(1497) : error C2377: “boost::unique_future<R>::future_ptr” : 重定义；typedef 不能由任何其他符号重载 with [ R=void ] boost\thread\future.hpp(1454) : 参见“boost::unique_future<R>::future_ptr”的声明 with [ R=void ] boost\thread\future.hpp(1497) : error C2059: 语法错误 : “)” boost\thread\future.hpp(1498) : error C2065: “a_future” : 未声明的标识符 boost\thread\future.hpp(1499) : fatal error C1903: 无法从以前的错误中恢复；正在停止编译 call "C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\vc7\bin\vcvars32.bat" >nul cl /Zm800 -nologo @"bin.v2\libs\thread\build\msvc-7.1\release\link-static\runtime-link-static\threading-multi\win32\thread.obj.rsp" ...failed compile-c-c++ bin.v2\libs\thread\build\msvc-7.1\release\link-static\runtime-link-static\threading-multi\win32\thread.obj... ...skipped <pbin.v2\libs\thread\build\msvc-7.1\release\link-static\runtime-link-static\threading-multi>libboost_thread-vc71-mt-s-1_55.lib for lack of <pbin.v2\libs\thread\build\msvc-7.1\release\link-static\runtime-link-static\threading-multi>win32\thread.obj... ...skipped <pstage\lib>libboost_thread-vc71-mt-s-1_55.lib for lack of <pbin.v2\libs\thread\build\msvc-7.1\release\link-static\runtime-link-static\threading-multi>libboost_thread-vc71-mt-s-1_55.lib... ...failed updating 2 targets... ...skipped 4 targets...

7 8

Patch in Ticket #9212 (Broken links to C++ standard papers)
by Michel Morin 13 Nov '13

13 Nov '13

Jonathan Wakely pointed out "Broken links to C++ standard papers" issue and attached a patch in #9212. ( https://svn.boost.org/trac/boost/ticket/9212 ) Though this patch is a large Boost-wide patch, it's very simple so I think someone can commit it to every library at once. Regards, Michel

4 9

can i make two io_service::strand instance whith same one io_service instance?
by shada 13 Nov '13

13 Nov '13

can i make two io_service::strand instance whith same one io_service instance?

2 1

[1.55][log] Last minute bug fix
by Andrey Semashev 12 Nov '13

12 Nov '13

Hi, Is it too late for a fix in Boost.Log in 1.55? Here's the commit: https://svn.boost.org/trac/boost/changeset/86600 This fixes garbage output when using dump() manipulator on CPUs with AVX2 support. The bug didn't appear on any of our testers because apparently none of them have Haswell CPUs. I tested this change locally on Linux, gcc 4.8, but it should be valid on all platforms. If it's too late already then maybe a note with the patch in the release notes would be possible?

2 5

[release][1.55.0] Release Notes Additions
by Tom Kent 12 Nov '13

12 Nov '13

I noticed that the list of compilers tested did not include msvc-8.0, it should be added to the list. I believe it got as much testing as 9.0. Also, could we add a link below the download section for the windows binaries on sourceforge? https://sourceforge.net/projects/boost/files/boost-binaries/1.55.0/ Thanks, Tom

3 3