November 2013 - Boost - lists.boost.org

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 13 Nov '13

13 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

Re: [boost] [TypeIndex] Peer review period for library acceptance begins, ending Thurs 21st Nov
by Antony Polukhin 12 Nov '13

12 Nov '13

2013/11/13 Niall Douglas <s_sourceforge(a)nedprod.com> <...> > On 12 Nov 2013 at 11:59, Robert Ramey wrote: > > > On Tuesday, November 12, 2013 11:34:27 AM UTC-8, Niall Douglas wrote: > > > > > Boost community feedback is requested for the formal peer review of > > > the TypeIndex library by Antony Polukhin. Feedback requested > > > includes ... > > > > > > The above phrasing is a little unclear to me. Is this is a formal review > of > > the library? > Yes, it's a formal review. > > I've just glanced over the documentation but I do have a couple of > > questions. > > > > The serialization library contains a component "extended_typeinfo". Am I > > correct > > in my understanding that this component is meant to address the same > > issues that extended_typeinfo does? If so, how are the two solutions > > different? > In short: * extended_typeinfo is not compatible with std::type_info and is hard to use * TypeIndex is a correctly working std::type_info that does not require RTTI + has other bonuses * detail/sp_typeinfo.hpp implements part of TypeIndex functionality, without workarounds for compiler issues Longer description: Serialization library is created to make a storeable in archive and portable between compilers type identifications. It's interface is not close to the interface of Standard Library, it requires A LOT of code to make typeids work (see example at http://www.boost.org/doc/libs/1_55_0/boost/serialization/extended_type_info… ) TypeIndex is designed to be simple, fast and lightweight. It's a drop-in replacement for std::type_info with big set of workarounds for issues of different compilers and an extension to get human readable type names + it contains a C++11 type_index class and works without RTTI. It does not require user's support code to work. Take a look at this page: http://apolukhin.github.io/type_index/boost_typeindex/getting_started.htmlto see how Standard Library classes and methods are mapped to the TypeIndex ones. TypeIndex is close to detail/sp_typeinfo.hpp (it's just a very very enchanted sp_typeinfo that does not adds macro, embeds workarounds and has interface of std::type_info + other features from paragraph above) -- Best regards, Antony Polukhin

1 0

[1.55] [uuid] Docs header says 'development version' on the website
by Andrey Semashev 12 Nov '13

12 Nov '13

Hi, On the website, Boost.UUID docs have a header that says that these docs are for the 'development version of boost': http://www.boost.org/doc/libs/1_55_0/libs/uuid/uuid.html I looked at a couple other libraries and the header is not displayed, so it's probably Boost.UUID specific. Does anyone know what could be the problem?

2 3

[multi_index] multiple definition errors since 86597
by Jürgen Hunold 12 Nov '13

12 Nov '13

Hi, revision 86597 changed boost/multi_index/detail/bucket_array.hpp Add were: static const std::size_t sizes[]; static const std::size_t sizes_length; member variables, initialised with +template<> +const std::size_t bucket_array_base<true>::sizes[]={ + BOOST_PP_SEQ_ENUM(BOOST_MULTI_INDEX_BA_SIZES) +template<> +const std::size_t bucket_array_base<true>::sizes_length= + sizeof(bucket_array_base<true>::sizes)/ + sizeof(bucket_array_base<true>::sizes[0]); + Now gcc (4.8.1) reports multiple definition errors when using multi_index in different translation units: file1.cpp.o:(.rodata+0x0): multiple definition of `boost::multi_index::detail::bucket_array_base<true>::sizes_length' file2.cpp.o:(.rodata+0x0): first defined here file1.cpp.o:(.rodata+0x20): multiple definition of `boost::multi_index::detail::bucket_array_base<true>::sizes' file2.cpp.o:(.rodata+0x20): first defined here CMakeFiles/graph_test.dir/main.cpp.o:(.rodata+0x0): multiple definition of `boost::multi_index::detail::bucket_array_base<true>::sizes_length' file2.cpp.o:(.rodata+0x0): first defined here file3.o:(.rodata+0x20): multiple definition of `boost::multi_index::detail::bucket_array_base<true>::sizes' file2.cpp.o:(.rodata+0x20): first defined here According to http://stackoverflow.com/questions/1553854/template-static-variable and my current c++ template knowledge, those instantiation belong to a .cpp file to avoid this. This does not work for a header-only library, of course. The current test suite does not catch this because it only contains single file tests. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold(a)gmx.eu ! Germany

2 2