- Boost-users - lists.preview.boost.org

boost graph adjacency_list delete nodes and vertices
by Paolo Bolzoni 14 Sep '15

14 Sep '15

Dear list, I am using boost graph with vecS both as edge-list and vertex-list and I need to delete some nodes. In my case nodes have no incoming or outgoing edges, but I'd like to understand how to do it in general. In vectors normally you simply swap the unwanted element with the last one and pop back. This way only the last element index is changed, all others are fine. The generalization of this idea is the base of the "remove erase idiom". It possible to apply it to adjacency_list (vecS,vecS)? I need this because I keep vertex index elsewhere, so I'd like to be able to update only the last one and not all of them. >From the implementation I get that is possible to swap the vertex you want to delete with the "last" one and delete it. By last one I mean the one returned by *(--vertices(g).second) It is really safe? And how to delete edges, it is possible? Yours faithfully, Paolo

1 0

problem in configuring the environment
by arto rasimus 12 Sep '15

12 Sep '15

I have Raspberry Pi, realtime kernel in it and machinekit 2.7-0 package. Boost version is 1.55-0. Question 1: What to check, since the machinekit does not find the boost? (and therefore its configuration script fails)Question 2: Is there possibly some library missing?uname -a: Linux raspberrypi 3.18.11+ #781 PREEMPT Tue Apr 21 18:02:18 BST 2015 armv6l GNU/Linux The error message that comes from machinekit is: configure: error: boost::python is required to build LinuxCNC Installed boost libraries: dpkg -l | grep boost ii libboost-atomic1.55-dev:armhf 1.55.0+dfsg-3 armhf atomic data types, operations, and memory ordering constraints ii libboost-atomic1.55.0:armhf 1.55.0+dfsg-3 armhf atomic data types, operations, and memory ordering constraints ii libboost-chrono1.55-dev:armhf 1.55.0+dfsg-3 armhf C++ representation of time duration, time point, and clocks ii libboost-chrono1.55.0:armhf 1.55.0+dfsg-3 armhf C++ representation of time duration, time point, and clocks ii libboost-date-time1.55-dev:armhf 1.55.0+dfsg-3 armhf set of date-time libraries based on generic programming concepts ii libboost-date-time1.55.0:armhf 1.55.0+dfsg-3 armhf set of date-time libraries based on generic programming concepts ii libboost-dev:armhf 1.55.0.2 armhf Boost C++ Libraries development files (default version) ii libboost-filesystem-dev:armhf 1.55.0.2 armhf filesystem operations (portable paths, iteration over directories, etc) in C++ (default version) ii libboost-filesystem1.55-dev:armhf 1.55.0+dfsg-3 armhf filesystem operations (portable paths, iteration over directories, etc) in C++ ii libboost-filesystem1.55.0:armhf 1.55.0+dfsg-3 armhf filesystem operations (portable paths, iteration over directories, etc) in C++ ii libboost-program-options-dev:armhf 1.55.0.2 armhf program options library for C++ (default version) ii libboost-program-options1.55-dev:armhf 1.55.0+dfsg-3 armhf program options library for C++ ii libboost-program-options1.55.0:armhf 1.55.0+dfsg-3 armhf program options library for C++ ii libboost-python-dev 1.55.0.2 armhf Boost.Python Library development files (default version) ii libboost-python1.55-dev 1.55.0+dfsg-3 armhf Boost.Python Library development files ii libboost-python1.55.0 1.55.0+dfsg-3 armhf Boost.Python Library ii libboost-serialization-dev:armhf 1.55.0.2 armhf serialization library for C++ (default version) ii libboost-serialization1.55-dev:armhf 1.55.0+dfsg-3 armhf serialization library for C++ ii libboost-serialization1.55.0:armhf 1.55.0+dfsg-3 armhf serialization library for C++ ii libboost-system-dev:armhf 1.55.0.2 armhf Operating system (e.g. diagnostics support) library (default version) ii libboost-system1.55-dev:armhf 1.55.0+dfsg-3 armhf Operating system (e.g. diagnostics support) library ii libboost-system1.55.0:armhf 1.55.0+dfsg-3 armhf Operating system (e.g. diagnostics support) library ii libboost-test-dev:armhf 1.55.0.2 armhf components for writing and executing test suites (default version) ii libboost-test1.55-dev:armhf 1.55.0+dfsg-3 armhf components for writing and executing test suites ii libboost-test1.55.0:armhf 1.55.0+dfsg-3 armhf components for writing and executing test suites ii libboost-thread-dev:armhf 1.55.0.2 armhf portable C++ multi-threading (default version) ii libboost-thread1.55-dev:armhf 1.55.0+dfsg-3 armhf portable C++ multi-threading ii libboost-thread1.55.0:armhf 1.55.0+dfsg-3 armhf portable C++ multi-threading ii libboost1.55-dev:armhf 1.55.0+dfsg-3

