- Boost - lists.preview.boost.org

[1.68.0 Beta1 RC1][iostreams][vs2017 preview] seekpos is not a member of std::pos
by Mateusz Loskot 07 Jul '18

07 Jul '18

Hi, I'm trying to build some of Boost libraries with the very latest VS 2017 Version 15.8.0 Preview 3.0 I've changed project-config.jam to point msvc-14.1 to the corresponding CL.EXE ``` using msvc : 14.1 : "c:\Program Files (x86)\Microsoft Visual Studio\Preview\Professional\VC\Tools\MSVC\14.15.26608\bin\HostX64\x64\cl.EXE" ; ``` In "x64 Native Tools Command Prompt for VS 2017 Preview", I do ``` .\bootstrap.bat b2 -j8 toolset=msvc-14.1 address-model=64 variant=release --with-iostreams ... compile-c-c++ bin.v2\libs\iostreams\build\msvc-14.1\release\address-model-64\link-static\threading-multi\file_descriptor.obj file_descriptor.cpp .\boost/iostreams/positioning.hpp(96): error C2039: 'seekpos': is not a member of 'std::fpos<_Mbstatet>' c:\Program Files (x86)\Microsoft Visual Studio\Preview\Professional\VC\Tools\MSVC\14.15.26608\include\iosfwd(132): note: see declaration of 'std::fpos<_Mbstatet>' ``` Is this expected? Shouldn't this be fixed by https://github.com/boostorg/iostreams/pull/57 ? Or the PR has not made it into the master? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

2 4

[Boost PP] MSVC PP Updated Info
by degski 07 Jul '18

07 Jul '18

More info <https://blogs.msdn.microsoft.com/vcblog/2018/07/06/msvc-preprocessor-progre…> . degski -- *"If something cannot go on forever, it will stop" - Herbert Stein*

1 0

[release] Boost 1.68.0 Beta 1 Release Candidate 1
by Marshall Clow 07 Jul '18

07 Jul '18

The release candidates for the first 1.68.0 beta release are now available at: <https://dl.bintray.com/boostorg/beta/1.68.0.beta.1.rc1/source/> The release notes are not yet available. The updated documentation is not yet available. [ They will be available in a day or two. ] The SHA256 checksums are as follows: 4b39978aa227f56cc00715d48032e18f4bb259de756637a653b5acead4417e0b boost_1_68_0_b1_rc1.7z 39f6fdc16fc62041ca1401c5e8d1cd0220de24fd5d909eca3f0bf1049d1fd6f9 boost_1_68_0_b1_rc1.tar.bz2 9714d11a205e6f3a1cf1ed17b0caad8a64bc4a5459dfc6e1629e14e5e4b44dc7 boost_1_68_0_b1_rc1.tar.gz fe35f20eb5c2ebf5d4e4f15d0416e484058a732ca1a1e59b831b79d4d7702bdd boost_1_68_0_b1_rc1.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Boost Release Managers

5 10

Error in ublas map_array doc
by Dick Hadsell 06 Jul '18

06 Jul '18

I was looking for a function to return the capacity of a Boost uBLAS map_array, so I checked the docs online. When I looked at this page: https://www.boost.org/doc/libs/1_67_0/libs/numeric/ublas/doc/index.html I found in the table of member functions two entries for the size() function, but one should clearly be the capacity() function. I confirmed in our headers that it exists. -- Dick Hadsell 203-992-6320 Fax: 203-992-6001 Reply-to: hadsell(a)blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 1 American Lane, Greenwich, CT 06831-2560

1 0

[release] 1.68.0 closed for Beta
by Marshall Clow 06 Jul '18

06 Jul '18

The master branch is now closed for all changes except by permission for the Beta release. Also, remember to add your libraries' changes to the release notes at: < https://github.com/boostorg/website/blob/master/feed/history/boost_1_68_0.q… > Thanks, -- The Boost Release Team

4 5

[MultiIndex] Hinted insertion for multiple indices?
by Gareth.Sylvester-Bradley＠sony.com 04 Jul '18

