- Boost-users - lists.boost.org

[MultiIndex] Prevent automatic re-indexing after "modify"?
by Deniz Bahadir 06 Feb '17

06 Feb '17

Hi guys, Hi Joaquín, I have a question concerning the automatic re-indexing of Boost.MultiIndex indexes. Is it somehow possible to modify a member of the element-type that is used as key for (another) index without triggering automatic re-indexing? (Of course, I want to be able to trigger manual re-indexing later.) Or is it at least possible to adjust the code so that this can be achieved? To understand my question, here is my use-case and why I need it. I have a boost::multi_index_container with multiple indexes (one hashed_unique and four hashed_non_unique). I am accessing a range of elements through a hashed_non_unique index 'A'. Then I am iterating through these elements and want to modify the value of a member 'M' of each element. However, that member is used when calculating the key for another hashed_non_unique index 'B'. Therefore, I must use the "modify" function of index 'A'. The problem is now that it takes forever to modify the entire range. (We are talking about 100 thousands if not millions of entries that need to be modified.) Probably because re-indexing is triggered after each call to "modify". However, in my case it should be perfectly fine to postpone the re-indexing after I modified the entire range, because I am not going to access any element through index 'B' until I finished modifying the entire range. As a workaround I removed index 'B' from the container and declared the element-member 'M' as mutable. This allows me to directly change the value of 'M'. The speedup is astonishing. It now finishes almost in no time. But this workaround is not really feasible as it requires reimplementing index 'B' by somehow tracking the information outside of the multi_index_container. Therefore, my question really is: Is it possible to provide an "unsafe_modify" function, which does the same as "modify" but does not trigger automatic re-indexing, and an "refresh_index" function, which (manually) triggers the re-indexing? Thanks, Deniz

3 4

Re: [Boost-users] Boost iostreams for binary data
by Bjorn Reese 06 Feb '17

06 Feb '17

On 01/31/2017 09:25 PM, Robert Dailey wrote: > I have my own BinaryInputStream and BinaryOutputStream classes that > simply take a reference to some container that meets the requirements > of random access and contiguous internal memory. It doesn't own this > container, but rather serves as an adapter to the container to allow > stream operators to be used for streaming out data. For example, you > can stream a `std::uint32_t` to the binary stream, and it will insert > 4 elements into an internal byte vector which is just > `std::vector<std::uint8_t>`. Do they work with arrays?

2 3

[clang-win][bjam][context] '-c' is not recognized as an internal or external command
by Mikhail Strelnikov 06 Feb '17

06 Feb '17

Hello Boost, I'd like to build Boost.Context with clang on Windows with BB. There are my files: site-config.jam: using clang-win : : "C:/Program Files/LLVM/bin/clang-cl.exe" : <compatibility>vc14 <cxxflags>-Xclang <cxxflags>-std=c++1z <cxxflags>-DBOOST_USE_WINDOWS_H <cxxflags>-DNOMINMAX <cxxflags>-DWIN32_LEAN_AND_MEAN <cxxflags>-D_HAS_AUTO_PTR_ETC=1 ; Jamroot: local BOOST_ROOT = [ modules.peek : BOOST_ROOT ] ; project main : source-location . : requirements <include>$(BOOST_ROOT) <define>BOOST_ALL_NO_LIB=1 ; use-project /boost : $(BOOST_ROOT) ; exe main : main.cpp /boost//coroutine /boost//date_time ; main.cpp int main() {} I run the command: b2.exe -d+2 toolset=clang-win address-model=64 link=static runtime-link=static release -sBOOST_ROOT=D:\path\to\boost This gives me following error: clang-win.compile.asm D:\path\to\boost\bin.v2\libs\context\build\clang-vc14-win\release\link-static\runtime-link-static\threading-multi\asm\make_x86_64_ms_pe_gas.obj -c -Zp4 -Cp -Cx -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTEXT_SOURCE -DBOOST_DISABLE_ASSERTS -DNDEBUG -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTEXT_SOURCE -DBOOST_DISABLE_ASSERTS -DNDEBUG /W3 -Fo "D:\path\to\boost\bin.v2\libs\context\build\clang-vc14-win\release\link-static\runtime-link-static\threading-multi\asm\make_x86_64_ms_pe_gas.obj" "D:\path\to\boost\libs\context\src\asm\make_x86_64_ms_pe_gas.asm" '-c' is not recognized as an internal or external command, Am I doing something wrong? Thanks.

2 4

[mpl] Working with map, copy and back_inserter
by ☂Josh Chia (謝任中) 05 Feb '17