1 0

TLS/Non-TLS mismatch in ASIO when using LTO
by Matthew S Wallace 11 Sep '15

11 Sep '15

When build/link my application with -flto (using GCC 4.8.3 and Boost 1.59) I get the following error when linking the executable: 1:58 /bin/ld: _ZN5boost4asio6detail15keyword_tss_ptrINS1_10call_stackINS1_15task_io_serviceENS1_27task_io_service_thread_infoEE7contextEE6value_E: TLS definition in ./build/lib/mylib.so section .tbss mismatches non-TLS definition in build/src/my_app/main.o (symbol from plugin) section .gnu.linkonce.t._ZN5boost4asio6detail15keyword_tss_ptrINS1_10call_stackINS1_15task_io_serviceENS1_27task_io_service_thread_infoEE7contextEE6value_E build/src/my_app/main.o (symbol from plugin): could not read symbols: Bad value collect2: error: ld returned 1 exit status I do not see this error if I do not use the -flto option at link time. I confess I have no real idea what’s going on here - a bit of googling suggested this might be related to the __thread directive in the GCC for thread local storage, so I tried to rebuild Boost like: ./b2 define=BOOST_ASIO_DISABLE_THREAD_KEYWORK_EXTENSION. This didn’t help. -Matt

1 0

[integer] what is the fastest integer type which can hold an 8 bit number?
by Robert Ramey 11 Sep '15

11 Sep '15

Reading the documentation at http://www.boost.org/doc/libs/1_59_0/libs/integer/doc/html/boost_integer/in… I invoke the following using temp_integer = typename boost::int_t<8>::fast; With the idea of getting the fastest integer type which will hold an 8 bit signed number. But I get temp_integer equal to a char type. This surprises me. I don't believe that the fastest integer type which can hold an 8 bit signed integer is a char. I looked into the boost/integer.hpp and I can't really figure it out. It doesn't seem to to have any processor specific code in it - which I would think would be necessary to implement the function. What am I missing here? Robert Ramey

3 3

Boost.Fiber mini-review September 4-13
by Nat Goodspeed 11 Sep '15

11 Sep '15

Hi all, The mini-review of Boost.Fiber by Oliver Kowalke begins today, Friday September 4th, and closes Sunday September 13th. It was reviewed in January 2014; the verdict at that time was "not in its present form." Since then Oliver has substantially improved documentation, performance, library customization and the underlying implementation, and is bringing the library back for mini-review. The substance of the library API remains the same, which is why a mini-review is appropriate. The Fiber library now requires a C++14-conforming compiler. I will monitor reviews and discussion on both the boost-users@ list and the boost@ developers' list. Please include at least "fiber" and "review" in your mail subject, e.g. by replying to this message. (Please reply to only ONE list, however.) Thank you for your interest and your feedback! ----------------------------------------------------- About the library: Boost.Fiber provides a framework for micro-/userland-threads (fibers) scheduled cooperatively. The API contains classes and functions to manage and synchronize fibers similar to Boost.Thread. Each fiber has its own stack. A fiber can save the current execution state, including all registers and CPU flags, the instruction pointer, and the stack pointer and later restore this state. The idea is to have multiple execution paths running on a single thread using a sort of cooperative scheduling (versus threads, which are preemptively scheduled). The running fiber decides explicitly when it should yield to allow another fiber to run (context switching). Boost.Fiber internally uses execution_context from Boost.Context; the classes in this library manage, schedule and, when needed, synchronize those contexts. A context switch between threads usually costs thousands of CPU cycles on x86, compared to a fiber switch with a few hundred cycles. A fiber can only run on a single thread at any point in time. docs: http://olk.github.io/libs/fiber/doc/html/index.html git: https://github.com/olk/boost-fiber --------------------------------------------------- Please always state in your review whether you think the library should be accepted as a Boost library! Additionally please consider giving feedback on the following general topics: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? Nat Goodspeed Boost.Fiber Review Manager ________________________________