04 Jul '18

Is there a way to provide insertion hints for multiple indices in a multi_index_container? In a particular example, I have a container with several ordered_non_unique indices, and for the majority of insertions, the value will end up at the end of these indices. I'm looking for a way to provide the index.end() hint for all of these indices? (Or maybe alternatively, to relax the stability/insertion-order guarantee?) Thanks, Gareth

2 3

[ASIO] Clarification regarding socket release on Windows
by Gyorgy Szekely 04 Jul '18

04 Jul '18

Hi, The documentation (boost 1.67) of asio::basic_stream_socket::release() has the following remark: *This function is unsupported on Windows versions prior to Windows 8.1, and will fail with boost::asio::error::operation_not_supported on these platforms.* This is in accordance with the compiler warning I get when building my project (from asio basic_socket.hpp), and the runtime behavior: the native socket ownership is indeed retained by asio. For the IOCP backend! If I add the BOOST_ASIO_DISABLE_IOCP define to the build I still get the warning, but the release() appears to be working: the ownership is released and I can do whatever I want with the socket. My question: does the above comment apply only to the IOCP backend and I can use release() with the reactive socket service? Or it just happens to be working in my current setup but it's not guaranteed for others (or it leaks resources, etc...)? Regards, Gyorgy

1 0

[beast] warning
by Vinnie Falco 04 Jul '18

04 Jul '18

I'd like to merge to master, this tiny fix for a warning: <https://github.com/boostorg/beast/pull/1175> The OSX build failure is spurious and unrelated Thanks

1 0

Boost linked example
by degski 03 Jul '18

03 Jul '18

Could someone, please, point me to an example (in the Boost source, i.e. a file in the libs sub-folder) that would require (with certainty) a built library. Which library don't matter. I've tried some date-time examples and boost::random::random_device, but it works, while I hoped it wouldn't. The latter can also mean I have some strays, but then I know that. I would like to check vcpkg static-static linking for Boost. Thanks, degski -- *"If something cannot go on forever, it will stop" - Herbert Stein*

2 4

CMT Library and CI Status for Boost 1.68.0
by James E. King III 01 Jul '18

01 Jul '18

I have been working on adding CI to the CMT libraries (and a few others). This provides improved quality and metrics for each repository with builds for various linux and windows combinations, as well as code coverage and static code analysis with coverity scan. Here is the current status for work that will make it into 1.68.0: The CI framework I have been adding is here: https://github.com/jeking3/boost-ci CI has been enabled on the following repositories (and any identified defects have been resolved) and is passing: function, mpl, pool, property_map, ptr_container, rational, tokenizer In addition, Boost.Move and Boost.Signals2 are also now using this framework to improve deliverable quality. CI not yet enabled on (and reasons): Boost.Assign fails to compile <https://github.com/boostorg/assign/pull/16> with MSVC 2012 in Appveyor. Boost.ConceptCheck fails to compile <https://github.com/boostorg/concept_check/pull/13> on most compilers in Travis CI and Appveyor. (It looks like it's unusable.) Boost.DisjointSets - status unknown (no CI) - open question still unanswered: Can we merge this into container? It is only used by graph and graph_parallel. Boost.DynamicBitset fails to compile <https://github.com/boostorg/dynamic_bitset/pull/23> on all MSVC and on linux with c++03 mode. Boost.Interval (numeric/interval) fails to compile <https://github.com/boostorg/interval/pull/14> - most combinations fail and may go into an infinite loop in some cases. Boost.Logic (tribool) uncovered issue #8 <https://github.com/boostorg/logic/issues/8>. Boost.Signals - we discussed a removal notification in an upcoming release but no action has been taken by the CMT yet to make this happen so it may slip into the next release. Boost.Statechart needs some Jamfile help to get it to work with this CI infrastructure. I am most concerned about Boost.ConceptCheck and Boost.Interval. Both may be unusable at this point. If folks have any spare cycles and care to take a look, it would be appreciated. Thanks, Jim

3 3