05 Feb '17

I'm trying to implement a compile-time topological sort of the DAG representing a certain dependency relationship between my classes. One of the data structures I can use to implement topological sort is a map, so I'm trying to use mpl::map using mpl::size_t<> as key. The documentation doesn't define key equality for mpl::map, but I assume it's effectively std::is_same<>. If so, I think I have a problem. In the following code, the last two lines fail static_assert(). The essence of the problem is that my attempt to construct/build my keys using copy with back_inserter does not give me a mpl::vector<> of mpl::size_t<> that is_same to Count, the expected value. It does give me a sequence, and the elements have the right value and value_type but they are not is_same to the expected size_t<> types. So, if I use the elements together with the size_t<> in an mpl::map, won't they be considered to be different keys? Josh #include <type_traits> #include <boost/mpl/at.hpp> #include <boost/mpl/back_inserter.hpp> #include <boost/mpl/copy.hpp> #include <boost/mpl/equal.hpp> #include <boost/mpl/equal_to.hpp> #include <boost/mpl/range_c.hpp> #include <boost/mpl/size_t.hpp> #include <boost/mpl/vector.hpp> using namespace std; namespace mpl = boost::mpl; using Empty = typename mpl::vector<>; using Count = mpl::vector<mpl::size_t<0>, mpl::size_t<1>>; using ConstructedCount = typename mpl::copy< typename mpl::range_c<size_t, 0, 2>, mpl::back_inserter<Empty>>::type; using The0 = typename mpl::at<ConstructedCount, mpl::size_t<0>>::type; using The1 = typename mpl::at<ConstructedCount, mpl::size_t<1>>::type; static_assert(mpl::equal<Count, ConstructedCount, mpl::equal_to<mpl::_1, mpl::_2>>::value, "succeeds"); static_assert(The1::value == 1, "succeeds"); static_assert(std::is_same<typename The1::value_type, size_t>::value, "succeeds"); static_assert(std::is_same<Count, ConstructedCount>::value, "fails"); static_assert(std::is_same<The1, mpl::size_t<1>>::value, "fails");

2 1

[mpl] at<> behaves differently for vector_c<> and vector<>
by ☂Josh Chia (謝任中) 05 Feb '17

05 Feb '17

I asked earlier in a post "[mpl] Working with map, copy and back_inserter". This is a related question. The common question is: What does compile-time equality means in MPL, particularly for map and set key equality? Does it mean std::is_same? The following code works whether USE_VECTOR_C is defined as 0 or 1 -- the last 2 lines are static_asserts that have conditions determined by USE_VECTOR_C so that they succeed, highlighting the difference in behavior between USE_VECTOR_C == 0 and USE_VECTOR_C == 1. USE_VECTOR_C == 0 is the normal case where everything is working as I expect. USE_VECTOR_C == 1 is the unexpected case where the static_asserts in the last 2 lines have conditions altered so that they succeed. Why do vector_c and vector give me different "element values"? In general, what should I be careful about when trying to use the "compile-time values" as keys to avoid the situation elucidated by the last line, where I expect two "compile-time values" to be the same but they are not, resulting in two set/map items instead of one? To clarify, I'm using boost 1.63 with gcc 6.3.1 and -std=c++14 on Arch Linux. Josh #include <type_traits> #include <boost/mpl/at.hpp> #include <boost/mpl/insert.hpp> #include <boost/mpl/set.hpp> #include <boost/mpl/size.hpp> #include <boost/mpl/size_t.hpp> #include <boost/mpl/vector.hpp> #include <boost/mpl/vector_c.hpp> using namespace std; namespace mpl = boost::mpl; #define USE_VECTOR_C 0 using Zero = mpl::size_t<0>; #if USE_VECTOR_C == 1 using Vector = mpl::vector_c<size_t, 0>; #else using Vector = mpl::vector<Zero>; #endif using ZeroElt = typename mpl::at<Vector, Zero>::type; using EmptySet = mpl::set<>; using NonEmptySet = typename mpl::insert<typename mpl::insert<EmptySet, Zero>::type, ZeroElt>::type; static_assert(ZeroElt::value == 0, ""); static_assert(is_same<ZeroElt::value_type, size_t>::value, ""); static_assert(is_same<ZeroElt, Zero>::value == !USE_VECTOR_C, ""); static_assert(mpl::size<NonEmptySet>::value == USE_VECTOR_C + 1, "");

2 1

context library of boost: compiling for windows 32 on ubuntu 64
by Jack Kumba 04 Feb '17

04 Feb '17