6 51

[Accumulators] Compiler error when compiling examples: extractor.hpp:36:74: error: no type named 'result_type' in 'boost::fusion::void_'
by Bernhard Wagner 11 Sep '15

11 Sep '15

When compiling: #include <boost/accumulators/framework/accumulator_set.hpp> #include <boost/accumulators/statistics/covariance.hpp> #include <boost/accumulators/statistics/variates/covariate.hpp> #include <boost/test/unit_test.hpp> #include <boost/test/floating_point_comparison.hpp> using namespace boost::accumulators; int main() { accumulator_set<double, stats<tag::covariance<double, tag::covariate1> > > acc; acc(1., covariate1 = 2.); acc(1., covariate1 = 4.); acc(2., covariate1 = 3.); acc(6., covariate1 = 1.); assert(covariance(acc) == -1.75); } using: clang++ -std=c++11 -stdlib=libc++ -Weverything accum_covariance.cpp -L /usr/local/Cellar/boost/1.55.0_2/lib/ -l boost_unit_test_framework (on OSX 10.8.5) I get following error. Same error when I try using rolling_sum or rolling_mean. In file included from accum_covariance.cpp:1: In file included from /usr/local/include/boost/accumulators/framework/accumulator_set.hpp:27: In file included from /usr/local/include/boost/accumulators/framework/accumulators/external_accumulator.hpp:13: /usr/local/include/boost/accumulators/framework/extractor.hpp:36:74: error: no type named 'result_type' in 'boost::fusion::void_' typedef typename mpl::apply<AccumulatorSet, feature_type>::type::result_type type; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~

2 2

xpressive: regex to catch HTML generic tag with back reference to tag name
by Mia 10 Sep '15

10 Sep '15

Hello,I am quite new to Boost Xpressive, I am using C++ on Visual Studio 2013 and Boost 1_58_0I need to clean up some text from all HTML tagsI an trying to use this regex:wsregex html_any_tag_regex = wsregex::compile("^([^<]*)?<([A-Za-z][A-Za-z0-9]*)[^>]*>(.+)<\\/(\\2)>(.*)?$");this regex causes compilation error: error C2664: 'int boost::mpl::assertion_failed(boost::mpl::assert::type)' : cannot convert argument 1 from 'boost::mpl::failed ************boost::is_same<wchar_t,char>::* ***********' to 'boost::mpl::assert::type'I tested my regex here:http://www.myezapp.com/apps/dev/regexp/show.wsand it is parsed exactly to my needs.What am I doing wrong?Thank youMia -- View this message in context: http://boost.2283326.n4.nabble.com/xpressive-regex-to-catch-HTML-generic-ta… Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

Linker error with boost::serialization
by Stephen Gray 10 Sep '15

10 Sep '15

Using Debian Jessie (64bit) I've just built Boost 1.56 from source. Whilst compiling an application I'm getting the error; g++ -o ./Release/sdCloneServer @"sdCloneServer.txt" -L. -L/usr/local/lib -L/usr/lib/x86_64-linux-gnu -lpthread -lzmq -lboost_date_time -lboost_serialization./Release/sdCloneServer_sdCloneServer.cpp.o: In function `boost::archive::detail::common_iarchive<boost::archive::text_iarchive>::vload(boost::archive::class_name_type&)':sdCloneServer.cpp:(.text._ZN5boost7archive6detail15common_iarchiveINS0_13text_iarchiveEE5vloadERNS0_15class_name_typeE[_ZN5boost7archive6detail15common_iarchiveINS0_13text_iarchiveEE5vloadERNS0_15class_name_typeE]+0x1): undefined reference to `boost::archive::text_iarchive_impl<boost::archive::text_iarchive>::load_override(boost::archive::class_name_type&)'collect2: error: ld returned 1 exit status I've tried manipulating the order in which the libraries are listed in the complier command but without success. Can anyone please offer suggestions on what is wrong and how to resolve this? With thanks.

1 0

Compilation problem with fedora 22
by Pierre Daye 10 Sep '15

10 Sep '15

