- Boost - lists.preview.boost.org

[mpl] clang error for narrowing from unsigned int 0xffffffff to long
by Edward Diener 15 Nov '13

15 Nov '13

In the mpl bitwise.cpp test there are lines like: MPL_ASSERT_RELATION( (bitor_<_0,_ffffffff>::value), ==, 0xffffffff ); MPL_ASSERT_RELATION( (bitor_<_1,_ffffffff>::value), ==, 0xffffffff ); MPL_ASSERT_RELATION( (bitor_<_8,_ffffffff>::value), ==, 0xffffffff ); Using clang under Windows with the VC++ RTL ( clang-cl ), clang gives an error of: bitwise.cpp(43,25) : error: non-type template argument evaluates to 4294967295, which cannot be narrowed to type 'long' [-Wc++11-narrowing] MPL_ASSERT_RELATION( (bitor_<_0,_ffffffff>::value), ==, 0xffffffff ); for the bitor_<_0,_ffffffff>::value expression part since the assert_relation template takes two 'long's as its values. Is this an actual bug according to the C++11 standard ? I would have thought that an unsigned int value of 0xffffffff would fit into a long as a -1, but it sounds like the new standard is saying that since the value of 4294967295 cannot be encompassed by a long it is an error. if it is an error how should it be fixed in MPL ?

3 9

typesafe printf with variadic template
by Michael Marcin 14 Nov '13

14 Nov '13

It seems a common example for C++11 and variadic templates is a typesafe printf which is supposed to obsolete things like Boost.Format. However there doesn't seem to be one usable out of the box. If this is really a large improvement shouldn't this facility be in boost?

4 3

Any interest in hashing algorithms SHA and/or FNV1a?
by foster brereton 14 Nov '13

14 Nov '13

I have been working on implementations of the SHA and FNV-1a class of hashing algorithms. Both are header-only. SHA (Secure Hash Algorithms) Implementations for SHA-1, -224, -256, -384, and -512. It does not implement the more recent SHA-3 (Keccak) algorithm. It would not be difficult to add support for 512/224 and 512/256 if they were desired. The routines support bit-level messages, meaning they can correctly digest messages that do not end on a byte boundary. More information here: http://en.wikipedia.org/wiki/Secure_Hash_Algorithm FNV (Fowler–Noll–Vo) The header supports the FNV-1a algorithm, which has better distribution characteristics than its cousin, FNV-1. I have added support for 32-, 64-, 128-, 256-, and 1024-bit variants. This is not a cryptographically secure algorithm, however is much faster than its crypto cousins and as such is a solid algorithm for obtaining unique hash values for e.g., data structures. I have also implemented a constexpr variant of the algorithm (32-bit and 64-bit only) for const char* to further performance when needed by pushing the hash to compile-time computation. More information here: http://en.wikipedia.org/wiki/Fowler%E2%80%93Noll%E2%80%93Vo_hash_function The algorithms are currently part of the Adobe Source Libraries on GitHub: SHA: https://github.com/stlab/adobe_source_libraries/blob/sha_cleanup/adobe/sha.… (note: the master branch version needs updating to this one.) FNV-1a: https://github.com/stlab/adobe_source_libraries/blob/master/adobe/fnv.hpp Would these algorithms be of general use to the Boost community? If so I would be willing to submit them formally.

7 25

Proposed Boost.Application Library new version available.
by Renato Forti 14 Nov '13

14 Nov '13

Hi Lars, >> I don't know if this has been raised before in the discussion of previous versions, but it's customary to not call something just "Boost.Whatever" if it's not an actual accepted Boost library. Thanks for the warning! >From now on I will always use: "Proposed Boost.Application Library" >> You should probably not use the actual Boost logotype in the documentation either... I used the Quickbook to generate the documentation. Quickbook adds 'boost' logotype automatically. Is there any way I can generate the documentation using the Quickbook, that does not include the 'boost' logotype? >> ... there should be one somewhere with the text "provisional" or "proposed" superimposed on it. On the first page of documentation I have this Caution: "Caution This is not yet an official Boost C++ library. It wasn't reviewed and can't be downloaded from www.boost.org. This beta is available to boost community to know real interest and get comments for refinement. The intention is to submit library to formal review, if community think that it is interesting!" That's not enough? Thanks a lot

2 2

Boost.Application new version available.
by Renato Forti 14 Nov '13

14 Nov '13

Hi All, Last version (0.4.1) of Boost.Application are available. Documentation: <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> https://github.com/retf/Boost.Application News in this release: * Now we have a self-pipe aspect ready to use for POSIX platform. The documentation of usage: <http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/boost_applic ation/posix_specifics.html#boost_application.posix_specifics.self_pipe_> http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/boost_applica tion/posix_specifics.html#boost_application.posix_specifics.self_pipe_ The sample usage of aspect: <https://github.com/retf/Boost.Application/blob/master/libs/application/exam ple/selfpipe/selfpipe.cpp> https://github.com/retf/Boost.Application/blob/master/libs/application/examp le/selfpipe/selfpipe.cpp * Some fixes on code and docs. Please send your comments!

2 1

[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

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

Data Structure and Algorithms yet to be implemented
by Manmohit Rekhi 12 Nov '13

12 Nov '13

Hi, I would really be grateful if could get to know 1)which Data Structures and Algorithms are yet to be implemented in boost? 2)How can i get started on them? Thanking you, Manmohit Rekhi

3 2

Boost 1.55.0 released!
by Marshall Clow 12 Nov '13

12 Nov '13