Hello, I want to compile libboost_context.a for windows 32 on my ubuntu 64. for that, I specify the following in my user-config.jam file using gcc : : "i686-w64-mingw32-g++" ; and then, I run the following: b2 --with-context toolset=gcc target-os=windows variant=release link=static address-model=32 binary-format=pe architecture=x86 this gives me the following error: libs/context/src/unsupported.cpp:7:2: error: #error "platform not supported" #error "platform not supported" ^ "i686-w64-mingw32-g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -march=i686 -mthreads -m32 -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTEXT_SOURCE -DBOOST_DISABLE_ASSERTS -DNDEBUG -I"." -c -o "bin.v2/libs/context/build/gcc-mingw-5.3.1/release/binary-format-pe/build-no/link-static/target-os-windows/threading-multi/unsupported.o" "libs/context/src/unsupported.cpp" ...failed gcc.compile.c++ bin.v2/libs/context/build/gcc-mingw-5.3.1/release/binary-format-pe/build-no/link-static/target-os-windows/threading-multi/unsupported.o... full message is posted here: https://thepasteb.in/p/y8hzcR93o3XO7t2 It seems like the context library of boost is not supported to compile for windows on linux? Is it the case? Thanks, Aja

3 4

Can I config process_id to log file name in the .ini setting file using Boost.Log?
by Bruce 04 Feb '17

04 Feb '17

Hi, I am using Boost.Log to output log file and using .ini file to config it. Now I need to start the exe file from the same directory for more than two instance with different start id, something like this: >start my_app.exe 1 >start my_app.exe 2 But currently only the first instance output the log content and the second one can't get the log file because the two exe uses the same log file. So I need to tell the app to use the different log file. So I want to config the .ini file to add process_id to the output file name, but I don't know how? I want to config the ini file like this but it failed:-( FileName="./log/mylog_%ProcessID%.log" Is there a way to add precess id to the output file name? Thanks.

1 0

Boost iostreams for binary data
by Robert Dailey 03 Feb '17

03 Feb '17

I have my own BinaryInputStream and BinaryOutputStream classes that simply take a reference to some container that meets the requirements of random access and contiguous internal memory. It doesn't own this container, but rather serves as an adapter to the container to allow stream operators to be used for streaming out data. For example, you can stream a `std::uint32_t` to the binary stream, and it will insert 4 elements into an internal byte vector which is just `std::vector<std::uint8_t>`. I did not implement these in terms of IO streams, because those seemed a bit overkill and make a lot of assumptions on the data being text-only. Also I can't stream binary data into vectors, lists, and other containers because the data simply can't be parsed. Each stream out of a binary vector must be done so with a finite count of bytes. Would it make sense to implement these objects in terms of the IOstream facilities provided by boost? I know these were designed to make defining stream classes easier, but honestly I don't have a lot of experience with them. Any feedback on this? Thanks in advance. I can provide some example code if needed.

2 2

Mail List Migration - Update
by Michael Caisse 02 Feb '17

02 Feb '17

The Boost mail lists are now migrated to a new set of servers. This change affected all mail lists and web resources (signing up, changing passwords, moderator access, archives...) that were associated with the domain lists.boost.org . If you are having difficulties, please drop me an email. (Oh the irony) Happy coding! michael -- Michael Caisse Ciere Consulting ciere.com

1 0

Mail Lists Migrate at 00:00 UTC Feb 3
by Michael Caisse 02 Feb '17

02 Feb '17

The following mail lists will be switched to new infrastructure at 00:00 UTC on February 3rd. There will be a small interruption while the DNS/MX records propagate. * Boost - Boost developers' mailing list * Boost-announce - Boost announce-only mailing list * Boost-bugs - Bugs reported/updated through Boost's Trac * Boost-build - Boost.Build developer's and user's list * Boost-cmake - Discussion of the CMake-based build system for Boost * Boost-commit - Boost Subversion commit messages * Boost-docs - Discussion of Boost Documentation * Boost-Interest - Moderated announcements of interest to the Boost community. * Boost-maint - Boost community maintenance mailing list * Boost-mpi - Discussion of Boost.MPI development * Boost-test - Test list for the boost mailing lists * Boost-Testing - Running Boost regression tests * Boost-users - Boost Users mailing list * Geometry - Boost.Geometry library mailing list * glas - Generic Linear Algebra Software * proto - Discussions about Boost.Proto and DSEL design * threads-devel - Discussions about the boost.thread library * ublas - ublas mailing list -- Michael Caisse Ciere Consulting ciere.com

1 0