Hello, I recently installed Fedora 22 and I decided to use boost 1.59.0. I also have a little server with Centos 7 on it. On both system, I installed boost 1.58.0. I also installed the Intel cluster studio XE 2016 on each machine. I can compile (and run) with no problem my code on the Centos 7 but I can not compile it under fedora 22. The relevant lines of code are: void GABAB::compCumSum(double* out,double T_in,double dur) > { > double dt=0.01; > int NStep=(int) floor(dur/dt); > > int tmpstartInd=startInd; > > startInd=0; > > StateVector x(2 * NState); > > controlled_runge_kutta< runge_kutta_cash_karp54 < StateVector, double, > StateVector, double, vector_space_algebra, mkl_operations > > > stepper_cumsum; > > compInitState(x, 0.0, 0.0); > > for (int ii = 0; ii < NState; ii++) > x[ ii + NState ] = 0.0; > > for (int ii = 0; ii < NState; ii++) > out[ii] = x[ii]; > > setInput(T_in, T_in); > > cumsum_GABAB tmp(*this); > > size_t steps = integrate_adaptive( stepper_cumsum, tmp , x , 0.0 , dur , > dt ); > > for (int ii = 0; ii < NState; ii++) > out[ii] = x[ii + NState]; > > startInd=tmpstartInd; > } StateVector is a typedef in another header file: typedef boost::numeric::ublas::vector< double > StateVector; If I comment the line starting with "integrate_adaptive(...", I can compile the code. Otherwise, I got a tons of errors, starting with: /usr/include/c++/5.1.1/functional(78): error: class > "boost::numeric::odeint::controlled_runge_kutta<boost::numeric::odeint::runge_kutta_dopri5<StateVector, > double, StateVector, double, boost::numeric::odeint::vector_space_algebra, > boost::numeric::odeint::default_operations, > boost::numeric::odeint::initially_resizer>, > boost::numeric::odeint::default_error_checker<double, > boost::numeric::odeint::vector_space_algebra, > boost::numeric::odeint::default_operations>, > boost::numeric::odeint::initially_resizer, > boost::numeric::odeint::explicit_error_stepper_fsal_tag>" has no member > "result_type" > { typedef typename _Functor::result_type result_type; }; I emphasize the fact that the code can easily be compiled under Centos 7 with the same installation procedure of boost and the intel cluster xe suite. Any clue of what is happening? Thanks, Pierre -- "It doesn't matter how beautiful your theory is, it doesn't matter how smart you are. If it doesn't agree with experiment, it's wrong." Richard P. Feynman

1 0

Boost.Test - problems overriding main
by ramonpadilla1＠yahoo.co.uk 10 Sep '15

10 Sep '15

I want to provide my own main function while using Boost.Test. So I have included the following macros: #define BOOST_TEST_ALTERNATIVE_INIT_API #define BOOST_TEST_NO_MAIN In my main function I have a call to: ::boost::unit_test::unit_test_main(&registering_all_tests, argc, argv) but this gives me the following error when build on OS X using Xcode 6: Undefined symbols for architecture x86_64: "boost::unit_test::unit_test_main(bool (*)(), int, char**)", referenced from: _main in main.o I found out that including the following file: #include <boost/test/included/unit_test.hpp> resolves this problem but I'm confused about the implications. The description of this file states that it uses the included (vs. linked) version of Unit Test Framework. The Boost getting started guide states that: > Boost.Test can be used in “header-only” or “separately compiled” mode,> although **separate compilation is recommended for serious use**. I have built the library separately. The Boost doc also states: > Including the UTF directly into your test module> > If you prefer to avoid the standalone library compilation you can> either include all files that constitute the static library in your> test module's makefile or include them as a part of a test module's> source file. To facilitate the later variant the UTF presents the> single-header usage variant. In either case no special build options> or macro definitions are required to be added to your compilation> options list by default. But the same flags that can be used for the> standalone library compilation are applicable in this case. Though,> obviously, neither BOOST_TEST_DYN_LINK nor BOOST_TEST_NO_LIB are> applicable. This solution may not be the best choice in a long run,> since it requires the UTF sources recompilation for every test module> you use it with and for every change of a test module you are working> on. In a result your testing cycle time may increase. If it become> tiresome, I recommend switching to one of the prebuilt library usage> variants. It seems that by choosing to include the included (vs. linked) version of Unit Test Framework I am dong the wrong thing. Can someone please clarify the correct approach. The examples of overriding main don't mention the need to do this.

2 4