Release 1.55.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains one new library and numerous enhancements and bug fixes for existing libraries. === New Libraries === • Predef: This library defines a set of compiler, architecture, operating system, library, and other version numbers from the information it can gather of C, C++, Objective C, and Objective C++ predefined macros or those defined in generally available headers, from Rene Rivera. === Known bugs with Visual Studio 2013/Visual C++ 12 === Visual Studio 2013 was released quite late in the release process, so there exist several unresolved issues. These include: • Serialization can't compile because of a missing include. • Using has_member_function_callable_with from Boost.Container's allocator_traits causes a compile error (#9332). • For several libraries overloads with intializer lists are incorrectly reported as ambiguous. This is a Visual C++ bug and it isn't clear if there's a good workaround. • In libraries such as Unordered and MultiIndex, calling overloaded functions with initializer lists can result in a compile error, with Visual C++ claiming that the overloads are ambiguous. This is a Visual C++ bug and it isn't clear if there's a good workaround. This won't affect code that doesn't use initializer lists, or uses an initializer list that doesn't require an implicit conversion (i.e. an initializer list of the container's exact value type). • Thread: ex_scoped_thread compile fails (#9333). For details, including download links, see http://www.boost.org/users/news/version_1.55.0 You can also download directly from SourceForge: http://sourceforge.net/projects/boost/files/boost/1.55.0/ To install this release on your system, see http://www.boost.org/doc/libs/release/more/getting_started/index.html Thanks, --The Boost release team Vladimir Prus Rene Rivera Marshall Clow Eric Niebler Daniel James Beman Dawes

2 2

Re: [boost] sqlpp11: SQL for C++
by Brian Wood 12 Nov '13

12 Nov '13

From: Bjorn Reese > On 11/09/2013 11:03 PM, Roland Bock wrote: >> >> * define types representing tables and columns, > > There seems to be room for improvement here. You should consider an > integration with Boost.Fusion. This way you can avoid having to build > a code generator. Hmm. If you want a second opinion, these guys http://springfuse.com are building a code generator. -- Brian Ebenezer Enterprises - So far G-d has helped us. http://webEbenezer.net

2 1

[Functional/Factory] Value factory not accepts rvalues?
by Lin, Yi-Li 12 Nov '13

12 Nov '13

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. But boost::value_factory<T>::operator() did not accept rvalue, they take lvaue reference instead. Maybe it'll be better to provide another version of operator takes const lvalue? (Additionally, use std::forward to forward universal reference in C++11?) Sample code which compiler complains: int get_value(); struct var { var( ); explicit var(int); }; void caller() { boost::value_factory<var> f; f(get_value()); }

2 2

Changes to trunk for clang using VC++RTL
by Edward Diener 12 Nov '13

12 Nov '13

I have held off making some changes to trunk in SVN for clang with VC++ RTL until Boost 1.55 was out. I can do so now based on my tests with clang but I am concerned that the changes will not be carried over to the Boost git development branch when Boost switches to git. Should I be waiting until the git changeover is made and everyone learns to deal with git and the setup for using Boost with git, or should I start making changes now and watch the regression tests cycle ? I am sure from my tests that the changes, although involved in low-level libraries like config, mpl, type_traits, will not adversely affect any other compiler and will help in testing clang using VC++ RTL for Boost as clang inches closer to full support in Windows using VC++ headers and libraries.

1 0

Re: [boost] [release][1.55.0] Visual C++ known bugs
by Daniel James 11 Nov '13

11 Nov '13

On 11 November 2013 20:40, Robert Ramey <robertmacleranramey(a)gmail.com> wrote: > > > On Monday, November 11, 2013 12:04:22 PM UTC-8, Daniel James wrote: >> >> On 11 November 2013 12:36, Sergey Cheban <s.ch...(a)drweb.com> wrote: >> > >> > Btw, what do you think about an additional SVN branch for the post-RC2 >> > VC12-related bugfixes? >> >> I just created a branch at: >> >> https://svn.boost.org/svn/boost/branches/maintenance/1_55_0 >> > > Since we've tagged the current state of the release branch with 1_55_0 do we > really have to create another branch? Can't > we just open the release branch for checkins? That would be easier. This branch is just for fixes. The release branch can have other changes, including breaking changes.

2 2

Re: [boost] [release][1.55.0] Visual C++ known bugs
by Daniel James 11 Nov '13

11 Nov '13

On 11 November 2013 21:23, Robert Ramey <robertmacleranramey(a)gmail.com> wrote: > > > On Monday, November 11, 2013 12:42:07 PM UTC-8, Daniel James wrote: >> >> On 11 November 2013 20:40, Robert Ramey <robertmac...(a)gmail.com> wrote: >> > >> > >> > On Monday, November 11, 2013 12:04:22 PM UTC-8, Daniel James wrote: >> >> >> >> On 11 November 2013 12:36, Sergey Cheban <s.ch...(a)drweb.com> wrote: >> >> > >> >> > Btw, what do you think about an additional SVN branch for the >> >> > post-RC2 >> >> > VC12-related bugfixes? >> >> >> >> I just created a branch at: >> >> >> >> https://svn.boost.org/svn/boost/branches/maintenance/1_55_0 >> >> >> > >> > Since we've tagged the current state of the release branch with 1_55_0 >> > do we >> > really have to create another branch? Can't >> > we just open the release branch for checkins? That would be easier. >> >> This branch is just for fixes. The release branch can have other >> changes, including breaking changes. > > > Soo... if we have fixes, we should check them into BOTH branches? If you want to, or just check it into release. It's a way to collect patches, make of that what you will.

1 0