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

Stacktrace library starts review today 14th Dec
by Niall Douglas 15 Dec '16

15 Dec '16

The formal review of the Stacktrace library by Antony Polukhin starts today 14th Dec and will conclude before Christmas. I appreciate we are likely a bit tired out from the many library reviews recently and of course it's Christmas, but given the lack of a portable way to work with stack backtraces, which you inevitably need to do eventually in any non-toy production application, Stacktrace needs your review! Stacktrace is an optionally header-only library providing four implementation backends, libunwind (POSIX only), windbg (Windows only), backtrace (from the C library on most POSIX implementations) and a null backend. At its very simplest it lets you capture the stack backtrace for the calling thread and to print it to a std::ostream& of your choice. The basic_stacktrace<> class quacks like a STL container of frame object instances. The rest of the API pretty much follows STL design principles for the most part. Use is therefore unsurprising. You can find the documentation at http://apolukhin.github.io/stacktrace/index.html and the github repo at https://github.com/apolukhin/stacktrace. Review guidelines ================= Reviews should be submitted to the developer list (boost(a)lists.boost.org) preferably with '[stacktrace]' in the subject. Or if you don't wish to for some reason or are not subscribed to the developer list you can send them privately to me at 's_sourceforge at nedprod dot com'. If so, please let me know whether or not you'd like your review to be forwarded to the list. For your review you may wish to consider the following questions: - What is your evaluation of the design? - What is your evaluation of the implementation? Most of my personal concerns with this library are with the implementation and I would hugely appreciate feedback from others with substantial experience of using stacktracing "in anger" in non-trivial use case scenarios. - 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? And finally, every review should attempt to answer this question: - Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Even if you do not wish to give a full review any technical comment regarding the library is welcome as part of the review period and will help me as the review manager decide whether the library should be accepted as a Boost library. Any questions about the use of the library are also welcome. Finally, thanks to Edward whose announcement of the Synapse library review I borrowed heavily from as I thought it very well structured. Hopefully the above is just as clear. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

3 3

SSDLC Compliance - Boost C++ Libraries
by GAN Kok Leong, Adrian 14 Dec '16

14 Dec '16

Hi, We have a cybersecurity requirement for all software. We would like to know whether Boost C++ Libraries is developed and comply with Secure Software Development Life Cycle (SSDLC)? Regards Adrian Gan [This e-mail is confidential and may be privileged. If you are not the intended recipient, please kindly notify us immediately and delete the message from your system; please do not copy or use it for any purpose, nor disclose its contents to any other person. Thank you.] ---ST Electronics Group---

2 1

question
by David Bergman 13 Dec '16

13 Dec '16

Is boost capable of parallel processing. That is do wrappers or interfaces exist to call existing parallel versions of functions to help the user/programmer?Thank you, David

2 1

question
by David Bergman 13 Dec '16

13 Dec '16

Does boost handle Bessel functions with imaginary or complex index?Thank you, David

1 0

[C++ Libraries] Is it develop according to SSDLC?
by GAN Kok Leong, Adrian 13 Dec '16

13 Dec '16

Hi, I would like to know whether Boost C++ Libraries version 1.36.0-11.17 is developed and comply with Secure Software Development Life Cycle (SSDLC)? Regards Adrian Gan [This e-mail is confidential and may be privileged. If you are not the intended recipient, please kindly notify us immediately and delete the message from your system; please do not copy or use it for any purpose, nor disclose its contents to any other person. Thank you.] ---ST Electronics Group---

1 0

Unexpected static libraries in Windows build
by Christian Ullrich 06 Dec '16

06 Dec '16

Hello, I have a question about compiling Boost (1.62.0) itself on Windows, with Visual Studio 2015. I want to build DLLs only, but after I run .\b2 link=shared runtime-link=shared [...] install , I have a number of static libraries (libboost_...-mt-1_62.lib) in the lib directory. Specifically: - system - chrono - timer - unit_test_framework - test_exec_monitor - exception The first four also exist as the DLLs I expected to get. From testing some previous Boost releases, it seems that the number of unexpected static libraries increases over time (1.58 only produces two, and more appear with the versions in between that and 1.62). Why are these static libraries built in a shared/shared configuration? Do I need to keep them, or are they some kind of temporary build artifact (used to build others, perhaps)? I have looked through the documentation, mailing list archive, bug tracker, etc., but could not find anything on the subject. If I have not looked hard enough, any pointers will be welcome. I even looked at b2's dependency graph (-d +12), and from that, it appears they are top-level dependencies, but I cannot figure out where _any_ top-level dependencies are defined, let alone these. Thanks for any hints, -- Christian

2 2

[boost.build] how to install boost for arduino ide
by uğur aykar 06 Dec '16

06 Dec '16

>Hello everyone; >I am trying to figure out how to use boost libraries for arduino (avr-gcc). I am so >new to the boost. >I especially want to use lorenz example and compile it with arduino ide. >it requires the odeint library inside the "Boost/numeric/odeint. " which i >downloaded from https://www.codeproject.com/articles/268589/odeint-v-solving-ordinary-diffe… >and dowloaded the whole boost library version boost_1_62_0. >but i couldn't understand how to install for arduino ide. >where should i start? I feel so lost here. Thank you all Ugur Aykar uguraykar(a)hotmail.com

1 0

boost_regex compiler error
by Chris Padwick 06 Dec '16

06 Dec '16

Hi - I am stuck on a linker error with the boost_regex library. My platform is ubuntu 16.04 LTS, arm64, NVIDIA TX1. I downloaded and built boost 1.62.0 with the following parameters: ./bootstrap.sh --prefix=/usr/local sudo ./b2 -d2 architecture=arm address-model=64 install I compiled a simple program using this command line: g++ main.cpp -I/usr/local/include -L/usr/local/lib -lboost_regex Here is the program: #include <boost/regex.hpp> #include <iostream> using namespace std; int main(int argc, char *argv[]) { static const boost::regex rxInt("[0-9]+"); string word = "foobar"; if(boost::regex_match(word, rxInt)) { cout << "Integer" << endl; } else { cout << "Not integer" << endl; } return 0; } Here are the linker errors: /tmp/ccuOD7Zj.o: In function `bool boost::regex_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >(__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, __gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, boost::match_results<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > >&, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags)': main.cpp:(.text._ZN5boost11regex_matchIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEESaINS_9sub_matchISB_EEEcNS_12regex_traitsIcNS_16cpp_regex_traitsIcEEEEEEbT_SJ_RNS_13match_resultsISJ_T0_EERKNS_11basic_regexIT1_T2_EENS_15regex_constants12_match_flagsE[_ZN5boost11regex_matchIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEESaINS_9sub_matchISB_EEEcNS_12regex_traitsIcNS_16cpp_regex_traitsIcEEEEEEbT_SJ_RNS_13match_resultsISJ_T0_EERKNS_11basic_regexIT1_T2_EENS_15regex_constants12_match_flagsE]+0x58): undefined reference to `boost::re_detail::perl_matcher<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::match()' /tmp/ccuOD7Zj.o: In function `boost::re_detail::perl_matcher<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::perl_matcher(__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, __gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, boost::match_results<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > >&, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags, __gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >)': main.cpp:(.text._ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcEEEEEC2ESC_SC_RNS_13match_resultsISC_SF_EERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsESC_[_ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcEEEEEC5ESC_SC_RNS_13match_resultsISC_SF_EERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsESC_]+0xf8): undefined reference to `boost::re_detail::perl_matcher<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::construct_init(boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags)' collect2: error: ld returned 1 exit status Any hints would be appreciated. Should I try to use an earlier version of boost? thank you!

2 2

[test] Really deactivate test
by Florian Lindner 05 Dec '16

05 Dec '16

Hello, I need to conditionally decativate tests and use a custom decorator for that, like that: virtual void apply(bt::test_unit& tu) { [...] if (std::find(_ranks.begin(), _ranks.end(), rank) == _ranks.end()) { std::cout << rank << " Disable, because of rank, test: " << tu.full_name() << std::endl; tu.p_default_status.value = bt::test_unit::RS_DISABLED; return; } } (i'm happy to provide full source code, if anyone is interested) As you can see it's deativated on some MPI ranks only. However, if a user uses -t "testname" it is activated again. Is there a way to really deactivate the test? Or delete it from the test tree? Thanks, Florian

1 0

VS 2017 RC + boost.context
by Michael Steinberg 05 Dec '16

05 Dec '16

Hi there, I'm trying to build boost with VS 2017 RC but run into problems building boost.context. The project jam file somehow triggers to build the "unsupported.cpp", but I'm not proficient enough with the build system to find out how I can circumvent that. I would be very grateful if somebody could help me out with this. Cheers! Michael

2 4

[Boost.Container] Performance of static_vector with default_init_t
by dariomt＠gmail.com 04 Dec '16

04 Dec '16

Hi, I'm constructing a static_vector<double,N>(n, default_init). I was expecting the constructor call to vanish into just setting the start pointer and the size & capacity members (and verifying n<=N). However, the profiler is showing some time spent in the loop inside uninitialized_default_init_alloc_n (boost/container/detail/utilities.hpp:678) For a builtin type and default_init_t, why do we even need to invoke the allocator? Can't we just leave the memory uninitialized? This is with Boost 1.55 and VS2008 Thanks in advance

2 1

[Boost.Signals2] Problem with cleanup when disconnecting from slot.
by Paul Blampspied 03 Dec '16

03 Dec '16

Am I right in thinking that when a signal is connected to a closure created by boost::bind, then the closure should be destructed when the connection is closed ? I am having trouble because I pass a boost::shared_ptr in the closure. The use count does not drop when the signal connection is closed (the signal is connected to a one-shot slot which closes the connection). As a result the shared_ptr never deletes its data causing a memory leak. I have seen a few mentions of bugs in signals2 with respect to object destruction on connection termination. Perhaps I have fallen foul of that. It seems quite a serious bug though considering the general standard of boost. Given that the one-shot slot receives the shared_ptr I am considering a hack to fix the problem - explicitly break into the shared_ptr and decrement the reference count that I believe should be decremented by conn.disconnect(). Is there a better way ?

1 0

Closure not destructed properly when signals2 connection is closed.
by Paul Blampspied 03 Dec '16

03 Dec '16

Am I right in thinking that when a signal is connected to a closure created by boost::bind, then the closure should be destructed when the connection is closed ? I am having trouble because I pass a boost::shared_ptr in the closure. The use count does not drop when the signal connection is closed (the signal is connected to a one-shot slot which closes the connection). As a result the shared_ptr never deletes its data causing a memory leak. I have seen a few mentions of bugs in signals2 with respect to object destruction on connection termination. Perhaps I have fallen foul of that. It seems quite a serious bug though considering the general standard of boost. Given that the one-shot slot receives the shared_ptr I am considering a hack to fix the problem - explicitly break into the shared_ptr and decrement the reference count that I believe should be decremented by conn.disconnect(). Is there a better way ?

1 0

[Log] Random "double free or corruption" in dtor of attribute_value_set
by robin.lorke＠jenoptik.com 01 Dec '16

01 Dec '16

Hi Gentlemen, I have an application that is using Boost.Log. The application is long-term running (days, weeks, maybe months). Currently I am experiencing random crashes in my application that seem related to Boost.Log. I dont't say that is is a bug in Boost.Log, but probably I am doing something wrong. I am using version 1.55.0 but I also tried upgrading to version 1.61.0 but it is still happening there. I am currently able to reproduce the crash by forcing logs at a pace of 3 records per second. Then it takes up to 3 days for the crash to happen. The application is multi-threaded and therefore several threads may be logging at the same time. For that reason I chose "severity_logger_mt". It seems related to the destruction of objects of type attribute_value_set. This is a gdb stacktrace of the crash (gcc O0 build): (gdb) bt #0 0xb6bdbed8 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:66 #1 0xb6bdf960 in __GI_abort () at abort.c:90 #2 0xb6c139fc in __libc_message (do_abort=2, fmt=0xb6cc8c44 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:200 #3 0xb6c1e17c in malloc_printerr (action=3, str=0xb6cc8d80 "double free or corruption (!prev)", ptr=<optimized out>) at malloc.c:4949 #4 0xb6b3fcb8 in boost::log::v2_mt_posix::attribute_value_set::~attribute_value_set() () from /usr/lib/libboost_log.so.1.55.0 #5 0xb6b42688 in boost::log::v2_mt_posix::record_view::public_data::destroy (boost::log::v2_mt_posix::record_view::public_data const*) () from /usr/lib/libboost_log.so.1.55.0 #6 0xb6b44c7c in boost::log::v2_mt_posix::core::push_record_move (boost::log::v2_mt_posix::record&) () from /usr/lib/libboost_log.so.1.55.0 #7 0xb6e66814 in Logger::addLog(Logger::LEVEL, char const*, char const*, int) () from /usr/lib/libtslog.so.1 #8 0x0005ba50 in addLogRusp (iMessageId=2, sMessage=<optimized out>, sProcess=0x8dee8 "Application", eLevel=Logger::LEVEL_INFO) at ../src/RLS-V/Platform/System.inl.h:303 #9 RLS::Application::fnThreadRuspOut (thread=...) at ../src/RLS-V/Application.cpp:1447 #10 0xb6e7aa4c in Thread::startFunction(void*) () from /usr/lib/libtscommon.so.1 #11 0xb6edae38 in start_thread (arg=0xb3eff460) at pthread_create.c:313 #12 0xb6c7c318 in ?? () from /lib/libc.so.6 Backtrace stopped: previous frame inner to this frame (corrupt stack?) This is the global logger initialization (using some custom attributes): BOOST_LOG_GLOBAL_LOGGER_INIT(appLogger, boost::log::sources::severity_logger_mt< robot::log::Severity >) { core::get()->add_global_attribute("TimeStamp", attributes::local_clock()); core::get()->add_global_attribute("ProcessID", AttrProcessId()); core::get()->add_global_attribute("LineCounter", attributes::counter< unsigned int >()); core::get()->add_global_attribute("Process", attributes::current_process_name()); core::get()->add_global_attribute("Scopes", attributes::named_scope ()); core::get()->add_global_attribute("LineID", attributes::counter< unsigned int >(1)); core::get()->add_global_attribute("SimpleTimeStamp", AttrSimpleTime ()); Logger::init(); sources::severity_logger_mt< Severity > lg; return lg; } These are are my macros for logging: //these are needed to convert a macro into a string #define STRINGIFY(x) #x #define TOSTRING(x) STRINGIFY(x) /* NOTE: * __FUNCTION__ is not a macro. It's a char pointer. So we use an empty std::string as basis to concatenate the char* to it */ #define R_LOG_ID(x,y) BOOST_LOG_SEV (robot::log::appLogger::get(), y) << boost::log::add_value("LogID", x) << boost::log::add_value("FLF", ROBOT_FLF) #define R_LOG(x) R_LOG_ID(0, x) #define ROBOT_FLF std::string() + TOSTRING(__FILE__) + ":" + TOSTRING (__LINE__) + " (" + __FUNCTION__ + ")" While "R_LOG_ID" is the only one that is used currently. There are currently three sinks active: syslog, console and a custom sink sending log records via an IPC mechanism (http://www.cs.cmu.edu/~./IPC/) I am currently testing if it will still happen if I deactivate one or more of those sinks. I imagine it will be hard to tell the exact problem from the information above but maybe you guys could point me in the right direction where to dig deeper. I will happily provide any missing information and/or code snippets that could help. Possibly there are well-known common mistakes that can lead to that memory corruption in attribute_value_set? Maybe something like lazy evaluation of log expressions or multi-threading issues? Many thanks in advance for any help! Robin Lorke

2 1

std::future::wait_for() not working in Boost UDP socket async receive operation
by jc.francois＠gmail.com 30 Nov '16

30 Nov '16

The good people over at stackoverflow were not able to help me with this issue that I expected to be trivial. I am writing a UDP server app with Boost that should listen on a socket for 5 seconds and if no datagram has been received within these 5 seconds, move on to do other things. After some research I decided to try the solution based on std::future. The problem is that the call to wait_for() always times out as if no data was received. But if I set a breakpoint on the line that executes after the timeout and that I inspect variables I see that the buffer contains the received datagram and the remote_endpoint object contains the address of the client. In other words the socket receive works as expected but the std::future::wait_for() does not react. why? Here is my test server code: { try { boost::asio::io_service io_service; boost::asio::io_service::work work(io_service); std::thread thread([&io_service]() { io_service.run(); }); udp::socket socket(io_service, udp::endpoint(udp::v4(), 10000)); char recv_buf[8]; for (;;) { ZeroMemory(recv_buf, 8); udp::endpoint remote_endpoint; std::future<std::size_t> recv_length; recv_length = socket.async_receive_from( boost::asio::buffer(recv_buf), remote_endpoint, 0, boost::asio::use_future); if (recv_length.wait_for( std::chrono::seconds(5)) == std::future_status::timeout) { printf("time out. Nothing received.\n"); } else { printf("received something: %s\n", recv_buf); } } io_service.stop(); thread.join(); } catch (std::exception& e) { printf("Error: %s\n", e.what()); } return 0; }

4 5

Question on data structure usage
by Ram 29 Nov '16

29 Nov '16

Hi, I have a map as follows, boost::unordered_map<string, string> sample_map; I would like to look up the keys using wildcards/regex from the user and get the values corresponding to it(get multiple matches). It looked like there is no straightforward way to do it. So, I was thinking as an when I populate the map, I create a seperate data structure to store the keys, so that I can get the values(list) that match my user inputted regex/wildcard search. The I use this list to get the values from the map. What data structure can I use for this purpose? Is my approach correct? Or can I do this directly using the map? Please help me solve this problem. Thanks, -R

4 10

Re: [Boost-users] Do we have plan to support VS 2017?
by senthil vel 29 Nov '16

29 Nov '16

Hi All, I am using VS 2017 for my software development.The last official release of boost ( boost_1_62_0 ) supports VS 2015. When will we get VS 2017 supported boost library? Is there any workaround, till we get the support? Regards, Senthil

2 1

[Boost.DateTime] How to bypass checks in boost::gregorian::date constructor
by dariomt＠gmail.com 28 Nov '16

28 Nov '16

>From the docs I see: "date(greg_year, greg_month, greg_day) Construct from parts of date. Throws bad_year, bad_day_of_month, or bad_day_month (derivatives of std::out_of_range) if the year, month or day are out of range." In my use case, I know for sure that the year, month and date are all in the valid range of values, so all the validity checks done by the library become redundant. Is it possible to somehow bypass those checks?

1 0

Re: [Boost-users] Building Boost 1.62 With Visual Studio 2017 RC
by Trueman, Chris 24 Nov '16

24 Nov '16

1 0

Building Boost 1.62 With Visual Studio 2017 RC
by Trueman, Chris 24 Nov '16

24 Nov '16

2 1

Assertion failure in r_c_shortest_paths.hpp
by Amit Prakash Ambasta 23 Nov '16

23 Nov '16

Hi, I have a sample r_c_shortest_paths use case demonstrated below. However on executing this code, assertion error occurs at /usr/include/boost/graph/r_c_shortest_paths.hpp:473: Assertion `p_cur_label->b_is_valid' failed. I've referred to the prior issue reported at https://svn.boost.org/trac/boost/ticket/11723 However, against his example specified, I can not reproduce the error.

1 0

[release] Boost 1.63.0 Beta 1
by Marshall Clow 21 Nov '16

21 Nov '16

The first beta packages for 1.63.0 beta 1 are now available: <https://sourceforge.net/projects/boost/files/boost/1.63.0.beta.1/> The SHA256 checksums are as follows: 3dbc1bca10941710755c13a00b1ae56d2d37fe90bbadcf9746203194f9d33e3a boost_1_63_0.7z c8b986fd57e436fd88dbc70e51d3e21efa2be3bdf835fa499b2cf6c0a8cc2985 boost_1_63_0.tar.bz2 745d99e4be9c0f324ec7ba15b7d228fd780067f2e8aeae2f16660a4cf6e6a051 boost_1_63_0.tar.gz e66bd6e2f637148c314398b92bc1f3cbdc777ee282f9de7885697afad3d9c202 boost_1_63_0.zip As always, the release managers would appreciate it if you download the archive of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. Thanks! -- The release managers

3 4

beginner boost::statechart questions
by Bedeho Mender 20 Nov '16

20 Nov '16

Hi, I have a few questions about the statechart library. 1) I would like to pass around a representation of the current configuration of a machine, to allow inspection of local variables and active states. The easiest approach would be to just pass around a copy of the machine, but this is not possible since the state_machine class is noncopyable. An alternative could have been to pass around a constant ref/ptr to the machine, but this is also not workable because the inspection will happen in another thread, and synchronisation is not feasible. Any suggestions? One alternative is to create a new snapshot representation, but it will be a headache to keep in synch with the primary machine. 2) A related question is whether there is a good way to start a machine in a given configuration? Using a sequence of events works in principle, but its a very impractical way to do so. For example if one wishes to restore a configuration from a prior session, then the client code has to log the full event history, and it may have a very hard time determining how many events need to be logged to reconstruct the given configuration. Logging and storing *all* events from the prior session will in many cases be wasteful, or even infeasible. 3) Suppose a machine makes a certain callback to client code in a set of different reactions. It would be nice if the client could inspect the currently active state, from which the given reaction is originating. However, my understanding is that the machine is unstable when processing a reaction, hence this is not possible. Is there a way around this? Best Bedeho Mender ᐧ

1 0

[geometry] Cannot compile boost::geometry::intersection
by Stanley Friesen 17 Nov '16

17 Nov '16

I am using boost library version 1.54 with gcc --std=c++11. I am trying a simple use of geometry::intersection as follows: #include <boost/geometry.hpp> #include <boost/geometry/geometries/point_xy.hpp> #include <boost/geometry/geometries/polygon.hpp> #include <boost/geometry/geometries/adapted/boost_polygon.hpp> using namespace boost::geometry; ...... typedef model::d2::point_xy<double> point_xy; model::polygon<point_xy> clipBounds; // add points to clipBounds model::polygon<point_xy> area; // add points to area model::polygon<point_xy> result; if(boost::geometry::intersection(area, clipBounds, result)) { std::cout << std::endl << "Boost intersection, size = " << num_points(result) << std::endl; } If I comment out the call to intersection, everything compiles. With it I get: In file included from /usr/include/boost/serialization/level.hpp:28:0, from /usr/include/boost/serialization/nvp.hpp:31, from ...: /usr/include/boost/mpl/eval_if.hpp: In instantiation of ‘struct boost::mpl::eval_if_c<false, boost::range_const_iterator<boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> > >, boost::range_mutable_iterator<boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> > > >’: /usr/include/boost/range/iterator.hpp:63:63: required from ‘struct boost::range_iterator<boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> > >’ /usr/include/boost/range/value_type.hpp:30:12: required from ‘struct boost::range_value<boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> > >’ /usr/include/boost/geometry/algorithms/intersection.hpp:97:64: required from ‘static bool boost::geometry::dispatch::intersection<Geometry1, Geometry2, Tag1, Tag2, Reverse>::apply(const Geometry1&, const Geometry2&, GeometryOut&, const Strategy&) [with GeometryOut = boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> >; Strategy = boost::geometry::strategy_intersection<boost::geometry::cartesian_tag, boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> >, boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> >, boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian>, void>; Geometry1 = boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> >; Geometry2 = boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> >; Tag1 = boost::geometry::polygon_tag; Tag2 = boost::geometry::polygon_tag; bool Reverse = false]’ /usr/include/boost/geometry/algorithms/intersection.hpp:201:67: required from ‘bool boost::geometry::intersection(const Geometry1&, const Geometry2&, GeometryOut&) [with Geometry1 = boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> >; Geometry2 = boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> >; GeometryOut = boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> >]’ /home/stanley/workspace/worldmodel/metric/map/GISCache.cpp:2492:62: required from here /usr/include/boost/mpl/eval_if.hpp:60:31: error: no type named ‘type’ in ‘boost::mpl::eval_if_c<false, boost::range_const_iterator<boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> > >, boost::range_mutable_iterator<boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> > > >::f_ {aka struct boost::range_mutable_iterator<boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> > >}’ typedef typename f_::type type; Since my code is virtually identical to the sample code in the documentation, I am very puzzled by this. What have I missed? How do I get this to compile? (I do find it odd that this error refers to boost/serialization rather than boost/geometry, but I suppose that has to do with the order of inclusion). -- View this message in context: http://boost.2283326.n4.nabble.com/geometry-Cannot-compile-boost-geometry-i… Sent from the Boost - Users mailing list archive at Nabble.com.

2 4

[statechart] Pass event data to state constructor using triggering_event
by ramonpadilla1＠yahoo.co.uk 16 Nov '16

16 Nov '16

I would like to be able to communicate the data from an event to a state that gets constructed as a result of a transition. From this post in 2009 and this one in 2010 the use of triggering_event() is suggested. However, I can't find an example anywhere that demonstrates how to use it. Can anyone help? Links in the message | Google Groups | | | | Boost - Users - [statechart] Passing pa... | |

1 0

[statechart] Passing parameters from event to State Local Storage
by Christophe Bourez 16 Nov '16

16 Nov '16

I need to maintain a parameter into the state local storage. This parameter is initially contained in the event that causes the transition to the target state. I give hereafter a small illustrative example. typename sc = boost::statechart; class EvTest : public sc::event<EvTest> { public: EvTest(std::size_t val) : value(val) {} std::size_t getValue() const { return this->value; } private: std::size_t value; }; class MyStateMachine; class StSource; class StTarget; class StSource : public sc::simple_state<StSource, MyStateMachine> { public: typedef sc::custom_reaction<EvTest> reactions; sc::result react(const EvTest &event) { // How to pass event.getValue() to the target state ? transit<StTarget>(); } }; class StTarget : public sc::simple_state<StTarget, MyStateMachine> { public: StTarget(std::size_t val) : val(value) {} private: std::size_t value; }; Thanks, Christophe

5 6

Help needed for boost polygon get trapezoid
by Lei Yin 15 Nov '16

15 Nov '16

Hello all, I recently moved to use boost.polygon for doing non-manhattan shape boolean operation, and I'm using get_trapezoids() function to convert output polygons to trapezoids. There're two problems I'm facing and couldn't overcome: 1. Somehow boost.polygon not always give me the largest polygon as possible. In the result, frequently I saw there are two trapezoids are neighboring each other, and they can be perfectly combined into one big trapezoid, but for some reason, boost.polygon give me separated two instead of one. 2. It maybe due to floating point snapping issue (I'm operating on integer base), for some special cases, I got very slim trapezoid like 1 db unit in width. Preferably, this trapezoid Any suggestion to solve above issues would be much appreciated! Thanks in advance. Lei

1 0

How to get response of the questions I posted?
by Bruce 15 Nov '16

15 Nov '16

Hi, I am not familiar with emails list. First time use or I don't known where to post boost.log questions. I found I can't receive the response of my thread by email. I have to check the boost.user archive and I can't response in the archive list. I do subscribed to this list or I can't post. Anybody can help me? Many thanks.

1 0

Questions about extending boost::log sink backend based on app_luncher example
by Bruce 15 Nov '16

15 Nov '16

Hi,I am extending the boost::log backend sink to show log record into GUI ListBox control, which is gui_logger. I modify based on the app_luncher example which extends backend sink of :basic_formatted_sink_backend. Below are the questions that I have for now: 1) when modifying the consume function, I don't know how to get the message body. void consume(logging::record_view const& rec, string_type const& command_line); I using TRACE of visualstudio 2015 to first log the message out into vs2015 console. But I don't know how the get the message from record_view? 2) When I TRACE(command_line.c_str()) of consume function, I logged every record out into vs2015 console. I need to set a filter to only output some of the log. How to set filters with gui_logger? I notice there is sink->set_filter function, but I don't know how to set in my situation.In my scenario, I setup a src::severity_channel_logger (db_logger) with keywords::channel = "dblog", which output to db.log file. I want to use gui_logger to show the latest 200 records on the ListBox. gui_logger should use the same filter with db_logger. gui_logger log the latest 200 records into gui ListBox. db_logger log all the records into text file. So I need to set the same filter with db_logger. 3) I read settings from the ini file for db_logger. I want also to read setting from ini file for gui_logger. How to do it?

1 0

How to wrap boost::log class to user?
by Bruce 14 Nov '16

14 Nov '16

Hi, I am coding a project and I use boost::log. I need to supply the log function to user, but I don't want the user use boost::log directly. I want to wrap the boost::log into my class. But I still want to keep the << cascade feature. Basically, I need to implement a MyLogger class, which support: MyLogger(info) << bla bla bla; MyLogger(trace) << bla bla bla; and in the operator << function, I can use: BOOST_LOG_SEV macro. I don't know how to implement the operator << in MyLogger class. Can anybody helps me, Thanks.

3 2

How to use boost::log to setup multiple logger?
by 刘宝良 14 Nov '16

14 Nov '16

Hi, I want to use boost::log to setup 3 logger for different purpose. Not one logger to have multiple output file. And I also want one logger to have one file output and a GUI output to be viewed by the end user. How to do it? -Bruce

1 0

boost::filesystem::path::iterator and libstdc++ std::search
by Oleksandr Senkovych 11 Nov '16

11 Nov '16

Hi guys. Several days ago I've faced a strange issue with boost::filesystem::path::iterator - it segfaults when used in some STL algorithms. Here's a sample code that crashes: http://melpon.org/wandbox/permlink/58aIbfJWeGgMKMdF I looked at the issue a little bit and discovered that the reason for that is this part of iterator code: const path& dereference() const { return m_element; } So when using std::search libstdc++ has to convert binary predicate to unary for later use in std::find_if: __first1 = std::__find_if(__first1, __last1, __gnu_cxx::__ops::__iter_comp_iter(__predicate, __first2)); It does this by capturing dereferenced value of second iterator (__first2 in a piece of code above) but since iterator is passed by-value, this wrapper holds dangling reference to local member of iterator.m_element. Now according to C++ standard part 24.2.1 [iterator.requirements.general]: 10. Destruction of an iterator may invalidate pointers and references previously obtained from that iterator. So this looks like a violation of a standard by libstdc++ library. Unfortunately I couldn't get my account registered at https://gcc.gnu.org/bugzilla/ and was not able to file a bug, so can I ask you to help me with it?

1 0

boost::filesystem::native
by Christopher J. Pisz 10 Nov '16

10 Nov '16

I did a Google search to see how to check if a given path is valid, preferably using boost. It brought me here: http://stackoverflow.com/questions/10426671/how-to-check-if-path-is-valid-i… Great! I say to myself. I then Google up the boost doc here: http://www.boost.org/doc/libs/1_62_0/libs/filesystem/doc/portability_guide.… I then write myself a test: #include <iostream> #include <sstream> #include <boost/filesystem.hpp> int main() { const std::string test1 = "D:\\Programing Projects\\Git Workspace\\Common\\x64\\Debug"; const std::string test2 = "D:\Programing Projects\\Git Workspace\\Common\\x64\\Debug\\"; const std::string test3 = "D:/Programing Projects/Git Workspace/Common/x64/Debug"; const std::string test4 = "D:/Programing Projects/Git Workspace/Common/x64/Debug/"; if (!boost::filesystem::native(test1)) { std::cout << "Boost says the following path is not valid for the native operating system: " << test1 << std::endl; } if (!boost::filesystem::native(test2)) { std::cout << "Boost says the following path is not valid for the native operating system: " << test2 << std::endl; } if (!boost::filesystem::native(test3)) { std::cout << "Boost says the following path is not valid for the native operating system: " << test3 << std::endl; } if (!boost::filesystem::native(test4)) { std::cout << "Boost says the following path is not valid for the native operating system: " << test4 << std::endl; } return 0; } The Test's Output: Boost says the following path is not valid for the native operating system: D:\Programing Projects\Git Workspace\Common\x64\Debug Boost says the following path is not valid for the native operating system: D:Programing Projects\Git Workspace\Common\x64\Debug\ Boost says the following path is not valid for the native operating system: D:/Programing Projects/Git Workspace/Common/x64/Debug Boost says the following path is not valid for the native operating system: D:/Programing Projects/Git Workspace/Common/x64/Debug/ What is wrong with that path that it says it is not valid for my native Windows 10 operating system?

3 11

Boost.ASIO stuck on some requests?
by Matthieu Brucher 10 Nov '16

10 Nov '16

Hi, I have an app that serves different clients and it is based on Boost.ASIO. My current issue is that if the first client is fast enough (a continuous fast loop with Python module requests), then the other clients may time out with no good reason when trying to connect. Is there a way of figuring out who is actually waiting on who? Maybe the clients are starved because of an issue on their box, or there is an issue in ASIO that serves always the first connection? Or is it Windows? I tried multithreading the server, but that didn't help, and a run with VTune Amplifier shows me that the app is mainly waiting. But if I add a 100ms sleep between requests, then everything is fine. But this is not an acceptable solution, as the clients in real life will want to launch requests all the time. Regards, Matthieu Brucher -- Information System Engineer, Ph.D. Blog: http://blog.audio-tk.com/ LinkedIn: http://www.linkedin.com/in/matthieubrucher

2 2

[boost][process] Formal review results
by Antony Polukhin 09 Nov '16

09 Nov '16

The Boost.Process library is accepted. Congratulations to Klemens, and thanks to everybody who reviewed the library! The votes were as follows: + Johannes - Niall Douglas +/- Tom Kent +/- Nat Goodspeed + Paul A. Bristow +/- Bjorn Reese + Edward Diener + Boris Schäling +/- Raphaël Londeix + Klaim - Joël Lamotte Legend: + accept - decline +/- accept conditionally Separate thanks to Gavin Lambert for providing a solution to deadlocking problem. Additional thanks to Nat Goodspeed, Niall Douglas, Gavin Lambert, Raphaël Londeix and Bjorn Reese for spending significant amount of time on discussing, reviewing or testing the library. -- Quick review summary -- During the review multiple technical issues were raised and as far as I know, Klemens already working on them. The biggest win of the review - is a fix for possible deadlock with pipes. The most controversial part of the library is it's interface. Many comments were addressing: * passing arguments * starting process right in `system(...)` function Current approaches have benefits and drawbacks, other approaches have different benefits and drawbacks. At this point some people agree that the current approach is the lesser evil. Reviewers also wished to have better/richer documentation. P.S.: Please continue with the discussion and report issues that would help to improve the library. -- Best regards, Antony Polukhin

1 0

Visual Studio "15" Preview Update 5 configuration
by csiga.biga＠aol.com 09 Nov '16

09 Nov '16

Hi fellow users! This is my first message to this list, so take it easy if something’s not right. I wanted to build Boost with the latest Visual Studio spin, dubbed „15” Update 5 (RC coming sometime in November), but the configuration scripts do not quite work. Because _MSC_VER is 1910, I get the unkown compiler pragma warning, but what is more vexing, is that the configuration is not right, I get compilation errors in boost::functional, because std::unary_function has been deprecated since C++11, and VS „15” has removed this function from the STL. The _MSC_FULL_VER is 191024516, and I wanted to use the new toolset, because it has significantly improved in terms of conformance, most notably support for generalized constexpr. (See full list in the link) Can someone help with patching the configuration scripts? I would rather not start defining things to get deprecated features into scope again, but if nothing else works as a hotfix, than so be it. Thanks in advance, Máté

1 0

Help in calculating the size of a boost::unordered_map
by Ram 08 Nov '16

08 Nov '16

Hi, I would like to calculate the size of my filled up boost::unordered_map including the house keeping. I was thinking of sizeof(boost:unordered_map mymap). I asked this question on stackoverflow but they say that wont help. Can somebody tell me an easy way to find the size including the housekeeping that it takes? The boost::unordered_map stores a std::string as the key and a pointer to my class object as the value. Thanks, Ram

5 7

An Asio based header-only asynchronous MySQL client library
by Cheng Lian 07 Nov '16

07 Nov '16

Hey all, Here is an Asio based header-only asynchronous MySQL client library called Amy (*A*synchronous *My*SQL). https://github.com/liancheng/amy In short, this library enables you to work with MySQL in both asynchronous and blocking ways. Links to examples are included in the README file. Haven't got time and energy to write comprehensive documents, though. The interesting thing is that, I wrote this library years ago as an exercise, open sourced it, and then basically forgot about it. However, recently an European developer contacted me and said that they used it in one of their game projects in production and it was "amazing". So I decided to spend some time to polish it a little bit and send it out here to see whether there are anyone else who are interested in it. Please let me know what you think about it. Thanks! Best, Cheng

1 0

Problem compiling a code that uses Boost
by Fernando E Alva Manchego 04 Nov '16

04 Nov '16

Hello, I'm trying to compile a code that uses boost. The code is this one: http://people.eng.unimelb.edu.au/tcohn/t3.html The version of boost installed in the machine is: 1.41 The machine where I'm running this code is a Scientific Linux release 6.8 (Carbon). The detailed error message that I get can be seen here: http://pastebin.com/ADj4j6k0 Basically, the errors messages are like this: undefined reference to `boost::program_options::options_description::options_description(...) undefined reference to `boost::program_options::validation_error::get_template(...) -lboost_program_options is in the compilation line. And I've checked using 'locate' that /usr/lib64 (as appears in the compilation line) contains: /usr/lib64/libboost_program_options-mt.so /usr/lib64/libboost_program_options-mt.so.5 /usr/lib64/libboost_program_options.so /usr/lib64/libboost_program_options.so.5 I would really appreciate any help you could help me with this error. Best, Fernando

1 0

Re: [Boost-users] build of datetime library fails
by LAMOTTE Thierry 03 Nov '16

03 Nov '16

Dear Andreas and Marcel, I checked my Visual Studio 13 Update : it is Update 5, so on this side it is ok. But Andreas you were perfectly right : as soon as I get Boost release 1.56, compilation completes with no warning and no error. I retry Boost 1.62 but it still does not work : it claims for a msvc internal error C1001. Sorry I won't keep investigating since I do not have time for that. I get at least one that works and for now it is enough to help me move on on my project matters that are quite far for boost. I greatly thank both of you for your help, I really appreciate. Best regards, Thierry Note: I do no know why I could not login with my email/password and reply directly on http://boost.2283326.n4.nabble.com/build-of-datetime-library-fails-td468 9472.html#a4689486

1 0

build of datetime library fails
by LAMOTTE Thierry 03 Nov '16

03 Nov '16

Dear Boost community, For the purpose of a project that uses Boost libraries, I tried rebuild Boost but I failed. I would please need some help to complete that building. My context is Microsoft Windows 7, 32 bits, Visual Studio 13 (msvc-12), Boost 1.54.0 My goal is to the create static libraries : libboost_chrono, regex, system, thread and datetime. I initially used a tutorial from the Nordic's github to build Boost : https://github.com/NordicSemiconductor/pc-ble-driver My last try was with Boost 1.54.0 (the one used in the mentioned tuto), the build of datetime library fails (I attached the ouput) and frankly speaking I do not know where I should start looking for. If anyone could help me ? For note, at early stage, I tried with Boost 1.62.0, but the outcome was even worse, I gave up. Best regards, Thierry

3 3

Microsoft and hana
by Dan Bloomquist 31 Oct '16

31 Oct '16

I'm sorry, I take it back. Things were fine until I included <boost/hana.hpp> I had been testing with <boost/hana/core/when.hpp> and the likes of: template<class T> constexpr T pi = T(3.1415926535897932385); // variable template which would not work until I patched. And to quote: In this release, we've updated the C++ compiler and standard library with enhanced support for C++11 and C++14 features, as well as preliminary support for certain features expected to be in the C++17 standard. The most notable compiler changes include complete support for generalized constexpr. Maybe next time.... Best, Dan.

5 4

Microsoft and hana
by Dan Bloomquist 29 Oct '16

29 Oct '16

I did a quick search here and didn't find anything on this. But I just patched up VS2015 with 'Visual Studio "15" Preview 5' <https://www.visualstudio.com/news/releasenotes/vs15-relnotes> and downloaded boost_1_62_0 The compiler now handles variable templates and I've compiled and run some simple hana tests. I did have to comment line 74 in "..\boost\hana\config.hpp". I just thought I'd drop a heads up for those, like me, that wanted to use hana with the Microsoft compiler. Best, Dan.

1 0

Re: [Boost-users] Boost Coroutine
by Emile Cormier 29 Oct '16

29 Oct '16

On 16-10-19 02:57 AM, Oliver Kowalke wrote: > > I'm not the maintainer of boost.asio, so I don't know if an upgrade is > planed - you might ask Christopher Kohlhoff. > This is a bit worrisome to me. We are using the Boost.Asio + Boost.Coroutine integration _extensively_ in our project. Did the API change from Coroutine1 to Coroutine2? Is it simply a matter of including from boost/coroutine2/xxx instead of boost/coroutine/xxx based on some preprocessor macro being defined?

2 1

boost 1.50 unable to make regex_match to work
by MAURICE Jean 27 Oct '16

27 Oct '16

1) Hi Kai, I wrote const_iterator BOOST_REGEX_CALL end()const { // JME 27/10/16 pour savoir si on passe là, je crée une division par 0 en // esperant que le compilateur ne la détecte pas int ijme1, ijme2; ijme2 = 1; ijme1 = 2; --ijme2; ijme1 = ijme1 / ijme2; return (!this->m_status ? 0 : this->m_expression + this->m_expression_len); // return (this->m_status ? 0 : this->m_expression + this->m_expression_len); JME 26/10/16 } Hoping the divide by 0 error would be thrown but it never appears. So I don't think this bug is annoying me. 2) As I am new to boost and regex I tried a simple test : string pattern = "GHI+"; string chaineatester = "ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789"; boost::regex boost_pattern( pattern ); boost::smatch what; int errjme = boost::regex_match( chaineatester, what, boost_pattern ); if (errjme == 1) { *outputLog << "test 1: GHI+ a été trouvé" << endl; } else { *outputLog << "test 1: GHI+ n'a pas été trouvé" << endl; // what[0] contains the whole string // what[1] contains the response code // what[2] contains the separator character // what[3] contains the text message. *outputLog << " what[0]:" << what[0] << endl \ << " what[1]:" << what[1] << endl \ << " what[2]:" << what[2] << endl \ << " what[3]:" << what[3] << endl; } string pattern2 = "GHI"; boost::regex boost_pattern2( pattern2 ); errjme = boost::regex_match( chaineatester, what, boost_pattern2 ); if (errjme == 1) { *outputLog << "test 1bis: GHI a été trouvé" << endl; } else { *outputLog << "test 1bis: GHI n'a pas été trouvé" << endl; *outputLog << " what[0]:" << what[0] << endl \ << " what[1]:" << what[1] << endl \ << " what[2]:" << what[2] << endl \ << " what[3]:" << what[3] << endl; } And here is what I get : test 1: GHI+ n'a pas été trouvé what[0]: what[1]: what[2]: what[3]: test 1bis: GHI n'a pas été trouvé what[0]: what[1]: what[2]: what[3]: What am I doing wrong ? Jean

2 4

[geometry] Stable and fast rtree serialize/de-serialize
by 邓尧 27 Oct '16

27 Oct '16

Hi all, How can I serialize/deserialize a Boost.Geometry rtree reliably and efficiently ? I tried the experimental rtree serialization support built-in (-DBOOST_GEOMETRY_INDEX_DETAIL_EXPERIMENTAL=1), I found that the implementation was unstable and failed to deserialize sometimes. I don't even know whether it corrupted any of the tree nodes. I also implemented a slow hack: save all tree nodes during serialization and rebuild the rtree during deserialization. I want something faster. Serialization time isn't important to me, I just need a faster deserialization (as fast as the experimental implementation) Thanks

1 0

Building Boost with VS15 Preview 5
by Trueman, Chris 26 Oct '16

26 Oct '16

2 2

Can't catch Boost.Asio exceptions inside coroutines
by Sergey Shpikin 25 Oct '16

25 Oct '16

I have this little example of Boost.Asio code: http://codepad.org/tuQedXI7 It works as expected on Linux producing 1 2 Caught Host not found (authoritative) but on Windows it crashes with: 1 2 terminate called after throwing an instance of 'boost::system::system_error' what(): Unknown error Tested on Windows Server 2008, Windows 7 and Wine, everything is the same. I'm compiling on Linux for Windows with MXE ( http://mxe.cc/ ) on GCC 4.9.4, Boost version is 1.60.0. I'm really stuck at this point as nothing in Google looks a valid solution for the case and I already have a working application on Linux but it crashes on any network error on Windows. On Windows coroutines prevent any exceptions from being caught when the program is compiled with -O1/2/3 but they're caught with -O0 or -Os (see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54267 — this is about GCC on FreeBSD but the same seemingly applies to MinGW). However, boost's own exceptions, like the aforementioned boost::system::system_error, still can't be caught.

1 0

boost @ Meeting C++ 2016
by Jens Weller 24 Oct '16

24 Oct '16

Hello boost community, a short and final reminder, that the Meeting C++ conference is just a few weeks away! A few tickets are still available, here is the schedule: https://meetingcpp.com/index.php/schedule16.html The schedule also has the link to the student program and diversity tickets! Also there is still a few places available in the boost workshop with Boris Schäling and Michael Caisse. I plan to have a meetup for boost users in one of the breaks in the upper lounge, so that the boost communtiy is able to actually meet at Meeting C++! thanks, Jens Weller

1 0

boost asio ssl read issue
by Ananth 24 Oct '16

24 Oct '16

Hi, I have posted the question here at StackForge with all the details. http://stackoverflow.com/questions/40163626/boost-asio- ssl-not-working-as-expected-when-used-with-null-buffers Basically, http://www.boost.org/doc/libs/1_40_0/doc/html/ boost_asio/overview/core/reactor.html did not work when used with ssl. With plain-tcp steam socket, it works fine. o If we do ssl_socket->lowest_layer().async_read_some(null_buffers(), read_cb), then we do get all data in read_cb, but read_cb keep getting called endlessly (and read_some then returns 0, with error 11 resource unavailable) (This causes cpu remain over-utilized for ever) If we do ssl_socket->async_read_some(null_buffers(), read_cb), then it works fine with small amounts of data. When larger data is to be received (~20MB or so), then not all data is received. around 1% of data towards the end is never received by the application. My guess is that data is sitting in openssl library some where I tried with latest ssl and boost code, but that did not help either. Can some one please help ? Thanks, Ananth

1 0

Filesystem recursive iterator issues
by mlimber 24 Oct '16

24 Oct '16

I have this code, which does a simple recursive directory iteration and prints each directory entry and then does it again ( http://coliru.stacked-crooked.com/a/0bfab95a513ebed8 ): #include <boost/filesystem.hpp> #include <boost/range/iterator_range.hpp> #include <iostream> namespace fs = boost::filesystem; int main() { try { const auto iter = fs::recursive_directory_iterator{ "." }; for( const auto& entry : boost::make_iterator_range( iter, {} ) ) { std::cout << entry << "\n"; } // Rinse and repeat std::cout << "\n"; for( const auto& entry : boost::make_iterator_range( iter, {} ) ) // CRASH -- Replace 'iter' with 'fs::recursive_directory_iterator{"."}' and it will work. //for( const auto& entry : boost::make_iterator_range( fs::recursive_directory_iterator{"."}, {} ) ) { std::cout << entry << "\n"; } } catch( const std::exception& e ) { std::cerr << e.what() << "\n"; } catch( ... ) { std::cerr << "Unknown exception.\n"; } } As you can see at Coliru, it crashes. (It also crashes on Visual Studio 2012 and with Boost 1.55.0 and on Coliru with <experimental/filesystem> instead of Boost.) Similarly, using a filesystem iterator with std::distance() fails when the iterator passed in is used again later (with boost: http://coliru.stacked-crooked.com/a/1b06dca057872762 and with experimental/filesystem: http://coliru.stacked-crooked.com/a/7bd5e73f1444619d ). It seems that something in the state of the *constant* iterator gets confused or corrupted after it is advanced to the end. I have a workaround for it commented out in the code. I found this possibly related issue: https://svn.boost.org/trac/boost/ticket/11910 Am I missing something? Should I file a new bug report? Cheers! M

1 0

When to use BOOST_ALL_DYN_LINK?
by Florian Lindner 24 Oct '16

24 Oct '16

Hello, http://www.boost.org/doc/libs/1_62_0/libs/log/doc/html/log/installation/con… says: BOOST_LOG_DYN_LINK If defined in user code, the library will assume the binary is built as a dynamically loaded library ("dll" or "so"). Otherwise it is assumed that the library is built in static mode. This macro must be either defined or not defined for all translation units of user application that uses logging. This macro can help with auto-linking on platforms that support it. BOOST_ALL_DYN_LINK Same as BOOST_LOG_DYN_LINK but also affects other Boost libraries the same way. We build our library in a dynamic and a static version using SCons: staticlib = env.StaticLibrary ( target = buildpath + '/libprecice', source = [sourcesPreCICE] ) env.Alias("staticlib", staticlib) solib = env.SharedLibrary ( target = buildpath + '/libprecice', source = [sourcesPreCICE] ) env.Alias("solib", solib) Both have BOOST_LOG_DYN_LINK set: env.Append(CPPDEFINES=["BOOST_LOG_DYN_LINK"]) However, I wonder if this is correct. Should DYN_LINK only be set when building the dynamically linked lib? Thanks, Florian

2 1

Update the index of a hashed_non_unique entry in boost::multiindex
by Ram 24 Oct '16

24 Oct '16

I have a boost::multiindex container which has an index as follows : boost::multi_index::hashed_non_unique< boost::multi_index::tag<IndexByNonUniqueId>, boost::multi_index::const_mem_fun<StoredObj, std::string, &StoredObj::getNonUniqueIdString> > This ID comes in as ""(empty string) when I initially get the object. I add it to the multiindex at this point. But later in the course of the program the ID gets populated using its "setNonUniqueId" method. At this point of time inside "setNonUniqueId" I would like to update the index to the object(in the multiindex) as well(while the ID is being updated from "" to something concrete). How do I do this? How do I locate the specific object and update the index? -R

2 4

upgrade from boost 1.39 to boost 1.50. Issue with regex_match
by MAURICE Jean 21 Oct '16

21 Oct '16

Hi, I am 'upgrading' a huge C++ app from VS2005 (32bits) to VS2010 (64 bits) and boost 1.39 to boost 1.50. This app runs both under Windows and Linux. In a function that searchs subdirectories and files of a given directory, we get the list of all the elements and then this list is filtered by : if(true==boost::regex_match(sAdaptation, what, childNode.infoNode.rFullPathFilePattern)) sAdaptation is ".\TEST\un_noeud" (this subdirectory exists) childNode.infoNode.rFullPathFilePattern is something like {m_pimpl={...}} And regex_match always returns false. If you can give me information about what is happening ... Jean

4 10

build boost 1.58 failed on centos 7.2
by Glenn WANG 20 Oct '16

20 Oct '16

hi, I try to build boost 1.58 on CentOS, but it cannot be done, there're many errors. could anybody help? thanks. ============================== ./b2 --with-log -q gcc.compile.c++ bin.v2/libs/system/build/gcc-4.8.5/release/threading-multi/error_code.o In file included from libs/system/src/error_code.cpp:19:0: ./boost/system/detail/error_code.ipp:48:27: error: expected ‘;’ at end of member declaration const char * name() const BOOST_SYSTEM_NOEXCEPT; ^ ./boost/system/detail/error_code.ipp:48:33: error: ‘BOOST_SYSTEM_NOEXCEPT’ does not name a type const char * name() const BOOST_SYSTEM_NOEXCEPT; ^ ./boost/system/detail/error_code.ipp:56:32: error: expected ‘;’ at end of member declaration const char * name() const BOOST_SYSTEM_NOEXCEPT; ^ ./boost/system/detail/error_code.ipp:56:38: error: ‘BOOST_SYSTEM_NOEXCEPT’ does not name a type const char * name() const BOOST_SYSTEM_NOEXCEPT;

1 0

Boost Coroutine
by Miguel Portilla 19 Oct '16

19 Oct '16

Hello, Using Boost 1.62, I am seeing the following warning when I build my project. warning : Boost.Coroutine is now deprecated. Please switch to Boost.Coroutine2. To disable this warning message, define BOOST_COROUTINE_NO_DEPRECATION_WARNING. I haven't found any documentation on what exactly this means or how to 'switch'. Can someone please point me to some docs or explain what 'switching' entails? Thanks, -M

2 3

Re: [Boost-users] [Boost-build] [System] Link issues using BOOST_ERROR_CODE_HEADER_ONLY
by Matthias Seemann 17 Oct '16

17 Oct '16

Hi, > We decided to fix these by defining the macro BOOST_ERROR_CODE_HEADER_ONLY > according to this link: > > http://www.boost.org/doc/libs/1_56_0/libs/system/doc/reference.html#Header-… > > However, when building Boost itself with this macro defined, we're > encountering several problems: > ... > 2) We get multiple definitions of "boost::system::throws" > Defining the macro BOOST_SYSTEM_NO_DEPRECATED (see that doc page above) resolved the issue of multiple definitions of "boost::system::throws". Matthias

1 0

boost graph pruning vertices (nodes)
by Brian Davis 14 Oct '16

14 Oct '16

In reading http://www.boost.org/doc/libs/1_62_0/libs/graph/doc/adjacency_list.html regarding Iterator and Descriptor Stability/Invalidation it leaves the impression that when using vecS there is no real good way to remove nodes. as example: typedef adjacency_list<listS, vecS> Graph; // VertexList=vecS all cases are wrong and typedef adjacency_list<listS, listS> Graph; // VertexList=listS where only one case is correct which leave the programmer walking the mine field. Of course same can be said for stl. My goal to remove graph vertices based on the value of the connected components. I currently have a method which uses connected components to generate a connected components list. I then generate a histogram of the connected components values thus giving me how many vertices are connected and what the connection property value is... assuming I understand connected components however I have thought I understood portions of boost only to find through some brain warp and folding my thought process back on itself like an origami master that I came to understand how certain parts work. vertid, component 0 0 1 0 2 0 3 0 4 1 5 1 6 2 7 2 8 2 9 2 10 2 11 2 12 3 13 3 so in this simple example vert ids [0-3] are connected in subnet 0 with a total of 4, [4-5] are connected in sub net 1 with a total of 2, [6-11] are connected in subnet 2 with a total of 6, and [12-13] is connected in subnet 3 with a total of 2. Histogram yields connected component value and number of vertices that have that value in the bin component : bin counts 0: #### 1: ## 2: ###### 3: ## etc for say subnet/subgraph less than 4 would yield the filtered histogram: 1: ## 3: ## using values 1, and 3 from filtered histogram I can then find the vertex ids to filter. Yielding vertices 4,5,12, and 15 to be removed which would remove subnets 1 and 3. 4 1 5 1 12 3 13 3 I tried to use boost::accumulators::density and maybe I have a different idea of what a histogram really is, but for a typical histogram density is just plane broken due to the seemingly use of count for number of bins (seems to ignore tag::density::num_bins) and associated logic. accumulator_t acc( tag::density::num_bins = n_bins, tag::density::cache_size = n_bins/2 ); Sure wish there was a boost::accumulators::histogram that just did what we need as programmers. I am unsure as to how much boost coolaid to drink before finding any use for density. I did find this relating to the seemingly not as advertised implementation of density http://lists.boost.org/Archives/boost/2008/01/132801.php. From http://www.boost.org/doc/libs/1_62_0/doc/html/accumulators/user_s_guide.html "The tag::density feature returns a histogram of the sample distribution. For more implementation details, see density_impl." err huh no it does not... at least in my testing. It would also be great if the abcicissas (intervals) were some how obtainable to compare to the ordinates (bin counts) . Note the histogram.hpp attached there. So I write by own histogram code using stl. I digress on that. So as I said I then filter the vertex vs connected components data based on a threshold say 4 to remove all vertices that are not connected to 4 or more vertices in a subnet/subgraph So I then have a list of vertices (subnets/subgraphs) that I wish to prune from the graph thus these questions: Question 1: if finding a list of vertices to erase, sorting them, and then using, a reverse iterator to remove(*itr, g) would this also not work? If this works why is it now shown as an example of vecS vertex removal working? Question 2: Should there not be a boost graph-ish way of doing this such as coloring vertices to be pruned by possibly adding property prune = true. then maybe a future call to prune(g) Question 3: Possibly there is a way to get filtered_graph to do the trick? Statement: it is unfortunate the use of the term vertex/vertices in stead of node(s) in boost graph. As some graphs have a vertex (euclidean geometry) such as a graph of the center-lines of the vascular network of a brain while other graphs do not. It is very confusing in this instance to keep the two strait in code. Ugh!

3 2

Re: [Boost-users] [Serialization] Free-standing serialize function for "enum class"
by Bjorn Reese 13 Oct '16

13 Oct '16

On 10/13/2016 06:56 PM, Rüdiger Berlich wrote: > I have for a while suspected a problem with the serialization of an „enum class“ item (currently with Boost 1.61 on Ubuntu 16.04), and have written a small test program to further examine any potential problems. While the generated XML looks fine and I cannot see any problems with the enum class, my custom, free-standing „serialize“ function does not get called. Boost.Serialization automatically converts an enum into an int before it is serialized.

2 1

[Serialization] Free-standing serialize function for "enum class"
by Rüdiger Berlich 13 Oct '16

13 Oct '16

Hi there, I have for a while suspected a problem with the serialization of an „enum class“ item (currently with Boost 1.61 on Ubuntu 16.04), and have written a small test program to further examine any potential problems. While the generated XML looks fine and I cannot see any problems with the enum class, my custom, free-standing „serialize“ function does not get called. It is modelled after the examples for non-intrusive serialization, so I do not understand the reason behind this. Any idea ? /*************************************/ // Compile with g++ --std=c++14 -o enum_ser -I/opt/boost/include/ -L/opt/boost/lib enum_ser.cpp -lboost_serialization #include <boost/serialization/nvp.hpp> #include <boost/archive/xml_oarchive.hpp> #include <boost/archive/xml_iarchive.hpp> #include <iostream> #include <sstream> enum class test_enum : int {a=5,b=6}; namespace boost { namespace serialization { //----------------------------------------- template<typename Archive> void serialize(Archive &ar , test_enum &x, const unsigned int){ std::cout << "Serializing via custom serialize function" << std::endl; int t = 0; if (Archive::is_saving::value) { t = static_cast<int>(x); ar & t; } else { ar & t; x = static_cast<test_enum>(t); } } //----------------------------------------- } } int main(int argc, char **argv){ std::ostringstream oss; test_enum x = test_enum::a; { boost::archive::xml_oarchive oa(oss); oa << BOOST_SERIALIZATION_NVP(x); } std::cout << oss.str() << std::endl; } /*************************************/ Output of the program (note: the „Serializing via custom serialize function“ does not appear) : /*************************************/ <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <!DOCTYPE boost_serialization> <boost_serialization signature="serialization::archive" version="14"> <x>5</x> </boost_serialization> /*************************************/ Thanks and Kind Regards, Beet

1 0

Boost test failures on arm platform
by Carlos Ferreira 13 Oct '16

13 Oct '16

Hello! I'm cross-compiling Boost to an arm platform and because of that, boost fails to execute the cxx11_* tests and then it outputs the information that the compiler does not support a series of cxx11_* capabilities. Is there a way to disable these library tests, when cross-compiling? -- Carlos Miguel Ferreira Researcher at Telecommunications Institute Aveiro - Portugal Work E-mail - cmf(a)av.it.pt Skype & GTalk -> carlosmf.pt(a)gmail.com LinkedIn -> http://www.linkedin.com/in/carlosmferreira

2 16

Announcing version 3 of the cxx_dual library
by Edward Diener 12 Oct '16

12 Oct '16

I have created version 3 of the cxx_dual library. version 3 is a large rewrite of the documentation to simplify the use of the library, as well as a change in the directory structure so that the basic usage of the library is through a single header file and the use of a namespace alias, and not through the macro interface. As in: #include <boost/cxx_dual/regex.hpp> void SomeFunction() { cxxd_regex_ns::regex re("A regular expression etc."); bool result(cxxd_regex_ns::regex_match("Some string...",re)); // etc. } What ! No macros ! Actually a few macros still exist for testing which dual library has been chosen and overriding the dual library chosen, but the basic functionality means almost no macros in user code. The library is available at https://github.com/eldiener/cxx_dual.git. What is it ? The Cxx Dual library, or CXXD for short, is a C++ macro header-only library which chooses between using a Boost library or its C++ standard equivalent library for a number of different C++ implementations, while allowing the end-user to use the same code to program either choice. An implementation is a Boost library which has a C++ standard library equivalent whose public interfaces are nearly the same in both cases. An 'implementation' is called a 'mod' for short and each of the possible Boost or C++ standard implementations for that mod are called a 'dual library'. The Cxx Dual library does this by automatically choosing either the Boost library or the C++ standard library for a particular mod, including the correct header file(s) needed for the dual library chosen, and creating a namespace alias for the namespace of the dual library chosen. CXXD also provides a macro-based solution for distinguishing between the Boost version and the C++ standard version of a dual library so that specific code for a particular dual library choice may be written in those cases where the public interfaces diverge.

1 0

Issues trying to use boost::unordered_map
by Ram 11 Oct '16

11 Oct '16

Hi, I am trying to use a boost::unordered_map as a member of my class. The unordered_map is defined as, boost::unordered_map<int, int> a; as a private member in the class. I have included #include "boost/unordered_map.hpp" using namespace boost; This is the compilation error I get, x_objs.cpp c:\codeworks\common\lib\boost\boost\unordered\detail\buckets.hpp(767) : error C2059: syntax error : '(' c:\codeworks\common\lib\boost\boost\unordered\detail\buckets.hpp(766) : while compiling class template member function 'void boost::unordered::detail::functions<H,P>::construct(bool,const H &,const P &)' with [ H=boost::hash<int>, P=std::equal_to<int> ] c:\codeworks\common\lib\boost\boost\unordered\detail\table.hpp(152) : see reference to class template instantiation 'boost::unordered::detail::functions<H,P>' being compiled with [ H=boost::hash<int>, P=std::equal_to<int> ] c:\codeworks\common\lib\boost\boost\unordered\detail\unique.hpp(179) : see reference to class template instantiation 'boost::unordered::detail::table<Types>' being compiled with [ Types=boost::unordered::detail::map<std::allocator<std::pair<const int,int>>,int,int,boost::hash<int>,std::equal_to<int>> ] c:\codeworks\common\lib\boost\boost\unordered\unordered_map.hpp(74) : see reference to class template instantiation 'boost::unordered::detail::table_impl<Types>' being compiled with [ Types=boost::unordered::detail::map<std::allocator<std::pair<const int,int>>,int,int,boost::hash<int>,std::equal_to<int>> ] c:\codeworks\sample_issue.h(276) : see reference to class template instantiation 'boost::unordered::unordered_map<K,T>' being compiled with [ K=int, T=int ] li_pip.cpp ld_pip.cpp pip.cpp . . . Can someone please help me? Thanks, Ram

6 39

[fiber] Asio autoecho example crashes (VS 2015 u3)
by DePizzottri 11 Oct '16

11 Oct '16

Hi all, I'm found that asio autoecho example crashes after main's return statement. Debugger shows write access from the fiber scheduler to the already destroed io_service. Substitution reference to io_service: boost::asio::io_service & io_svc_; in round_robin algo to the shared_ptr: boost::shared_ptr<boost::asio::io_service> io_svc_; with approprieate correction of the other code solves the problem. Maybe I misunderstood something in the descrition from documentation? Or its some kind of feature? -- View this message in context: http://boost.2283326.n4.nabble.com/fiber-Asio-autoecho-example-crashes-VS-2… Sent from the Boost - Users mailing list archive at Nabble.com.

2 4

Re: [Boost-users] [ASIO] Do coroutines allow serving multiple clients at once?
by mmarkd9＠libero.it 10 Oct '16

10 Oct '16

Thanks, does spawning a coroutine also spawn a new thread? I'd be inclined to think so from what you told me

2 1

R: Re: [ASIO] Do coroutines allow serving multiple clients at once?
by mmarkd9＠libero.it 10 Oct '16

10 Oct '16

Thanks, does spawning a coroutine also spawn a new thread? I'd be inclined to think so from what you told me ----Messaggio originale---- Da: "Oliver Kowalke" <oliver.kowalke(a)gmail.com> Data: 10-ott-2016 15.19 A: "boost-users"<boost-users(a)lists.boost.org> Ogg: Re: [Boost-users] [ASIO] Do coroutines allow serving multiple clients at once? 2016-10-10 9:44 GMT+02:00 mmarkd9(a)libero.it <mmarkd9(a)libero.it>: I'd like to know if this code is able to serve multiple clients connecting at the same time to the server. I would say no. You spawn only one coroutine that calls in the for-loop async. operations of accept(), read() and write() in a sequence. No other client is able to connect to your server, e.g. connect() on the client side returns, until you enter accept() again. In order to serve multiple clients at the same time you need to spawn a coroutine that accepts new connections and for each client request (read()/write() operations) you need to spawn a new coroutine.

1 0

Re: [Boost-users] [ASIO] Do coroutines allow serving multiple clients at once?
by mmarkd9＠libero.it 10 Oct '16

10 Oct '16

Thanks, does spawning a coroutine also spawn a new thread? I'd be inclined to think so from what you told me

1 0

[Boost.Filesystem] crashes in static destruction of global string object
by Nguyen Huu Hai 10 Oct '16

10 Oct '16

Hello, libs/filesytem/src/portability.cpp defines valid_posix as a std::string object instead of a const char * pointer. May I know if there are reasons for that? I'm using Boost.Filesystem as a shared library and my processes crash on exit with stack traces pointing to the static destruction of valid_posix. Making it const char* fixes the crashes. Regards, Hai

2 2

[ASIO] Do coroutines allow serving multiple clients at once?
by mmarkd9＠libero.it 10 Oct '16

10 Oct '16

I'm using ASIO with coroutines2 to create a ssl echo server. The code I've been experimenting is the following: http://nopaste.linux-dev.org/?1120051 While this is highly readable compared to the asynchronous callbacks version (thanks coroutines), I'd like to know if this code is able to serve multiple clients connecting at the same time to the server. In theory, every time I return control to the io_service object (i.e. I yield in the spawn coroutine) it should take care of whatever connection is pending / buffered / scheduled to be accepted next, right? Is this a reliable way to handle multiple requests? I don't plan on supporting massive workloads (e.g. 500k connections at once) but having some resilience would be nice indeed. Any other thoughts/tips are also warmly welcome.

2 1

Epoch to date
by Philippe de Rochambeau 09 Oct '16

09 Oct '16

Hello, how do you convert an Unix epoch (e.g., 1476015285) to a formatted date string (e.g., 1984-01-01) with Boost? Many thanks. Philippe

2 1

BoostLog and BoostASIO don't seem to play nice together
by james 08 Oct '16

08 Oct '16

Hi, I'm facing pretty much the same issue as was reported here in 2014: http://boost.2283326.n4.nabble.com/Boostlog-and-ASIO-crash-in-shared-librar… In short, I have a .so that wraps BoostASIO to create a HTTP client. Loading this .so into a program that also uses BoostLog results in either a segfault or no callbacks being fired (even async_resolve which I believe should eventually time-out). Removing all uses of and linking to BoostLog in the main program makes it all work again. Before I try to produce a minimum example, is this a known issue? Code is built with BOOST_LOG_DYN_LINK, asio is header only. We're using boost 1.55, and g++ (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4 Thanks James

1 0

graph strongly connected components
by Mika S 07 Oct '16

07 Oct '16

I am trying to use the implementation for strongly connected components http://www.boost.org/doc/libs/1_61_0/libs/graph/doc/strong_components.html Is this the iterative or the recursive implementation of tarjan's algorithm ?

2 2

GCC 5.3.0 failing Features Check when building Boost
by Carlos Ferreira 06 Oct '16

06 Oct '16

Hello I'm having some issues regarding the features check, when build Boost using OpenWRT GCC 5.3.0 cross-compiler for armv7. I'm building against musl. I have passed -std=c++14 to the cxxflags, but it seems to have no effect. This is the features output > - 32-bit : yes > - arm : yes > - symlinks supported : yes > - C++11 mutex : yes > - lockfree boost::atomic_flag : no > - Boost.Config Feature Check: cxx11_auto_declarations : no > - Boost.Config Feature Check: cxx11_constexpr : no > - Boost.Config Feature Check: cxx11_defaulted_functions : no > - Boost.Config Feature Check: cxx11_final : no > - Boost.Config Feature Check: cxx11_hdr_tuple : no > - Boost.Config Feature Check: cxx11_lambdas : no > - Boost.Config Feature Check: cxx11_noexcept : no > - Boost.Config Feature Check: cxx11_nullptr : no > - Boost.Config Feature Check: cxx11_rvalue_references : no > - Boost.Config Feature Check: cxx11_template_aliases : no > - Boost.Config Feature Check: cxx11_thread_local : no > - Boost.Config Feature Check: cxx11_variadic_templates : no > - has_icu builds : no > warning: Graph library does not contain MPI-based parallel components. > note: to enable them, add "using mpi ;" to your user-config.jam > - zlib : yes > - iconv (libc) : no > - iconv (separate) : yes > - icu : no > - icu (lib64) : no > - native-atomic-int32-supported : yes > - pthread-supports-robust-mutexes : yes > - compiler-supports-visibility : yes > - gcc visibility : yes > - long double support : yes > - zlib : yes What am I missing, so that all those cxx_* features can be checked? -- Carlos Miguel Ferreira Researcher at Telecommunications Institute Aveiro - Portugal Work E-mail - cmf(a)av.it.pt Skype & GTalk -> carlosmf.pt(a)gmail.com LinkedIn -> http://www.linkedin.com/in/carlosmferreira

1 1

[regex] link error on upgrade to 1.62.0
by James Walker 05 Oct '16

05 Oct '16

Hi, I'm trying to update from 1.60.0 to 1.62.0 on Mac with Xcode 4.6.3, and I'm getting link errors on Regex. I am definitely compiling all 17 of the .cpp files in libs/regex/src. The errors are shown below. Any idea what I might be missing? Undefined symbols for architecture i386: "boost::re_detail_106200::perl_matcher<char const*, std::allocator<boost::sub_match<char const*> >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::construct_init(boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags)", referenced from: boost::re_detail_106200::perl_matcher<char const*, std::allocator<boost::sub_match<char const*> >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::perl_matcher(char const*, char const*, boost::match_results<char const*, std::allocator<boost::sub_match<char const*> > >&, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags, char const*) in BVHJointMap.o boost::re_detail_106200::perl_matcher<char const*, std::allocator<boost::sub_match<char const*> >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::perl_matcher(char const*, char const*, boost::match_results<char const*, std::allocator<boost::sub_match<char const*> > >&, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags, char const*) in AnimationsManager.o "boost::re_detail_106200::perl_matcher<char const*, std::allocator<boost::sub_match<char const*> >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::find()", referenced from: bool boost::regex_search<char const*, char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >(char const*, char const*, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags) in BVHJointMap.o "boost::re_detail_106200::perl_matcher<char const*, std::allocator<boost::sub_match<char const*> >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::match()", referenced from: bool boost::regex_match<char const*, std::allocator<boost::sub_match<char const*> >, char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >(char const*, char const*, boost::match_results<char const*, std::allocator<boost::sub_match<char const*> > >&, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags) in AnimationsManager.o ld: symbol(s) not found for architecture i386

1 1

boost::asio cross-library link issue
by Stanley Friesen 05 Oct '16

05 Oct '16

We are using Boost 1.54. The issue i have is a strange problem with the ASIO library. We have two libraries build using ASIO from Boost 1.54 (libpcl and one of our own libraries). For some reason, despite being built with the same version of boost, the layout of class task_io_service differs between the two libraries. The member function instantiations are in the libraries as weak symbols, so we do not get a link error, but which version of each function that is called from any given place is unpredictable, and varies when we change out own code. In particular, at least op_queue_ and all following members have offsets that differ by 8 bytes (the size of a 64-bit pointer) between the two builds. The result is that sometimes the op_queue back pointer is corrupted (by the other version setting stopped_), or the stop flag is not seen because it was set by the other build. The result is either that run() returns immediately without doing anything, or out application crashes from trying to dereference an invalid pointer. (Often what is supposed to be a NULL back pointer is set to 1, which does not compare equal to NULL). I have looked for conditionally compiled elements in task_io_service, op_queue, and epoll_reactor with no luck. I can see no reason the two library builds should end up with different class layouts. So, does anybody have any clue what might be happening here? Or how to go about fixing the problem? [I hesitate to try forcing strong symbols in our library, since this would break libpcl, due to many functions being inline]. -- View this message in context: http://boost.2283326.n4.nabble.com/boost-asio-cross-library-link-issue-tp46… Sent from the Boost - Users mailing list archive at Nabble.com.

5 8

Different checksums for different SourceForge locations
by Carlos Ferreira 05 Oct '16

05 Oct '16

I'm having some issues in downloading the Boost 1.62 package from the SF servers. It seems that the Eastern US servers checksum values are not matching the rest of the servers, nor the checksum values provided at the Boost.org website. Is there anyone else having the same problem? -- Carlos Miguel Ferreira Researcher at Telecommunications Institute Aveiro - Portugal Work E-mail - cmf(a)av.it.pt Skype & GTalk -> carlosmf.pt(a)gmail.com LinkedIn -> http://www.linkedin.com/in/carlosmferreira

2 8

Need help with errors while building boost for clang on android NDK
by Robert Dailey 04 Oct '16

04 Oct '16

I'm using NDK r11 and I'm setting up project-config.jam to build boost using clang + llvm STL. I'm running into a few errors that I do not know how to solve. I will post my config file at the bottom. First problem is that boost does not know where to find tools 'ar' and 'ranlib': clang-linux.archive bin.v2\libs\container\build\clang-linux-android\release\link-static\runtime-link-static\target-os-linux\threading-multi\libboost_container-clang-mt-s-1_61.a '"ar"' is not recognized as an internal or external command, operable program or batch file. '"ranlib"' is not recognized as an internal or external command, operable program or batch file. How can I explicitly specify the NDK path to these executables? Second problem is related to some assembler stuff, I think. I get these errors while compiling boost thread: clang-linux.compile.asm bin.v2\libs\context\build\clang-linux-android\release\link-static\runtime-link-static\target-os-linux\threading-multi\asm\make_i386_ms_pe_gas.o libs\\context\\src\\asm\\make_i386_ms_pe_gas.asm:30:1: error: unknown directive .def _make_fcontext; .scl 2; .type 32; .endef ^ libs\\context\\src\\asm\\make_i386_ms_pe_gas.asm:30:22: error: unknown directive .def _make_fcontext; .scl 2; .type 32; .endef ^ libs\\context\\src\\asm\\make_i386_ms_pe_gas.asm:30:36: error: expected identifier in directive .def _make_fcontext; .scl 2; .type 32; .endef ^ libs\\context\\src\\asm\\make_i386_ms_pe_gas.asm:30:40: error: unknown directive .def _make_fcontext; .scl 2; .type 32; .endef ^ libs\\context\\src\\asm\\make_i386_ms_pe_gas.asm:136:1: error: unknown directive .def __exit; .scl 2; .type 32; .endef ^ How can I solve this? I have no idea at this point. I'm invoking the build using: b2 --without-python threading=multi link=static runtime-link=static toolset=gcc-android target-os=linux threadapi=pthread --stagedir=android stage And my project-config.jam looks like: import option ; option.set keep-going : false ; androidNDKRoot = E:/android/ndk ; androidAbiVer = 4.9 ; androidPlatform = windows-x86_64 ; using clang : android : $(androidNDKRoot)/toolchains/llvm/prebuilt/$(androidPlatform)/bin/clang++ : <compileflags>--sysroot=$(androidNDKRoot)/platforms/android-15/arch-arm <compileflags>-Os <compileflags>-fno-strict-aliasing <compileflags>-O2 <compileflags>-DNDEBUG <compileflags>-g <compileflags>-I$(androidNDKRoot)/sources/cxx-stl/llvm-libc++abi/libcxxabi/include <compileflags>-I$(androidNDKRoot)/sources/cxx-stl/llvm-libc++/libcxx/include <compileflags>-I$(androidNDKRoot)/sources/cxx-stl/llvm-libc++/libs/armeabi-v7a <compileflags>-I$(androidNDKRoot)/sources/android/support/include <compileflags>-DANDROID <compileflags>-D__ANDROID__ <compileflags>-D__arm__ <compileflags>-D_REENTRANT ;

3 8

boost::lockfree::queue::reserve fail with fixed_sized = true
by Sam Sigbjørn 04 Oct '16

04 Oct '16

Hello, When i compile lockfree::queue with option fixed_sized set to true i get a compilation error in reserve: void reserve(size_type n) { pool.template reserve<true>(n); } Btw, MSC version is 190024210 (Update 3) and i defined _ENABLE_ATOMIC_ALIGNMENT_FIX Thanks

1 0

[release] Boost 1.62.0 release available
by Rene Rivera 04 Oct '16

04 Oct '16

Release 1.62.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 two new libraries and numerous enhancements and bug fixes for existing libraries. New Libraries * Fiber: Framework for userland-threads/fibers, from Oliver Kowalke. * QVM: Boost QVM is a generic library for working with quaternions, vectors and matrices of static size with the emphasis on 2, 3 and 4-dimensional operations needed in graphics, video games and simulation applications, from Emil Dotchevski. For details, including download links, see http://www.boost.org/users/ news/version_1.62.0 You can also download directly from SourceForge: http://sourceforge.net/ projects/boost/files/boost/1.62.0/ The SHA256 checksums are as follows: b91c2cda8bee73ea613130e19e72c9589e9ef0357c4c5cc5f7523de82cce11f7 boost_1_62_0.7z 36c96b0f6155c98404091d8ceb48319a28279ca0333fba1ad8611eb90afb2ca0 boost_1_62_0.tar.bz2 440a59f8bc4023dbe6285c9998b0f7fa288468b889746b1ef00e8b36c559dce1 boost_1_62_0.tar.gz 084b2e0638bbe0975a9e43e21bc9ceae33ef11377aecab3268a57cf41e405d4e boost_1_62_0.zip Tom Kent has made pre-built windows binaries, and they are available at: https://sourceforge.net/projects/boost/files/boost-binaries/1.62.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

3 5

boost 1.62 msvc compilation error : regression from 1.61 ?
by Julien Schueller 04 Oct '16

04 Oct '16

Hello, I'm trying to update from boost 1.61 to 1.62 on msvc for conda and encountered this error: [00:03:41] Performing configuration checks [00:03:41] [00:03:41] - 32-bit : yes ... [00:03:41] - x86 : yes [00:03:41] - symlinks supported : yes [00:03:41] - C++11 mutex : no [00:03:41] - Boost.Config Feature Check: cxx11_auto_declarations : no ... [00:03:42] - has_icu builds : no ... [00:03:43] - zlib : yes [00:03:43] error: at C:/conda/conda-bld/work/boost_1_62_0/tools/build/src/kernel\modules.jam:107 [00:03:43] error: Name clash for '<pbuildboost\boost\bin.v2\standalone\ac\msvc-9.0\release\link-static\threading-multi>main.obj' [00:03:43] error: [00:03:43] error: Tried to build the target twice, with property sets having [00:03:43] error: these incompatible properties: [00:03:43] error: [00:03:43] error: - <dll-path>C:\conda\envs\_build\Library\lib <library-path>C:\conda\envs\_build\Library\lib <xdll-path>C:\conda\envs\_build\Library\lib [00:03:43] error: - none [00:03:43] error: [00:03:43] error: Please make sure to have consistent requirements for these [00:03:43] error: properties everywhere in your project, especially for install [00:03:43] error: targets. [00:03:43] [00:03:43] Command failed: cmd.exe /c bld.bat [00:03:43] Command exited with code 1 Full logs are available here: https://ci.appveyor.com/project/conda-forge/boost-feedstock/build/1.0.36 I've got the same error for vc9, vc10 and vc14 for both 32 and 64bits. I configure with the exact same script I used for 1.61, here's the configure part: call bootstrap.bat .\b2 install ^ --build-dir=buildboost ^ --prefix=%LIBRARY_PREFIX% ^ toolset=msvc-%VSTRING%.0 ^ address-model=%ARCH% ^ variant=release ^ threading=multi ^ link=static,shared ^ -j%CPU_COUNT% ^ -s ZLIB_INCLUDE="%LIBRARY_INC%" ^ -s ZLIB_LIBPATH="%LIBRARY_LIB%" It can be seen there: https://github.com/conda-forge/boost-feedstock/blob/master/recipe/bld.bat I've not seen it reported in the trac tickets, did someone get the same error ? -- J Schueller

1 0

[Boost::asio] Problem using the same io_service with many sockets
by María Victoria Rocha 03 Oct '16

03 Oct '16

Hi all, I have defined an io_service that is used by two sockets, one of them uses tcp, and the other udp. When the callback of this async_read_some is called socket.async_read_some(boost::asio::buffer(readBuffer), boost::bind(&RequestHandler::onRead, shared_from_this(), boost::asio::placeholders::error, boost::asio::placeholders::bytes_transferred)); A udp socket is created with the same io_service and an async_receive_from is called. On the callback of this read operation I try to write to the tcp socket but it captures an exception with message: "unknown exception". When this happens, the client that is listening to the tcp socket, receives "End of file" error. I resolved this problem with an io_service per socket but I would like to use the same io_service. Someone has any idea why this happens? Thanks! Victoria

2 1

[Thread] Thread library in boost 1.62 broken with g++ 4.6.3 and -std=c++0x
by Andreas Wehrmann 03 Oct '16

03 Oct '16

Hello folks, I've just wanted to try out the new release and noticed that the Thread library was not building. Assuming this code: #include <boost/thread.hpp> int main( void ) { return 0; } When compiled with -std=c++0x the compilation fails with: In file included from ./boost/boost_1_62_0/boost/exception/detail/exception_ptr.hpp:20:0, from ./boost/boost_1_62_0/boost/exception_ptr.hpp:9, from ./boost/boost_1_62_0/boost/thread/exceptional_ptr.hpp:10, from ./boost/boost_1_62_0/boost/thread/future.hpp:25, from ./boost/boost_1_62_0/boost/thread.hpp:24, from test.cpp:2: ./boost/boost_1_62_0/boost/exception/info.hpp: In instantiation of ‘boost::error_info<boost::tag_original_exception_type, const std::type_info*>’: ./boost/boost_1_62_0/boost/exception/detail/exception_ptr.hpp:95:32: instantiated from here ./boost/boost_1_62_0/boost/exception/info.hpp:66:5: error: ‘class boost::error_info<boost::tag_original_exception_type, const std::type_info*>’ has no member named ‘value_’ ./boost/boost_1_62_0/boost/container/detail/pair.hpp:85:30: warning: ‘boost::container::piecewise_construct’ defined but not used [-Wunused-variable] ./boost/boost_1_62_0/boost/system/error_code.hpp:221:36: warning: ‘boost::system::posix_category’ defined but not used [-Wunused-variable] ./boost/boost_1_62_0/boost/system/error_code.hpp:222:36: warning: ‘boost::system::errno_ecat’ defined but not used [-Wunused-variable] ./boost/boost_1_62_0/boost/system/error_code.hpp:223:36: warning: ‘boost::system::native_ecat’ defined but not used [-Wunused-variable] Compilation works if I don't use -std=c++0x. The exact compiler version is "g++ (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3". I'm aware that g++ 4.6.3 is not among the compilers tested for C++11, but it is for pre-Cpp11; I'm wondering if there is a reason for that which I might not be aware of (any known problems?). Best regards, Andreas

3 2

thread no defined - issue
by Alexander Carôt 29 Sep '16

29 Sep '16

Hi all, one single (windows) user in my project community (http://www.soundjack.eu) has the following problem: #ifndef BOOST_THREAD_DEFINES_THREAD_ATTRIBUTES_NATIVE_HANDLE cout << "THREAD IS NOT DEFINED" << endl; #endif This statement is true but only for him – on any other machine (Win, Linux and OSX) is works fine. Does anybody know what he can do in order to fix this issue ? Thanks in advance, best Alex

4 8

help with boost::variant, accessing recursive types
by Littlefield, Tyler 29 Sep '16

29 Sep '16

all, I have the following: boost::make_recursive_variant<int, bool, std::string, std::map<std::string, boost::recursive_variant_>>::type node; I'm populating this tree. I'm using libucl because it has a relaxed JSON syntax but I wanted to have a tree-like configuration here. The std::map is a key:value pair obviously. So my questions: How do I get std::maps from this variant? I know boost::get exists, will it just return a pointer to std::map? does setting elements in the map set elements on the variant? I also didn't see any return info for what boost::get returns if the element does not exist. Will it just return null since it does return a T*? Finally, is there a way to see the type of the variant? I don't really care if it's a bool or string, although I would like to place some implicit checks on certain values when they're retrieved. PS: If there's a way to pull this off with boost::property_tree, I would love to know how. I'm looking at using libucl as mentioned before because it provides a nginx-like not really JSON-style configuration syntax. Any tips would be appreciated. HOpefully these questions are clear and make sense. -- Take care, Ty Twitter: @sorressean Web: https://tysdomain.com Pubkey: https://tysdomain.com/files/pubkey.asc

2 1

Unable to build boost 1.61 on Solaris 11.3 w/ DevStudio 12.5
by Jon Earle 29 Sep '16

29 Sep '16

Please bear with me as I am not really familiar with Solaris. I have an 11.3 box, where I installed the developer studio 12.5. Following directions at https://blogs.oracle.com/studiocpp/entry/test, I tried to build boost 1.61. It fails horribly! I get as far as: >> create compiler configuration for Studio 12.4 C++03 (using Boost.Config configure) so all the fancy C++11 stuff in Boost is not yet enabled even if we compile with -std=c++11. ] cd libs/config; CXX=CC CXXFLAGS="-std=c++03 -m64" LDFLAGS="-std=c++03 -m64" sh ./configure << which fails. Config.log contains: configure:1959: CC -std=c++03 -m64 -std=c++03 -m64 conftest.cpp >&5 CC: Warning: Option -std=c++03 passed to ld, if ld is invoked, ignored otherwise CC: Warning: Option -std=c++03 passed to ld, if ld is invoked, ignored otherwise ld: fatal: option '-d' has illegal argument '=c++03' ld: fatal: option '-d' has illegal argument '=c++03' Removing "-std=c++03" does allow the configure process to run but not as it was intended. Building with: "./b2 --user-config=user-config.jam address-model=64 -j12 --disable-icu" gives me a lot of errors, such as those below. Below my problem description, I've pasted the build errors I noticed until I broke the build. What is the proper sequence to build boost 1.61 on Solaris? Many thanks for any help! Build output (excerpts): root@solaris:~/jearle/crypto/3rdpartySW/boost-build/boost_1_61_0# ./b2 --user-config=user-config.jam address-model=64 -j12 --disable-icu Performing configuration checks - 32-bit : yes (cached) - arm : no (cached) - mips1 : no (cached) - power : no (cached) - sparc : no (cached) - x86 : yes (cached) Building the Boost C++ Libraries. - symlinks supported : yes (cached) error: No best alternative for libs/context/build/asm/make_x86_64_sysv_elf_gas.o next alternative: required properties: <threading>multi matched next alternative: required properties: <threading>multi matched error: No best alternative for libs/context/build/asm/jump_x86_64_sysv_elf_gas.o next alternative: required properties: <threading>multi matched next alternative: required properties: <threading>multi matched error: No best alternative for libs/context/build/asm/ontop_x86_64_sysv_elf_gas.o next alternative: required properties: <threading>multi matched next alternative: required properties: <threading>multi matched - C++11 mutex : no (cached) - lockfree boost::atomic_flag : no (cached) warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - zlib : no (cached) - icu : no (cached) - icu (lib64) : no (cached) - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - compiler-supports-visibility : no (cached) - compiler-supports-ssse3 : yes (cached) - has_icu builds : no (cached) - compiler-supports-avx2 : no (cached) - gcc visibility : no (cached) - long double support : yes (cached) warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. error: No best alternative for libs/context/build/asm/make_x86_64_sysv_elf_gas.o next alternative: required properties: <threading>multi matched next alternative: required properties: <threading>multi matched error: No best alternative for libs/context/build/asm/jump_x86_64_sysv_elf_gas.o next alternative: required properties: <threading>multi matched next alternative: required properties: <threading>multi matched error: No best alternative for libs/context/build/asm/ontop_x86_64_sysv_elf_gas.o next alternative: required properties: <threading>multi matched next alternative: required properties: <threading>multi matched - zlib : no (cached) - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. ... ...patience... ...found 9011 targets... ...updating 845 targets... sun.compile.c++ bin.v2/libs/wave/build/sun/release/address-model-64/link-static/threading-multi/instantiate_re2c_lexer.o CC: Warning: Option -std=c++11 passed to ld, if ld is invoked, ignored otherwise "./boost/detail/iterator.hpp", line 19: Error: iterator_traits is not a member of std. "./boost/wave/util/flex_string.hpp", line 128: Error: Templates can only declare classes or functions. "./boost/wave/util/flex_string.hpp", line 131: Warning: Implicit int is not supported in C++. "./boost/wave/util/flex_string.hpp", line 131: Error: "," expected instead of "!=". "./boost/wave/util/flex_string.hpp", line 131: Error: A declaration was expected instead of "--". "./boost/wave/util/flex_string.hpp", line 131: Warning: Implicit int is not supported in C++. "./boost/wave/util/flex_string.hpp", line 131: Error: Multiple declaration for n. "./boost/wave/util/flex_string.hpp", line 131: Error: Use ";" to terminate declarations. "./boost/wave/util/flex_string.hpp", line 131: Error: A declaration was expected instead of "++". "./boost/wave/util/flex_string.hpp", line 131: Warning: Implicit int is not supported in C++. "./boost/wave/util/flex_string.hpp", line 131: Error: Use ";" to terminate declarations. "./boost/wave/util/flex_string.hpp", line 131: Error: A declaration was expected instead of "++". "./boost/wave/util/flex_string.hpp", line 131: Warning: Implicit int is not supported in C++. "./boost/wave/util/flex_string.hpp", line 131: Error: "," expected instead of ")". "./boost/wave/util/flex_string.hpp", line 135: Error: A declaration was expected instead of "return". "./boost/wave/util/flex_string.hpp", line 135: Warning: Implicit int is not supported in C++. "./boost/wave/util/flex_string.hpp", line 2538: Error: A declaration was expected instead of "}". "./boost/wave/util/flex_string.hpp", line 2539: Error: A declaration was expected instead of "}". "./boost/wave/token_ids.hpp", line 359: Error: flex_string is not a member of boost::wave::util. "./boost/wave/token_ids.hpp", line 359: Error: A declaration does not specify a tag or an identifier. "./boost/wave/token_ids.hpp", line 359: Error: Use ";" to terminate declarations. "./boost/wave/token_ids.hpp", line 359: Error: A declaration was expected instead of "<". "./boost/wave/token_ids.hpp", line 359: Error: A declaration does not specify a tag or an identifier. "./boost/wave/token_ids.hpp", line 359: Error: Use ";" to terminate declarations. "./boost/wave/token_ids.hpp", line 359: Error: A declaration was expected instead of ",". "./boost/wave/token_ids.hpp", line 359: Warning: declarator required in declaration. "./boost/wave/token_ids.hpp", line 359: Error: Use ";" to terminate declarations. "./boost/wave/token_ids.hpp", line 359: Error: A declaration was expected instead of ",". "./boost/wave/token_ids.hpp", line 359: Warning: declarator required in declaration. "./boost/wave/token_ids.hpp", line 359: Error: Use ";" to terminate declarations. "./boost/wave/token_ids.hpp", line 359: Error: A declaration was expected instead of ",". "./boost/wave/token_ids.hpp", line 359: Error: CowString is not a member of boost::wave::util. Compilation aborted, too many Error messages. ... "CC" -xO4 -mt -erroff=%none -std=c++11 -m64 -DBOOST_ALL_NO_LIB=1 -DBOOST_THREAD_USE_LIB=1 -DNDEBUG -I"." -c -o "bin.v2/libs/wave/build/sun/release/address-model-64/link-static/threading-multi/instantiate_re2c_lexer_str.o" "libs/wave/src/instantiate_re2c_lexer_str.cpp" ...failed sun.compile.c++ bin.v2/libs/wave/build/sun/release/address-model-64/link-static/threading-multi/instantiate_re2c_lexer_str.o... sun.compile.c++ bin.v2/libs/wave/build/sun/release/address-model-64/link-static/threading-multi/wave_config_constant.o CC: Warning: Option -std=c++11 passed to ld, if ld is invoked, ignored otherwise "./boost/detail/iterator.hpp", line 19: Error: iterator_traits is not a member of std. "./boost/wave/util/flex_string.hpp", line 128: Error: Templates can only declare classes or functions. "./boost/wave/util/flex_string.hpp", line 131: Warning: Implicit int is not supported in C++. "./boost/wave/util/flex_string.hpp", line 131: Error: "," expected instead of "!=". "./boost/wave/util/flex_string.hpp", line 131: Error: A declaration was expected instead of "--". "./boost/wave/util/flex_string.hpp", line 131: Warning: Implicit int is not supported in C++. "./boost/wave/util/flex_string.hpp", line 131: Error: Multiple declaration for n. "./boost/wave/util/flex_string.hpp", line 131: Error: Use ";" to terminate declarations. "./boost/wave/util/flex_string.hpp", line 131: Error: A declaration was expected instead of "++". "./boost/wave/util/flex_string.hpp", line 131: Warning: Implicit int is not supported in C++. "./boost/wave/util/flex_string.hpp", line 131: Error: Use ";" to terminate declarations. "./boost/wave/util/flex_string.hpp", line 131: Error: A declaration was expected instead of "++". "./boost/wave/util/flex_string.hpp", line 131: Warning: Implicit int is not supported in C++. "./boost/wave/util/flex_string.hpp", line 131: Error: "," expected instead of ")". "./boost/wave/util/flex_string.hpp", line 135: Error: A declaration was expected instead of "return". "./boost/wave/util/flex_string.hpp", line 135: Warning: Implicit int is not supported in C++. "./boost/wave/util/flex_string.hpp", line 2538: Error: A declaration was expected instead of "}". "./boost/wave/util/flex_string.hpp", line 2539: Error: A declaration was expected instead of "}". 13 Error(s) and 5 Warning(s) detected. ... "CC" -xO4 -mt -erroff=%none -std=c++11 -m64 -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -I"." -c -o "bin.v2/libs/filesystem/build/sun/release/address-model-64/link-static/threading-multi/portability.o" "libs/filesystem/src/portability.cpp" ...failed sun.compile.c++ bin.v2/libs/filesystem/build/sun/release/address-model-64/link-static/threading-multi/portability.o... sun.compile.c++ bin.v2/libs/filesystem/build/sun/release/address-model-64/link-static/threading-multi/utf8_codecvt_facet.o CC: Warning: Option -std=c++11 passed to ld, if ld is invoked, ignored otherwise sun.compile.c++ bin.v2/libs/filesystem/build/sun/release/address-model-64/link-static/threading-multi/path.o CC: Warning: Option -std=c++11 passed to ld, if ld is invoked, ignored otherwise "./boost/detail/iterator.hpp", line 19: Error: iterator_traits is not a member of std. 1 Error(s) detected. ... "CC" -xO4 -mt -erroff=%none -std=c++11 -m64 -DBOOST_ALL_NO_LIB=1 -DBOOST_IOSTREAMS_USE_DEPRECATED -DNDEBUG -I"." -c -o "bin.v2/libs/iostreams/build/sun/release/address-model-64/link-static/threading-multi/bzip2.o" "libs/iostreams/src/bzip2.cpp" ...failed sun.compile.c++ bin.v2/libs/iostreams/build/sun/release/address-model-64/link-static/threading-multi/bzip2.o... ...skipped <pbin.v2/libs/iostreams/build/sun/release/address-model-64/link-static/threading-multi>libboost_iostreams.a for lack of <pbin.v2/libs/iostreams/build/sun/release/address-model-64/link-static/threading-multi>mapped_file.o... ...skipped <pstage/lib>libboost_iostreams.a for lack of <pbin.v2/libs/iostreams/build/sun/release/address-model-64/link-static/threading-multi>libboost_iostreams.a... sun.compile.c++ bin.v2/libs/log/build/sun/release/address-model-64/build-no/link-static/log-api-unix/threading-multi/named_scope.o CC: Warning: Option -std=c++11 passed to ld, if ld is invoked, ignored otherwise "./boost/log/utility/string_literal.hpp", line 76: Error: Too few arguments for template std::reverse_iterator<std::_Iterator, std::_Category, std::_Tt, std::_Reference, std::_Pointer, std::_Distance>. "./boost/log/attributes/named_scope.hpp", line 82: Where: While specializing "boost::log::v2s_mt_posix::basic_string_literal<char, std::char_traits<char>>". "./boost/log/attributes/named_scope.hpp", line 82: Where: Specialized in non-template code. "./boost/log/attributes/named_scope.hpp", line 219: Error: Too few arguments for template std::reverse_iterator<std::_Iterator, std::_Category, std::_Tt, std::_Reference, std::_Pointer, std::_Distance>. "./boost/log/attributes/named_scope.hpp", line 220: Error: Too few arguments for template std::reverse_iterator<std::_Iterator, std::_Category, std::_Tt, std::_Reference, std::_Pointer, std::_Distance>. "./boost/log/attributes/named_scope.hpp", line 295: Error: Cannot cast from boost::log::v2s_mt_posix::attributes::named_scope_list::iter<1> to int. "./boost/log/attributes/named_scope.hpp", line 299: Error: Cannot cast from boost::log::v2s_mt_posix::attributes::named_scope_list::iter<1> to int. "./boost/log/attributes/named_scope.hpp", line 318: Error: The operation "* int" is illegal. "libs/log/src/named_scope.cpp", line 213: Error: Cannot use void* to initialize boost::log::v2s_mt_posix::attributes::named_scope_entry*. "libs/log/src/named_scope.cpp", line 217: Error: construct is not a member of std::allocator<boost::log::v2s_mt_posix::attributes::named_scope_entry>. "libs/log/src/named_scope.cpp", line 235: Error: destroy is not a member of std::allocator<boost::log::v2s_mt_posix::attributes::named_scope_entry>. 9 Error(s) detected. ... "CC" -xO4 -mt -erroff=%none -std=c++11 -m64 -DBOOST_ALL_NO_LIB=1 -DBOOST_DATE_TIME_STATIC_LINK -DDATE_TIME_INLINE -DNDEBUG -I"." -c -o "bin.v2/libs/date_time/build/sun/release/address-model-64/link-static/threading-multi/gregorian/greg_month.o" "libs/date_time/src/gregorian/greg_month.cpp" ...failed sun.compile.c++ bin.v2/libs/date_time/build/sun/release/address-model-64/link-static/threading-multi/gregorian/greg_month.o... ...skipped <pbin.v2/libs/date_time/build/sun/release/address-model-64/link-static/threading-multi>libboost_date_time.a for lack of <pbin.v2/libs/date_time/build/sun/release/address-model-64/link-static/threading-multi>gregorian/greg_month.o... ...skipped <pstage/lib>libboost_date_time.a for lack of <pbin.v2/libs/date_time/build/sun/release/address-model-64/link-static/threading-multi>libboost_date_time.a... sun.compile.c++ bin.v2/libs/log/build/sun/release/address-model-64/build-no/link-static/log-api-unix/threading-multi/thread_id.o CC: Warning: Option -std=c++11 passed to ld, if ld is invoked, ignored otherwise "libs/log/src/thread_id.cpp", line 213: Warning (Anachronism): Formal argument 2 of type extern "C" void(*)(void*) in call to pthread_key_create(unsigned*, extern "C" void(*)(void*)) is being passed void(*)(void*). 1 Warning(s) detected. sun.compile.c++ bin.v2/libs/log/build/sun/release/address-model-64/build-no/link-static/log-api-unix/threading-multi/severity_level.o CC: Warning: Option -std=c++11 passed to ld, if ld is invoked, ignored otherwise "./boost/move/unique_ptr.hpp", line 434: Error: typenamebmupd is not defined. "libs/log/src/severity_level.cpp", line 66: Where: While instantiating "boost::movelib::unique_ptr<unsigned long, boost::movelib::default_delete<unsigned long>>::unique_ptr<unsigned long*>(unsigned long*, boost::move_upmu::nat*)". "libs/log/src/severity_level.cpp", line 66: Where: Instantiated from non-template code. "./boost/move/unique_ptr.hpp", line 434: Error: get_element_type is not defined. "libs/log/src/severity_level.cpp", line 66: Where: While instantiating "boost::movelib::unique_ptr<unsigned long, boost::movelib::default_delete<unsigned long>>::unique_ptr<unsigned long*>(unsigned long*, boost::move_upmu::nat*)". "libs/log/src/severity_level.cpp", line 66: Where: Instantiated from non-template code. "./boost/move/unique_ptr.hpp", line 434: Error: "," expected instead of "<". "libs/log/src/severity_level.cpp", line 66: Where: While instantiating "boost::movelib::unique_ptr<unsigned long, boost::movelib::default_delete<unsigned long>>::unique_ptr<unsigned long*>(unsigned long*, boost::move_upmu::nat*)". "libs/log/src/severity_level.cpp", line 66: Where: Instantiated from non-template code. "./boost/move/unique_ptr.hpp", line 434: Error: Illegal value for template parameter. "libs/log/src/severity_level.cpp", line 66: Where: While instantiating "boost::movelib::unique_ptr<unsigned long, boost::movelib::default_delete<unsigned long>>::unique_ptr<unsigned long*>(unsigned long*, boost::move_upmu::nat*)". "libs/log/src/severity_level.cpp", line 66: Where: Instantiated from non-template code. "./boost/move/unique_ptr.hpp", line 434: Error: Template template-parameter boost::move_upmu::U requires a class template argument. "libs/log/src/severity_level.cpp", line 66: Where: While instantiating "boost::movelib::unique_ptr<unsigned long, boost::movelib::default_delete<unsigned long>>::unique_ptr<unsigned long*>(unsigned long*, boost::move_upmu::nat*)". "libs/log/src/severity_level.cpp", line 66: Where: Instantiated from non-template code. "./boost/move/unique_ptr.hpp", line 434: Error: type is not a member of boost::move_upmu::missing_virtual_destructor<boost::movelib::default_delete<unsigned long>, int>. "libs/log/src/severity_level.cpp", line 66: Where: While instantiating "boost::movelib::unique_ptr<unsigned long, boost::movelib::default_delete<unsigned long>>::unique_ptr<unsigned long*>(unsigned long*, boost::move_upmu::nat*)". "libs/log/src/severity_level.cpp", line 66: Where: Instantiated from non-template code. "./boost/move/unique_ptr.hpp", line 434: Error: value is not defined. "libs/log/src/severity_level.cpp", line 66: Where: While instantiating "boost::movelib::unique_ptr<unsigned long, boost::movelib::default_delete<unsigned long>>::unique_ptr<unsigned long*>(unsigned long*, boost::move_upmu::nat*)". "libs/log/src/severity_level.cpp", line 66: Where: Instantiated from non-template code. 7 Error(s) detected. ... ...failed sun.compile.c++ bin.v2/libs/log/build/sun/release/address-model-64/build-no/link-static/log-api-unix/threading-multi/syslog_backend.o... sun.compile.c++ bin.v2/libs/log/build/sun/release/address-model-64/link-static/log-api-unix/threading-multi/dump_ssse3.o CC: Warning: Option -std=c++11 passed to ld, if ld is invoked, ignored otherwise "libs/log/src/dump_ssse3.cpp", line 179: ube: error: _mm_lddqu_si128 intrinsic requires at least -xarch=sse3. CC: ube failed for libs/log/src/dump_ssse3.cpp "CC" -xO4 -mt -erroff=%none -std=c++11 -m64 -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_STATIC_LINK=1 -DBOOST_CHRONO_STATIC_LINK=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DBOOST_LOG_BUILDING_THE_LIB=1 -DBOOST_LOG_USE_NATIVE_SYSLOG -DBOOST_LOG_WITHOUT_EVENT_LOG -DBOOST_SPIRIT_USE_PHOENIX_V3=1 -DBOOST_SYSTEM_NO_DEPRECATED -DBOOST_SYSTEM_STATIC_LINK=1 -DBOOST_THREAD_BUILD_LIB=1 -DBOOST_THREAD_DONT_USE_CHRONO=1 -DBOOST_THREAD_POSIX -DBOOST_THREAD_USE_LIB=1 -DDATE_TIME_INLINE -DNDEBUG -D_XOPEN_SOURCE=500 -D__EXTENSIONS__ -D__STDC_CONSTANT_MACROS -D__typeof__=__typeof__ -I"." -c -o "bin.v2/libs/log/build/sun/release/address-model-64/link-static/log-api-unix/threading-multi/dump_ssse3.o" "libs/log/src/dump_ssse3.cpp"

2 1

Insertion/Use of boost::multi_index - new thread
by Ram 29 Sep '16

29 Sep '16

Hi, When I try to create a object of this, typedef boost::multi_index_container< ClassX*, //mapped value boost::multi_index::indexed_by< //list of indices boost::multi_index::hashed_unique< boost::multi_index::const_mem_fun<ParentClassOfX, Key1, &ParentClassOfX::getKey1> //hashed index by unique Key1 >, boost::multi_index::hashed_unique< boost::multi_index::const_mem_fun<ParentClassOfX, Vs64, &ParentClassOfX::getKey2> //hashed index by unique Key1 > > >ClassXMultiKeyIndexed; like, ClassXMultiKeyIndexed sample; and insert a pointer like this, ClassX *a; ClassXMultiKeyIndexed sample; //a is not NULL and is filled up before the below insert sample.insert(a); This is the compilation error, it compiles fine if "sample.insert(a)" is commented out. Compilation error : Compiling... stm_container_manager_abc.cpp c:\code\common\lib\boost\boost\detail\allocator_utilities.hpp(153) : error C2061: syntax error : identifier 'p' c:\code\common\lib\boost\boost\multi_index\detail\index_base.hpp(105) : see reference to function template instantiation 'void boost::detail::allocator::construct<Container*>(void *,const Type &)' being compiled with [ Type=Container * ] c:\code\common\lib\boost\boost\multi_index\detail\index_base.hpp(102) : while compiling class template member function 'boost::multi_index::detail::hashed_index_node<Super,Category> *boost::multi_index::detail::index_base<Value,IndexSpecifierList,Allocator>::insert_(Container *const &,boost::multi_index::detail::hashed_index_node<Super,Category> *&,boost::multi_index::detail::lvalue_tag)' with [ Super=boost::multi_index::detail::hashed_index_node<boost::multi_index::detail::index_node_base<Container *,std::allocator<Container *>>,boost::multi_index::detail::hashed_unique_tag>, Category=boost::multi_index::detail::hashed_unique_tag, Value=Container *, IndexSpecifierList=boost::multi_index::indexed_by<boost::multi_index::hashed_unique<boost::multi_index::const_mem_fun<DBObject,Key1,DBObject::getKey1>>,boost::multi_index::hashed_unique<boost::multi_index::const_mem_fun<DBObject,Vs64,DBObject::getKey2>>>, Allocator=std::allocator<Container *> ] c:\code\common\lib\boost\boost\multi_index\hashed_index.hpp(93) : see reference to class template instantiation 'boost::multi_index::detail::index_base<Value,IndexSpecifierList,Allocator>' being compiled with [ Value=Container *, IndexSpecifierList=boost::multi_index::indexed_by<boost::multi_index::hashed_unique<boost::multi_index::const_mem_fun<DBObject,Key1,DBObject::getKey1>>,boost::multi_index::hashed_unique<boost::multi_index::const_mem_fun<DBObject,Vs64,DBObject::getKey2>>>, Allocator=std::allocator<Container *> ] c:\code\common\lib\boost\boost\multi_index\hashed_index.hpp(93) : see reference to class template instantiation 'boost::multi_index::detail::hashed_index<KeyFromValue,Hash,Pred,SuperMeta,TagList,Category>' being compiled with [ KeyFromValue=boost::multi_index::const_mem_fun<DBObject,Vs64,DBObject::getKey2>, Hash=boost::hash<boost::long_long_type>, Pred=std::equal_to<__int64>, SuperMeta=boost::multi_index::detail::nth_layer<2,Container *,boost::multi_index::indexed_by<boost::multi_index::hashed_unique<boost::multi_index::const_mem_fun<DBObject,Key1,DBObject::getKey1>>,boost::multi_index::hashed_unique<boost::multi_index::const_mem_fun<DBObject,Vs64,DBObject::getKey2>>>,std::allocator<Container *>>, TagList=boost::mpl::vector0<boost::mpl::na>, Category=boost::multi_index::detail::hashed_unique_tag ] c:\code\common\lib\boost\boost\multi_index_container.hpp(100) : see reference to class template instantiation 'boost::multi_index::detail::hashed_index<KeyFromValue,Hash,Pred,SuperMeta,TagList,Category>' being compiled with [ KeyFromValue=boost::multi_index::const_mem_fun<DBObject,Key1,DBObject::getKey1>, Hash=boost::hash<boost::long_long_type>, Pred=std::equal_to<__int64>, SuperMeta=boost::multi_index::detail::nth_layer<1,Container *,boost::multi_index::indexed_by<boost::multi_index::hashed_unique<boost::multi_index::const_mem_fun<DBObject,Key1,DBObject::getKey1>>,boost::multi_index::hashed_unique<boost::multi_index::const_mem_fun<DBObject,Vs64,DBObject::getKey2>>>,std::allocator<Container *>>, TagList=boost::mpl::vector0<boost::mpl::na>, Category=boost::multi_index::detail::hashed_unique_tag ] c:\code\common\src\biz\model\stm-stow_model\stm_container_manager_abc.h(323) : see reference to class template instantiation 'boost::multi_index::multi_index_container<Value,IndexSpecifierList>' being compiled with [ Value=Container *, IndexSpecifierList=boost::multi_index::indexed_by<boost::multi_index::hashed_unique<boost::multi_index::const_mem_fun<DBObject,Key1,DBObject::getKey1>>,boost::multi_index::hashed_unique<boost::multi_index::const_mem_fun<DBObject,Vs64,DBObject::getKey2>>> ] Build log was saved at "file://c:\code\win\Debug\obj\BuildLog.htm" ProjABC - 1 error(s), 0 warning(s) ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

4 26

local_time.hpp gives ... boost errors
by MAURICE Jean 29 Sep '16

29 Sep '16

Hi, I could narrow the place where boost errors appears. Using VS2010 (with 'show includes') on a Win7 machine. Boost is installed in C:\utilitaires\boost\boost15\boost_1_50_0\boost and this directory name has been replaced by - underneath (so it's version 1.50 !) When I write #pragma message (" avant boost/date_time/local_time/local_time.hpp") #include "boost/date_time/local_time/local_time.hpp" I get all these error messages : avant boost/date_time/local_time/local_time.hpp --/mpl/list/aux_/preprocessed/plain/list20.hpp(157): error C2143: syntax error : missing ',' before 'string' --/mpl/list/aux_/preprocessed/plain/list20.hpp(163): error C2974: 'boost::mpl::list19' : invalid template argument for 'T18', type expected --/mpl/list/aux_/preprocessed/plain/list20.hpp(144) : see declaration of 'boost::mpl::list19' --/mpl/list/aux_/preprocessed/plain/list20.hpp(167) : see reference to class template instantiation 'boost::mpl::list20<T0,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,__formal>' being compiled --/mpl/list/aux_/preprocessed/plain/list20.hpp(164): error C3203: 'list19' : unspecialized class template can't be used as a template argument for template parameter 'Next', expected a real type --/mpl/list/aux_/preprocessed/plain/list20.hpp(164): error C2955: 'boost::mpl::list19' : use of class template requires template argument list --/mpl/list/aux_/preprocessed/plain/list20.hpp(144) : see declaration of 'boost::mpl::list19' --/mpl/list/aux_/preprocessed/plain/list20.hpp(165): error C2955: 'boost::mpl::l_item' : use of class template requires template argument list --/mpl/list/aux_/item.hpp(30) : see declaration of 'boost::mpl::l_item' --/mpl/aux_/preprocessed/plain/list.hpp(20): error C2143: syntax error : missing ',' before 'string' --/mpl/aux_/preprocessed/plain/list.hpp(14): error C3747: missing default template parameter : parameter 20 --/mpl/aux_/preprocessed/plain/list.hpp(31): error C2975: 'boost::mpl::list' : invalid template argument for 'unnamed-parameter', expected compile-time constant expression --/mpl/aux_/preprocessed/plain/list.hpp(22) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(34): error C2913: explicit specialization; 'boost::mpl::list' is not a specialization of a class template --/mpl/aux_/preprocessed/plain/list.hpp(46): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(43) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(58): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(55) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(70): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(67) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(82): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(79) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(94): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(91) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(107): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(104) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(120): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(117) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(133): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(130) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(146): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(143) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(159): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(156) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(173): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(170) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(187): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(184) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(201): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(198) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(215): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(212) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(231): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(226) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(249): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(243) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(267): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(261) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(285): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(279) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(303): error C2976: 'boost::mpl::list' : too few template arguments --/mpl/aux_/preprocessed/plain/list.hpp(297) : see declaration of 'boost::mpl::list' --/mpl/aux_/preprocessed/plain/list.hpp(311): error C2143: syntax error : missing ',' before 'string' --/mpl/vector/aux_/preprocessed/plain/vector20.hpp(1020): error C2143: syntax error : missing ',' before 'string' --/mpl/vector/aux_/preprocessed/plain/vector20.hpp(1045): error C2059: syntax error : 'string' --/mpl/vector/aux_/preprocessed/plain/vector20.hpp(1052) : see reference to class template instantiation 'boost::mpl::vector20<T0,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,__formal>' being compiled --/mpl/vector/aux_/preprocessed/plain/vector20.hpp(1045): error C2238: unexpected token(s) preceding ';' --/mpl/vector/aux_/preprocessed/plain/vector20.hpp(1049): error C2059: syntax error : 'string' --/mpl/vector/aux_/preprocessed/plain/vector20.hpp(1049): error C2238: unexpected token(s) preceding ';' --/mpl/vector/aux_/preprocessed/plain/vector20.hpp(1072): error C2975: 'boost::mpl::vector20' : invalid template argument for 'unnamed-parameter', expected compile-time constant expression --/mpl/vector/aux_/preprocessed/plain/vector20.hpp(1023) : see declaration of 'boost::mpl::vector20' --/mpl/vector/aux_/preprocessed/plain/vector20.hpp(1073) : see reference to class template instantiation 'boost::mpl::push_front_impl<boost::mpl::aux::vector_tag<N>>::apply<Vector,T>' being compiled with [ N=19 ] --/mpl/vector/aux_/preprocessed/plain/vector20.hpp(1114): error C2975: 'boost::mpl::vector20' : invalid template argument for 'unnamed-parameter', expected compile-time constant expression --/mpl/vector/aux_/preprocessed/plain/vector20.hpp(1023) : see declaration of 'boost::mpl::vector20' --/mpl/vector/aux_/preprocessed/plain/vector20.hpp(1115) : see reference to class template instantiation 'boost::mpl::push_back_impl<boost::mpl::aux::vector_tag<N>>::apply<Vector,T>' being compiled with [ N=19 ] --/mpl/aux_/preprocessed/plain/vector.hpp(20): error C2143: syntax error : missing ',' before 'string' --/mpl/aux_/preprocessed/plain/vector.hpp(14): error C3747: missing default template parameter : parameter 20 --/mpl/aux_/preprocessed/plain/vector.hpp(31): error C2975: 'boost::mpl::vector' : invalid template argument for 'unnamed-parameter', expected compile-time constant expression --/mpl/aux_/preprocessed/plain/vector.hpp(22) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(34): error C2913: explicit specialization; 'boost::mpl::vector' is not a specialization of a class template --/mpl/aux_/preprocessed/plain/vector.hpp(46): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(43) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(58): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(55) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(70): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(67) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(82): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(79) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(94): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(91) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(107): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(104) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(120): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(117) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(133): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(130) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(146): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(143) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(159): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(156) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(173): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(170) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(187): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(184) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(201): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(198) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(215): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(212) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(231): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(226) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(249): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(243) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(267): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(261) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(285): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(279) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(303): error C2976: 'boost::mpl::vector' : too few template arguments --/mpl/aux_/preprocessed/plain/vector.hpp(297) : see declaration of 'boost::mpl::vector' --/mpl/aux_/preprocessed/plain/vector.hpp(311): error C2143: syntax error : missing ',' before 'string' --/math/policies/policy.hpp(406): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(440) : see reference to class template instantiation 'boost::math::policies::policy<A1,A2,A3,A4,A5,A6,A7,A8,A9,A10,A11,A12,A13>' being compiled --/math/policies/policy.hpp(406): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(407): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(407): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(408): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(408): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(409): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(409): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(410): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(410): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(411): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(411): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(412): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(412): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(413): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(413): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(418): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(418): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(419): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(419): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(425): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(425): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(426): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(426): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(430): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(430): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(434): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(434): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(438): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(438): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(439): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(439): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(514): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(588) : see reference to class template instantiation 'boost::math::policies::normalise<Policy,A1,A2,A3,A4,A5,A6,A7,A8,A9,A10,A11,A12,A13>' being compiled --/math/policies/policy.hpp(514): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(515): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(515): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(516): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(516): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(517): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(517): error C2955: 'boost::mpl::list' : use of class template requires template argument list --/mpl/aux_/preprocessed/plain/list.hpp(314) : see declaration of 'boost::mpl::list' --/math/policies/policy.hpp(518): error C3203: 'list' : unspecialized class template can't be used as a template argument for template parameter 'Seq', expected a real type --/math/policies/policy.hpp(518): fatal error C1003: error count exceeds 100; stopping compilation What have I done wrong ? TIA Jean

2 1

ambiguous overload for operator>> error when using lexical_cast with qvm::vec
by kique G 28 Sep '16

28 Sep '16

Hi, I am trying to use lexical_cast to convert from strings to qvm vectors, but I keep getting an ambiguous operator>> error. I have overloaded the >> operator for istreams and that seems to be working fine when I use it to read from a istringstream. In a lexical_cast, though, I get the "ambiguous overload for operator>>" error. I have tried declaring my operator>> overload inside the std and boost::qvm namespaces to check if it was something related to ADL, but I keep getting the same error. The thing is the other candidates do not seem to make a lot of sense to me. Could somebody please tell me what I am doing wrong? Thanks in advance, Enrique Garcia This is a minimal example (I am building gcc/boost from the last versions on their repositories): #include <iostream> #include <boost/qvm/vec.hpp> #include <boost/lexical_cast.hpp> std::ostream& operator<<(std::ostream& out, boost::qvm::vec<float, 3> const& v) { out << "(" << v.a[0] << "," << v.a[1] << "," << v.a[2] << ")"; } std::istream& operator>>(std::istream& in, boost::qvm::vec<float, 3>& v) { char c; return in >> c >> v.a[0] >> c >> v.a[1] >> c >> v.a[2] >> c; } int main() { boost::qvm::vec<float, 3> vect { 1.0f, 2.0f, 3.0f }; std::cout << vect << std::endl; // This code works just fine. (4.0,5.0,6.0) is printed std::istringstream istream("(4.0,5.0,6.0"); istream >> vect; std::cout << vect << std::endl; // This code generates an ambiguous overload for operator>> error (see below) vect = boost::lexical_cast<boost::qvm::vec<float, 3>>("(1.0,2.0,3.0)"); std::cout << vect << std::endl; return 0; } This is the error I am getting from gcc: In file included from /usr/local/include/boost/config.hpp:61:0, from /usr/local/include/boost/static_assert.hpp:17, from /usr/local/include/boost/qvm/static_assert.hpp:7, from /usr/local/include/boost/qvm/vec.hpp:11, from /home/kique/Documents/Bitflow2x/source/main.cpp:57: /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp: In instantiation of 'const bool boost::detail::has_right_shift_impl::operator_exists<std::basic_istream<char>, boost::qvm::vec<float, 3> >::value': /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:179:4: required from 'const bool boost::detail::has_right_shift_impl::trait_impl1<std::basic_istream<char>, boost::qvm::vec<float, 3>, boost::detail::has_right_shift_impl::dont_care, false>::value' /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:208:4: required from 'const bool boost::detail::has_right_shift_impl::trait_impl<std::basic_istream<char>, boost::qvm::vec<float, 3>, boost::detail::has_right_shift_impl::dont_care>::value' /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:216:8: required from 'struct boost::has_right_shift<std::basic_istream<char>, boost::qvm::vec<float, 3>, boost::detail::has_right_shift_impl::dont_care>' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:241:21: required from 'struct boost::detail::deduce_target_char_impl<boost::detail::deduce_character_type_later<boost::qvm::vec<float, 3> > >' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:270:89: required from 'struct boost::detail::deduce_target_char<boost::qvm::vec<float, 3> >' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:407:92: required from 'struct boost::detail::lexical_cast_stream_traits<const char*, boost::qvm::vec<float, 3> >' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:468:15: required from 'struct boost::detail::lexical_converter_impl<boost::qvm::vec<float, 3>, const char*>' /usr/local/include/boost/lexical_cast/try_lexical_convert.hpp:196:44: required from 'bool boost::conversion::detail::try_lexical_convert(const Source&, Target&) [with Target = boost::qvm::vec<float, 3>; Source = char [14]]' /usr/local/include/boost/lexical_cast.hpp:41:60: required from 'Target boost::lexical_cast(const Source&) [with Target = boost::qvm::vec<float, 3>; Source = char [14]]' /home/kique/Documents/Bitflow2x/source/main.cpp:83:72: required from here /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:158:70: error: ambiguous overload for 'operator>>' (operand types are 'std::basic_istream<char>' and 'boost::qvm::vec<float, 3>') BOOST_STATIC_CONSTANT(bool, value = (sizeof(s_check(((make<Lhs>() BOOST_TT_TRAIT_OP make<Rhs>()),make<has_operator>())))==sizeof(::boost::type_traits::yes_type))); ^ In file included from /usr/local/include/c++/7.0.0/iostream:40:0, from /home/kique/Documents/Bitflow2x/source/main.cpp:56: /usr/local/include/c++/7.0.0/istream:120:7: note: candidate: std::basic_istream<_CharT, _Traits>::__istream_type& std::basic_istream<_CharT, _Traits>::operator>>(std::basic_istream<_CharT, _Traits>::__istream_type& (*)(std::basic_istream<_CharT, _Traits>::__istream_type&)) [with _CharT = char; _Traits = std::char_traits<char>; std::basic_istream<_CharT, _Traits>::__istream_type = std::basic_istream<char>] operator>>(__istream_type& (*__pf)(__istream_type&)) ^~~~~~~~ /usr/local/include/c++/7.0.0/istream:124:7: note: candidate: std::basic_istream<_CharT, _Traits>::__istream_type& std::basic_istream<_CharT, _Traits>::operator>>(std::basic_istream<_CharT, _Traits>::__ios_type& (*)(std::basic_istream<_CharT, _Traits>::__ios_type&)) [with _CharT = char; _Traits = std::char_traits<char>; std::basic_istream<_CharT, _Traits>::__istream_type = std::basic_istream<char>; std::basic_istream<_CharT, _Traits>::__ios_type = std::basic_ios<char>] operator>>(__ios_type& (*__pf)(__ios_type&)) ^~~~~~~~ /usr/local/include/c++/7.0.0/istream:131:7: note: candidate: std::basic_istream<_CharT, _Traits>::__istream_type& std::basic_istream<_CharT, _Traits>::operator>>(std::ios_base& (*)(std::ios_base&)) [with _CharT = char; _Traits = std::char_traits<char>; std::basic_istream<_CharT, _Traits>::__istream_type = std::basic_istream<char>] operator>>(ios_base& (*__pf)(ios_base&)) ^~~~~~~~ /usr/local/include/c++/7.0.0/istream:259:7: note: candidate: std::basic_istream<_CharT, _Traits>& std::basic_istream<_CharT, _Traits>::operator>>(std::basic_istream<_CharT, _Traits>::__streambuf_type*) [with _CharT = char; _Traits = std::char_traits<char>; std::basic_istream<_CharT, _Traits>::__streambuf_type = std::basic_streambuf<char>] operator>>(__streambuf_type* __sb); ^~~~~~~~ In file included from /usr/local/include/boost/type_traits/has_right_shift.hpp:43:0, from /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:39, from /usr/local/include/boost/lexical_cast/try_lexical_convert.hpp:42, from /usr/local/include/boost/lexical_cast.hpp:32, from /home/kique/Documents/Bitflow2x/source/main.cpp:58: /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:70:13: note: candidate: boost::detail::has_right_shift_impl::no_operator boost::detail::has_right_shift_impl::operator>>(const boost::detail::has_right_shift_impl::any&, const boost::detail::has_right_shift_impl::any&) no_operator operator BOOST_TT_TRAIT_OP (const any&, const any&); ^~~~~~~~ In file included from /usr/local/include/c++/7.0.0/iostream:40:0, from /home/kique/Documents/Bitflow2x/source/main.cpp:56: /usr/local/include/c++/7.0.0/istream:808:5: note: candidate: std::basic_istream<char, _Traits>& std::operator>>(std::basic_istream<char, _Traits>&, signed char*) [with _Traits = std::char_traits<char>] operator>>(basic_istream<char, _Traits>& __in, signed char* __s) ^~~~~~~~ /usr/local/include/c++/7.0.0/istream:803:5: note: candidate: std::basic_istream<char, _Traits>& std::operator>>(std::basic_istream<char, _Traits>&, unsigned char*) [with _Traits = std::char_traits<char>] operator>>(basic_istream<char, _Traits>& __in, unsigned char* __s) ^~~~~~~~ In file included from /usr/local/include/boost/config.hpp:61:0, from /usr/local/include/boost/static_assert.hpp:17, from /usr/local/include/boost/qvm/static_assert.hpp:7, from /usr/local/include/boost/qvm/vec.hpp:11, from /home/kique/Documents/Bitflow2x/source/main.cpp:57: /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp: In instantiation of 'const bool boost::detail::has_right_shift_impl::operator_returns_void<std::basic_istream<char>, boost::qvm::vec<float, 3> >::value': /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:179:4: required from 'const bool boost::detail::has_right_shift_impl::trait_impl1<std::basic_istream<char>, boost::qvm::vec<float, 3>, boost::detail::has_right_shift_impl::dont_care, false>::value' /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:208:4: required from 'const bool boost::detail::has_right_shift_impl::trait_impl<std::basic_istream<char>, boost::qvm::vec<float, 3>, boost::detail::has_right_shift_impl::dont_care>::value' /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:216:8: required from 'struct boost::has_right_shift<std::basic_istream<char>, boost::qvm::vec<float, 3>, boost::detail::has_right_shift_impl::dont_care>' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:241:21: required from 'struct boost::detail::deduce_target_char_impl<boost::detail::deduce_character_type_later<boost::qvm::vec<float, 3> > >' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:270:89: required from 'struct boost::detail::deduce_target_char<boost::qvm::vec<float, 3> >' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:407:92: required from 'struct boost::detail::lexical_cast_stream_traits<const char*, boost::qvm::vec<float, 3> >' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:468:15: required from 'struct boost::detail::lexical_converter_impl<boost::qvm::vec<float, 3>, const char*>' /usr/local/include/boost/lexical_cast/try_lexical_convert.hpp:196:44: required from 'bool boost::conversion::detail::try_lexical_convert(const Source&, Target&) [with Target = boost::qvm::vec<float, 3>; Source = char [14]]' /usr/local/include/boost/lexical_cast.hpp:41:60: required from 'Target boost::lexical_cast(const Source&) [with Target = boost::qvm::vec<float, 3>; Source = char [14]]' /home/kique/Documents/Bitflow2x/source/main.cpp:83:72: required from here /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:95:114: error: ambiguous overload for 'operator>>' (operand types are 'std::basic_istream<char>' and 'boost::qvm::vec<float, 3>') BOOST_STATIC_CONSTANT(bool, value = (sizeof(::boost::type_traits::yes_type)==sizeof(returns_void((make<Lhs>() BOOST_TT_TRAIT_OP make<Rhs>(),returns_void_t()))))); ^ In file included from /usr/local/include/c++/7.0.0/iostream:40:0, from /home/kique/Documents/Bitflow2x/source/main.cpp:56: /usr/local/include/c++/7.0.0/istream:120:7: note: candidate: std::basic_istream<_CharT, _Traits>::__istream_type& std::basic_istream<_CharT, _Traits>::operator>>(std::basic_istream<_CharT, _Traits>::__istream_type& (*)(std::basic_istream<_CharT, _Traits>::__istream_type&)) [with _CharT = char; _Traits = std::char_traits<char>; std::basic_istream<_CharT, _Traits>::__istream_type = std::basic_istream<char>] operator>>(__istream_type& (*__pf)(__istream_type&)) ^~~~~~~~ /usr/local/include/c++/7.0.0/istream:124:7: note: candidate: std::basic_istream<_CharT, _Traits>::__istream_type& std::basic_istream<_CharT, _Traits>::operator>>(std::basic_istream<_CharT, _Traits>::__ios_type& (*)(std::basic_istream<_CharT, _Traits>::__ios_type&)) [with _CharT = char; _Traits = std::char_traits<char>; std::basic_istream<_CharT, _Traits>::__istream_type = std::basic_istream<char>; std::basic_istream<_CharT, _Traits>::__ios_type = std::basic_ios<char>] operator>>(__ios_type& (*__pf)(__ios_type&)) ^~~~~~~~ /usr/local/include/c++/7.0.0/istream:131:7: note: candidate: std::basic_istream<_CharT, _Traits>::__istream_type& std::basic_istream<_CharT, _Traits>::operator>>(std::ios_base& (*)(std::ios_base&)) [with _CharT = char; _Traits = std::char_traits<char>; std::basic_istream<_CharT, _Traits>::__istream_type = std::basic_istream<char>] operator>>(ios_base& (*__pf)(ios_base&)) ^~~~~~~~ /usr/local/include/c++/7.0.0/istream:259:7: note: candidate: std::basic_istream<_CharT, _Traits>& std::basic_istream<_CharT, _Traits>::operator>>(std::basic_istream<_CharT, _Traits>::__streambuf_type*) [with _CharT = char; _Traits = std::char_traits<char>; std::basic_istream<_CharT, _Traits>::__streambuf_type = std::basic_streambuf<char>] operator>>(__streambuf_type* __sb); ^~~~~~~~ In file included from /usr/local/include/boost/type_traits/has_right_shift.hpp:43:0, from /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:39, from /usr/local/include/boost/lexical_cast/try_lexical_convert.hpp:42, from /usr/local/include/boost/lexical_cast.hpp:32, from /home/kique/Documents/Bitflow2x/source/main.cpp:58: /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:70:13: note: candidate: boost::detail::has_right_shift_impl::no_operator boost::detail::has_right_shift_impl::operator>>(const boost::detail::has_right_shift_impl::any&, const boost::detail::has_right_shift_impl::any&) no_operator operator BOOST_TT_TRAIT_OP (const any&, const any&); ^~~~~~~~ In file included from /usr/local/include/c++/7.0.0/iostream:40:0, from /home/kique/Documents/Bitflow2x/source/main.cpp:56: /usr/local/include/c++/7.0.0/istream:808:5: note: candidate: std::basic_istream<char, _Traits>& std::operator>>(std::basic_istream<char, _Traits>&, signed char*) [with _Traits = std::char_traits<char>] operator>>(basic_istream<char, _Traits>& __in, signed char* __s) ^~~~~~~~ /usr/local/include/c++/7.0.0/istream:803:5: note: candidate: std::basic_istream<char, _Traits>& std::operator>>(std::basic_istream<char, _Traits>&, unsigned char*) [with _Traits = std::char_traits<char>] operator>>(basic_istream<char, _Traits>& __in, unsigned char* __s) ^~~~~~~~ In file included from /usr/local/include/boost/lexical_cast/try_lexical_convert.hpp:42:0, from /usr/local/include/boost/lexical_cast.hpp:32, from /home/kique/Documents/Bitflow2x/source/main.cpp:58: /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp: In instantiation of 'struct boost::detail::deduce_target_char_impl<boost::detail::deduce_character_type_later<boost::qvm::vec<float, 3> > >': /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:270:89: required from 'struct boost::detail::deduce_target_char<boost::qvm::vec<float, 3> >' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:407:92: required from 'struct boost::detail::lexical_cast_stream_traits<const char*, boost::qvm::vec<float, 3> >' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:468:15: required from 'struct boost::detail::lexical_converter_impl<boost::qvm::vec<float, 3>, const char*>' /usr/local/include/boost/lexical_cast/try_lexical_convert.hpp:196:44: required from 'bool boost::conversion::detail::try_lexical_convert(const Source&, Target&) [with Target = boost::qvm::vec<float, 3>; Source = char [14]]' /usr/local/include/boost/lexical_cast.hpp:41:60: required from 'Target boost::lexical_cast(const Source&) [with Target = boost::qvm::vec<float, 3>; Source = char [14]]' /home/kique/Documents/Bitflow2x/source/main.cpp:83:72: required from here /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:241:21: error: 'value' is not a member of 'boost::has_right_shift<std::basic_istream<char>, boost::qvm::vec<float, 3>, boost::detail::has_right_shift_impl::dont_care>' >::type type; ^~~~ In file included from /usr/local/include/boost/qvm/static_assert.hpp:7:0, from /usr/local/include/boost/qvm/vec.hpp:11, from /home/kique/Documents/Bitflow2x/source/main.cpp:57: /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:243:13: error: 'value' is not a member of 'boost::detail::deduce_target_char_impl<boost::detail::deduce_character_type_later<boost::qvm::vec<float, 3> > >::result_t {aka boost::has_right_shift<std::basic_istream<char>, boost::qvm::vec<float, 3>, boost::detail::has_right_shift_impl::dont_care>}' BOOST_STATIC_ASSERT_MSG((result_t::value || boost::has_right_shift<std::basic_istream<wchar_t>, T >::value), ^ In file included from /usr/local/include/boost/config.hpp:61:0, from /usr/local/include/boost/static_assert.hpp:17, from /usr/local/include/boost/qvm/static_assert.hpp:7, from /usr/local/include/boost/qvm/vec.hpp:11, from /home/kique/Documents/Bitflow2x/source/main.cpp:57: /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp: In instantiation of 'const bool boost::detail::has_right_shift_impl::operator_exists<std::basic_istream<wchar_t>, boost::qvm::vec<float, 3> >::value': /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:179:4: required from 'const bool boost::detail::has_right_shift_impl::trait_impl1<std::basic_istream<wchar_t>, boost::qvm::vec<float, 3>, boost::detail::has_right_shift_impl::dont_care, false>::value' /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:208:4: required from 'const bool boost::detail::has_right_shift_impl::trait_impl<std::basic_istream<wchar_t>, boost::qvm::vec<float, 3>, boost::detail::has_right_shift_impl::dont_care>::value' /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:216:8: required from 'struct boost::has_right_shift<std::basic_istream<wchar_t>, boost::qvm::vec<float, 3>, boost::detail::has_right_shift_impl::dont_care>' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:243:13: required from 'struct boost::detail::deduce_target_char_impl<boost::detail::deduce_character_type_later<boost::qvm::vec<float, 3> > >' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:270:89: required from 'struct boost::detail::deduce_target_char<boost::qvm::vec<float, 3> >' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:407:92: required from 'struct boost::detail::lexical_cast_stream_traits<const char*, boost::qvm::vec<float, 3> >' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:468:15: required from 'struct boost::detail::lexical_converter_impl<boost::qvm::vec<float, 3>, const char*>' /usr/local/include/boost/lexical_cast/try_lexical_convert.hpp:196:44: required from 'bool boost::conversion::detail::try_lexical_convert(const Source&, Target&) [with Target = boost::qvm::vec<float, 3>; Source = char [14]]' /usr/local/include/boost/lexical_cast.hpp:41:60: required from 'Target boost::lexical_cast(const Source&) [with Target = boost::qvm::vec<float, 3>; Source = char [14]]' /home/kique/Documents/Bitflow2x/source/main.cpp:83:72: required from here /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:158:70: error: ambiguous overload for 'operator>>' (operand types are 'std::basic_istream<wchar_t>' and 'boost::qvm::vec<float, 3>') BOOST_STATIC_CONSTANT(bool, value = (sizeof(s_check(((make<Lhs>() BOOST_TT_TRAIT_OP make<Rhs>()),make<has_operator>())))==sizeof(::boost::type_traits::yes_type))); ^ In file included from /usr/local/include/c++/7.0.0/iostream:40:0, from /home/kique/Documents/Bitflow2x/source/main.cpp:56: /usr/local/include/c++/7.0.0/istream:120:7: note: candidate: std::basic_istream<_CharT, _Traits>::__istream_type& std::basic_istream<_CharT, _Traits>::operator>>(std::basic_istream<_CharT, _Traits>::__istream_type& (*)(std::basic_istream<_CharT, _Traits>::__istream_type&)) [with _CharT = wchar_t; _Traits = std::char_traits<wchar_t>; std::basic_istream<_CharT, _Traits>::__istream_type = std::basic_istream<wchar_t>] operator>>(__istream_type& (*__pf)(__istream_type&)) ^~~~~~~~ /usr/local/include/c++/7.0.0/istream:124:7: note: candidate: std::basic_istream<_CharT, _Traits>::__istream_type& std::basic_istream<_CharT, _Traits>::operator>>(std::basic_istream<_CharT, _Traits>::__ios_type& (*)(std::basic_istream<_CharT, _Traits>::__ios_type&)) [with _CharT = wchar_t; _Traits = std::char_traits<wchar_t>; std::basic_istream<_CharT, _Traits>::__istream_type = std::basic_istream<wchar_t>; std::basic_istream<_CharT, _Traits>::__ios_type = std::basic_ios<wchar_t>] operator>>(__ios_type& (*__pf)(__ios_type&)) ^~~~~~~~ /usr/local/include/c++/7.0.0/istream:131:7: note: candidate: std::basic_istream<_CharT, _Traits>::__istream_type& std::basic_istream<_CharT, _Traits>::operator>>(std::ios_base& (*)(std::ios_base&)) [with _CharT = wchar_t; _Traits = std::char_traits<wchar_t>; std::basic_istream<_CharT, _Traits>::__istream_type = std::basic_istream<wchar_t>] operator>>(ios_base& (*__pf)(ios_base&)) ^~~~~~~~ /usr/local/include/c++/7.0.0/istream:259:7: note: candidate: std::basic_istream<_CharT, _Traits>& std::basic_istream<_CharT, _Traits>::operator>>(std::basic_istream<_CharT, _Traits>::__streambuf_type*) [with _CharT = wchar_t; _Traits = std::char_traits<wchar_t>; std::basic_istream<_CharT, _Traits>::__streambuf_type = std::basic_streambuf<wchar_t>] operator>>(__streambuf_type* __sb); ^~~~~~~~ In file included from /usr/local/include/boost/type_traits/has_right_shift.hpp:43:0, from /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:39, from /usr/local/include/boost/lexical_cast/try_lexical_convert.hpp:42, from /usr/local/include/boost/lexical_cast.hpp:32, from /home/kique/Documents/Bitflow2x/source/main.cpp:58: /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:70:13: note: candidate: boost::detail::has_right_shift_impl::no_operator boost::detail::has_right_shift_impl::operator>>(const boost::detail::has_right_shift_impl::any&, const boost::detail::has_right_shift_impl::any&) no_operator operator BOOST_TT_TRAIT_OP (const any&, const any&); ^~~~~~~~ In file included from /usr/local/include/boost/config.hpp:61:0, from /usr/local/include/boost/static_assert.hpp:17, from /usr/local/include/boost/qvm/static_assert.hpp:7, from /usr/local/include/boost/qvm/vec.hpp:11, from /home/kique/Documents/Bitflow2x/source/main.cpp:57: /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp: In instantiation of 'const bool boost::detail::has_right_shift_impl::operator_returns_void<std::basic_istream<wchar_t>, boost::qvm::vec<float, 3> >::value': /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:179:4: required from 'const bool boost::detail::has_right_shift_impl::trait_impl1<std::basic_istream<wchar_t>, boost::qvm::vec<float, 3>, boost::detail::has_right_shift_impl::dont_care, false>::value' /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:208:4: required from 'const bool boost::detail::has_right_shift_impl::trait_impl<std::basic_istream<wchar_t>, boost::qvm::vec<float, 3>, boost::detail::has_right_shift_impl::dont_care>::value' /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:216:8: required from 'struct boost::has_right_shift<std::basic_istream<wchar_t>, boost::qvm::vec<float, 3>, boost::detail::has_right_shift_impl::dont_care>' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:243:13: required from 'struct boost::detail::deduce_target_char_impl<boost::detail::deduce_character_type_later<boost::qvm::vec<float, 3> > >' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:270:89: required from 'struct boost::detail::deduce_target_char<boost::qvm::vec<float, 3> >' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:407:92: required from 'struct boost::detail::lexical_cast_stream_traits<const char*, boost::qvm::vec<float, 3> >' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:468:15: required from 'struct boost::detail::lexical_converter_impl<boost::qvm::vec<float, 3>, const char*>' /usr/local/include/boost/lexical_cast/try_lexical_convert.hpp:196:44: required from 'bool boost::conversion::detail::try_lexical_convert(const Source&, Target&) [with Target = boost::qvm::vec<float, 3>; Source = char [14]]' /usr/local/include/boost/lexical_cast.hpp:41:60: required from 'Target boost::lexical_cast(const Source&) [with Target = boost::qvm::vec<float, 3>; Source = char [14]]' /home/kique/Documents/Bitflow2x/source/main.cpp:83:72: required from here /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:95:114: error: ambiguous overload for 'operator>>' (operand types are 'std::basic_istream<wchar_t>' and 'boost::qvm::vec<float, 3>') BOOST_STATIC_CONSTANT(bool, value = (sizeof(::boost::type_traits::yes_type)==sizeof(returns_void((make<Lhs>() BOOST_TT_TRAIT_OP make<Rhs>(),returns_void_t()))))); ^ In file included from /usr/local/include/c++/7.0.0/iostream:40:0, from /home/kique/Documents/Bitflow2x/source/main.cpp:56: /usr/local/include/c++/7.0.0/istream:120:7: note: candidate: std::basic_istream<_CharT, _Traits>::__istream_type& std::basic_istream<_CharT, _Traits>::operator>>(std::basic_istream<_CharT, _Traits>::__istream_type& (*)(std::basic_istream<_CharT, _Traits>::__istream_type&)) [with _CharT = wchar_t; _Traits = std::char_traits<wchar_t>; std::basic_istream<_CharT, _Traits>::__istream_type = std::basic_istream<wchar_t>] operator>>(__istream_type& (*__pf)(__istream_type&)) ^~~~~~~~ /usr/local/include/c++/7.0.0/istream:124:7: note: candidate: std::basic_istream<_CharT, _Traits>::__istream_type& std::basic_istream<_CharT, _Traits>::operator>>(std::basic_istream<_CharT, _Traits>::__ios_type& (*)(std::basic_istream<_CharT, _Traits>::__ios_type&)) [with _CharT = wchar_t; _Traits = std::char_traits<wchar_t>; std::basic_istream<_CharT, _Traits>::__istream_type = std::basic_istream<wchar_t>; std::basic_istream<_CharT, _Traits>::__ios_type = std::basic_ios<wchar_t>] operator>>(__ios_type& (*__pf)(__ios_type&)) ^~~~~~~~ /usr/local/include/c++/7.0.0/istream:131:7: note: candidate: std::basic_istream<_CharT, _Traits>::__istream_type& std::basic_istream<_CharT, _Traits>::operator>>(std::ios_base& (*)(std::ios_base&)) [with _CharT = wchar_t; _Traits = std::char_traits<wchar_t>; std::basic_istream<_CharT, _Traits>::__istream_type = std::basic_istream<wchar_t>] operator>>(ios_base& (*__pf)(ios_base&)) ^~~~~~~~ /usr/local/include/c++/7.0.0/istream:259:7: note: candidate: std::basic_istream<_CharT, _Traits>& std::basic_istream<_CharT, _Traits>::operator>>(std::basic_istream<_CharT, _Traits>::__streambuf_type*) [with _CharT = wchar_t; _Traits = std::char_traits<wchar_t>; std::basic_istream<_CharT, _Traits>::__streambuf_type = std::basic_streambuf<wchar_t>] operator>>(__streambuf_type* __sb); ^~~~~~~~ In file included from /usr/local/include/boost/type_traits/has_right_shift.hpp:43:0, from /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:39, from /usr/local/include/boost/lexical_cast/try_lexical_convert.hpp:42, from /usr/local/include/boost/lexical_cast.hpp:32, from /home/kique/Documents/Bitflow2x/source/main.cpp:58: /usr/local/include/boost/type_traits/detail/has_binary_operator.hpp:70:13: note: candidate: boost::detail::has_right_shift_impl::no_operator boost::detail::has_right_shift_impl::operator>>(const boost::detail::has_right_shift_impl::any&, const boost::detail::has_right_shift_impl::any&) no_operator operator BOOST_TT_TRAIT_OP (const any&, const any&); ^~~~~~~~ In file included from /usr/local/include/boost/qvm/static_assert.hpp:7:0, from /usr/local/include/boost/qvm/vec.hpp:11, from /home/kique/Documents/Bitflow2x/source/main.cpp:57: /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp: In instantiation of 'struct boost::detail::deduce_target_char_impl<boost::detail::deduce_character_type_later<boost::qvm::vec<float, 3> > >': /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:270:89: required from 'struct boost::detail::deduce_target_char<boost::qvm::vec<float, 3> >' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:407:92: required from 'struct boost::detail::lexical_cast_stream_traits<const char*, boost::qvm::vec<float, 3> >' /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:468:15: required from 'struct boost::detail::lexical_converter_impl<boost::qvm::vec<float, 3>, const char*>' /usr/local/include/boost/lexical_cast/try_lexical_convert.hpp:196:44: required from 'bool boost::conversion::detail::try_lexical_convert(const Source&, Target&) [with Target = boost::qvm::vec<float, 3>; Source = char [14]]' /usr/local/include/boost/lexical_cast.hpp:41:60: required from 'Target boost::lexical_cast(const Source&) [with Target = boost::qvm::vec<float, 3>; Source = char [14]]' /home/kique/Documents/Bitflow2x/source/main.cpp:83:72: required from here /usr/local/include/boost/lexical_cast/detail/converter_lexical.hpp:243:13: error: 'value' is not a member of 'boost::has_right_shift<std::basic_istream<wchar_t>, boost::qvm::vec<float, 3>, boost::detail::has_right_shift_impl::dont_care>' BOOST_STATIC_ASSERT_MSG((result_t::value || boost::has_right_shift<std::basic_istream<wchar_t>, T >::value), ^ ninja: build stopped: subcommand failed.

2 1

[release] Boost 1.62.0 Release Candidate 1
by Rene Rivera 28 Sep '16

28 Sep '16

The release candidates for the 1.62.0 release are now available at: https://sourceforge.net/projects/boost/files/boost/1.62.0.rc.1/boost_1_62_0… https://sourceforge.net/projects/boost/files/boost/1.62.0.rc.1/boost_1_62_0… https://sourceforge.net/projects/boost/files/boost/1.62.0.rc.1/boost_1_62_0… https://sourceforge.net/projects/boost/files/boost/1.62.0.rc.1/boost_1_62_0… The SHA256 checksums are as follows: b91c2cda8bee73ea613130e19e72c9589e9ef0357c4c5cc5f7523de82cce11f7 boost_1_62_0_rc1.7z 36c96b0f6155c98404091d8ceb48319a28279ca0333fba1ad8611eb90afb2ca0 boost_1_62_0_rc1.tar.bz2 440a59f8bc4023dbe6285c9998b0f7fa288468b889746b1ef00e8b36c559dce1 boost_1_62_0_rc1.tar.gz 084b2e0638bbe0975a9e43e21bc9ceae33ef11377aecab3268a57cf41e405d4e boost_1_62_0_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. Thanks, the release managers. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

5 6

[boost][heap] Which heap to use.
by degski 27 Sep '16

27 Sep '16

Hi All, I seem to remember reading about this [the subject of this post] in the docs, but I don't seem to be able to find it [that page] now. What criteria should I use to choose a specific Boost.Heap implementation (skew, fibonacci etc), from the ones provided by the Boost.Heap library? Thanks in advance and have a good day, degski

3 10

newbie !!
by MAURICE Jean 27 Sep '16

27 Sep '16

Hi, This is my second 'account' to this mailing list. In fact I am a freelance who works for a company that works for another company and when I am somewhere I can't have access to the 'elsewhere' outlook. I am an old C++ (and FORTRAN and Visual Foxpro) programmer. But I am new to boost, windows (MFC) and Visual Studio 2010. My challenge is to 'upgrade' a huge app (250 k lines of code) both Windows and Linux from boost 1.3.x (and stingray and .....) to boost 1.50 and win 7 ... Boost 1.50 is the last version our customer can use because of its 'private' version of Debian. I am first dealing with windows. When I compile the solution, I get a lot of errors and I would like you give me the first steps to do. Here is an example about file ...\boost\boost15\boost_1_50_0\boost/mpl/list/aux_/preprocessed/plain/list20.hpp list20.hpp(157): error C2143: syntax error : missing ',' before 'string' list20.hpp(163): error C2974: 'boost::mpl::list19' : invalid template argument for 'T18', type expected list20.hpp(144) : see declaration of 'boost::mpl::list19' list20.hpp(167) : see reference to class template instantiation 'boost::mpl::list20<T0,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,__formal>' being compiled list20.hpp(164): error C3203: 'list19' : unspecialized class template can't be used as a template argument for template parameter 'Next', expected a real type list20.hpp(164): error C2955: 'boost::mpl::list19' : use of class template requires template argument list list20.hpp(144) : see declaration of 'boost::mpl::list19' list20.hpp(165): error C2955: 'boost::mpl::l_item' : use of class template requires template argument list So if you can explain me what is wrong (I mean I am astonished (?) to find a syntax error and I think I must not modify the file so the error may come from elsewhere ...) TIA Jean

2 3

[fiber] High CPU usage when fiber round robin sheduler is idle
by lin li 26 Sep '16

26 Sep '16

Hi, guys. I have a problem with Boost fiber in 1.62 beta 2. My machine is a 4 core machine with 64bit ubuntu 14.04 installed. In my program, I created 4 kernel threads each of which uses the round robin fiber scheduler. One thread 1, I created one fiber that read data from a socket in a blocking manner. Once it got some data, it writes the data into a blocking fiber channel. For the rest thread kernel threads, I created 5 fibers for each of them. They all read (in a blocking manner) data from the same channel. My problem is when no data is sent to the socket, and the system is idling, I can see very high CPU usage on three cores. I profiled the code, it seems to me that the kernel threads keep calling fiber scheduler to sleep then wake up again. I suspect that the time interval for the function suspend_until() may be too short. If that is the case, then how can I increase it?

2 1

[serialization] Runtime overhead of serialization archives
by georg＠schorsch-tech.de 25 Sep '16

25 Sep '16

Hi all, currently i try to measure the runtime overhead of serialization vs. plain c-style serialization. The goal is to send it from one process to an other process on the same machine. As my statemachines are written with boost::msm, i want to deliver types. For the IPC i used interprocess::message_queue. I wrote a template function for the test and added a trait to plug in the test functions. I tested on the same machine, once with Linux Debian stretch x64 and Win 10 x64 MSVC 2015. What really astonish me is the fact, that the measured times using boost::serilization is so high compared to "c-style: id + data" method. In the c-style method i used a FNV hash of the type name as the ID. All tests were done on a Intel Core i7 2670QM CPU. All results in sec. I sent/received 100000 objects over a message_queue. Boost 1.61.0 Linux x86_64 / gcc 6.1.1 Win 10 x64/ MSVC 2015 Boost XML Send 2.220753 8.255834 Boost XML Receive 3.208353 10.14462 Boost Text Send 2.024946 8.578654 Boost Text Receive 3.207359 10.704126 Boost BinarySend 2.018026 8.363865 Boost Binary Receive 3.17984 11.201501 Cstyle Send 0.13566 0.056814 Cstyle Receive 0.087906 0.058706 Char Send 0.071683 0.013965 Char Receive 0.062119 0.012631 To measure the real overhead of the message passing, i made a test and just sent 100000 plain chars over the "wire". There are two strange things: a) The serilization with boost seems to be about 16 times slower than the plain c-style method, the receive seems to be about 30 times slower. I think i do something wrong..... he tests were compiled on release mode. b) On the same hardware, the Windows implementation is so much slower than the Linux one... about factor 3. But at the c-style method, it turns around.... Linux is slower than Windows. Has anyone an idea whats the issue here? I added the code at the end of this text Best regards Georg // ----------------------------------------------------- // Code // ----------------------------------------------------- #define BOOST_TEST_MODULE first_tests #include <boost/test/unit_test.hpp> #include <boost/interprocess/ipc/message_queue.hpp> // send all data through this #include <boost/timer/timer.hpp> // measure the used time #include <iostream> // for output // STL Archive + Stuff #include <boost/serialization/base_object.hpp> #include <boost/serialization/export.hpp> #include <boost/serialization/shared_ptr.hpp> #include <boost/serialization/unique_ptr.hpp> // include headers that implement a archive in xml format #include <boost/archive/archive_exception.hpp> #include <boost/archive/xml_iarchive.hpp> #include <boost/archive/xml_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/binary_iarchive.hpp> #include <boost/archive/binary_oarchive.hpp> #include <boost/iostreams/device/array.hpp> #include <boost/iostreams/device/back_inserter.hpp> #include <boost/iostreams/stream.hpp> #include <memory> #include <stdint.h> #include <typeinfo> #include <vector> using namespace boost::interprocess; static const int test_count = 100000; // send this many structs // the test structure struct ev_test { long a = 1; unsigned long b = 2; }; // ---------------------------------------------------------------------------- // a packet on the wire // ---------------------------------------------------------------------------- using packet = std::vector<char>; //----------------------------------------------------------------------------- // Type carrier and its support // ---------------------------------------------------------------------------- namespace { class carrier_visitor_base; class carrier_base // the base in the queue { public: using ptr = std::unique_ptr<carrier_base>; virtual ~carrier_base() {} virtual void accept(carrier_visitor_base *p_visitor) = 0; template <class Archive> void serialize(Archive &ar, const unsigned int version) { } }; template <typename T> class carrier; class carrier_visitor_base { public: virtual ~carrier_visitor_base() {} virtual void handle(carrier<ev_test> *p_evt) = 0; virtual void handle(carrier<char> *p_evt) = 0; }; template <typename T> class carrier : public carrier_base // the specific carrier { public: explicit carrier() : m_data() {} explicit carrier(const T &data) : m_data(data) {} virtual void accept(carrier_visitor_base *p_visitor) override { p_visitor->handle(this); } T &data() { return m_data; } private: T m_data; }; } // ns anon // ---------------------------------------------------------------------------- // the traits for the chartest // ---------------------------------------------------------------------------- struct char_test { static const char *name() { return "char_test 'c': "; } static size_t msg_size() { return sizeof(char); } static char get_data() { return 'c'; } template <typename T> static packet to_wire(T data) { packet ret; ret.push_back(get_data()); return ret; } static carrier_base::ptr from_wire(const packet &data) { auto p_data = new carrier<char>(); p_data->data() = data[0]; return std::unique_ptr<carrier<char>>(p_data); } }; // ---------------------------------------------------------------------------- // the traits for the boost xml serialization test // ---------------------------------------------------------------------------- // ---------------------------------------------------------------------------- // external serialization function // ---------------------------------------------------------------------------- namespace boost { namespace serialization { // serialization function for ev_test template <class Archive> inline void serialize(Archive &ar, ev_test &t, const unsigned int version) { ar &BOOST_SERIALIZATION_NVP(t.a); ar &BOOST_SERIALIZATION_NVP(t.b); } // serialization function for carrier<T> template <class Archive, typename T> void serialize(Archive &ar, carrier<T> &t, const unsigned int version) { ar &boost::serialization::make_nvp( "carrier_base", boost::serialization::base_object<carrier_base>(t)); // BOOST_SERIALIZATION_BASE_OBJECT_NVP(a); auto &data = t.data(); ar &BOOST_SERIALIZATION_NVP(data); } } } // we must export all carrier BOOST_SERIALIZATION_SHARED_PTR(carrier<ev_test>) BOOST_CLASS_EXPORT(carrier<ev_test>) struct boost_xml_trait { static const char *name() { return "boost_xml_test: ev_test: "; } typedef boost::archive::xml_oarchive oarchive; typedef boost::archive::xml_iarchive iarchive; }; struct boost_text_trait { static const char *name() { return "boost_text_test: ev_test: "; } typedef boost::archive::xml_oarchive oarchive; typedef boost::archive::xml_iarchive iarchive; }; struct boost_binary_trait { static const char *name() { return "boost_binary_test: ev_test: "; } typedef boost::archive::xml_oarchive oarchive; typedef boost::archive::xml_iarchive iarchive; }; template <typename archive_trait> struct boost_test { static const char *name() { return archive_trait::name(); } static size_t msg_size() { return 600; } // throws boost::archive::archive_exception template <typename T> static packet to_wire(T data) { using namespace boost::iostreams; using T1 = typename std::remove_cv<T>::type; using BT = typename std::remove_reference<T1>::type; carrier_base::ptr p_carrier = std::make_unique<carrier<BT>>(data); packet p; { back_insert_device<packet> sink{ p }; stream<back_insert_device<packet>> os{ sink }; typename archive_trait::oarchive oa(os); oa << BOOST_SERIALIZATION_NVP(p_carrier); } return p; } // throws boost::archive::archive_exception static carrier_base::ptr from_wire(const packet &data) { using namespace boost::iostreams; carrier_base::ptr p_carrier; boost::iostreams::array_source source{ data.data(), data.size() }; stream<array_source> is{ source }; typename archive_trait::iarchive ia(is); // this takes the most time ia >> BOOST_SERIALIZATION_NVP(p_carrier); return p_carrier; } }; // ---------------------------------------------------------------------------- // the traits for the cstyle serialization test // ---------------------------------------------------------------------------- // ---------------------------------------------------------------------------- // cstyle serialization with fnv type identifier // ---------------------------------------------------------------------------- struct cstyle_test { static const char *name() { return "cstyle_test: "; } static size_t msg_size() { return 1000; } // FowlerNollVo hash function // https://en.wikipedia.org/wiki/Fowler%E2%80%93Noll%E2%80%93Vo_hash_function struct fnv { const static uint64_t base = 0xcbf29ce484222325; const static uint64_t prime = 0x00000100000001b3; const static uint64_t next(uint64_t current, size_t char_code) { return (current ^ char_code) * prime; } const static uint64_t value(const char *cptr, uint64_t interim = base) { return (*cptr == '\0') ? interim : value(cptr + 1, next(interim, static_cast<size_t>(*cptr))); } }; template <typename T> static packet to_wire(T data) { packet buffer(msg_size()); // to be fair, send the same amount of bytes const uint64_t id = fnv::value(typeid(T).name()); size_t pos = 0; assert(msg_size() >= sizeof(uint64_t) + sizeof(T)); // buffer.resize(buffer.size() + sizeof(uint64_t) + sizeof(T)); std::memcpy(buffer.data() + pos, &id, sizeof(uint64_t)); pos += sizeof(uint64_t); std::memcpy(buffer.data() + pos, &data, sizeof(T)); pos += sizeof(T); return buffer; } static carrier_base::ptr from_wire(const packet &data) { // get the id size_t pos = 0; uint64_t id; std::memcpy(&id, data.data() + pos, sizeof(uint64_t)); pos += sizeof(uint64_t); // create the specific pointer if (id == fnv::value(typeid(ev_test).name())) { assert(data.size() >= sizeof(uint64_t) + sizeof(ev_test)); auto p_evt = new carrier<ev_test>(); std::memcpy(&p_evt->data(), data.data() + pos, sizeof(ev_test)); return carrier_base::ptr(p_evt); } throw std::runtime_error("deserialize error"); } }; template <typename trait> void do_test() { class runtime : public carrier_visitor_base { public: virtual void handle(carrier<ev_test> *p_evt) override { i += p_evt->data().a; } virtual void handle(carrier<char> *p_evt) override { i += p_evt->data(); } int i = 0; }; try { std::cout << "Sending " << trait::name() << test_count << std::endl; // Erase previous message queue message_queue::remove("message_queue"); // Create a message_queue. message_queue mq(create_only // only create , "message_queue" // name , test_count // max message number , trait::msg_size() // max message size ); // send ev_tests boost::timer::auto_cpu_timer t; for (int i = 0; i < test_count; ++i) { auto buffer = trait::to_wire(ev_test()); mq.send(buffer.data(), buffer.size(), 0); } } catch (const interprocess_exception &ex) { message_queue::remove("message_queue"); std::cout << ex.what() << std::endl; BOOST_CHECK(true == false); } runtime rt; try { std::cout << "Receiving " << trait::name() << test_count << std::endl; // Open a message queue. message_queue mq(open_only // only create , "message_queue" // name ); message_queue::size_type recvd_size; packet buffer(trait::msg_size()); unsigned int priority; boost::timer::auto_cpu_timer t; for (int i = 0; i < test_count; ++i) { // receive the raw data mq.receive(buffer.data(), buffer.size(), recvd_size, priority); // deserialize auto p_carrier = trait::from_wire(buffer); // handle it to the protocol p_carrier->accept(&rt); } } catch (const interprocess_exception &ex) { message_queue::remove("message_queue"); std::cout << ex.what() << std::endl; BOOST_CHECK(true == false); } message_queue::remove("message_queue"); std::cout << "RT Counter: " << rt.i << std::endl << std::endl; } BOOST_AUTO_TEST_CASE(carrier_boost_xml_ev_test) { do_test<boost_test<boost_xml_trait>>(); } BOOST_AUTO_TEST_CASE(carrier_boost_text_ev_test) { do_test<boost_test<boost_text_trait>>(); } BOOST_AUTO_TEST_CASE(carrier_boost_binary_ev_test) { do_test<boost_test<boost_binary_trait>>(); } BOOST_AUTO_TEST_CASE(carrier_cstyle_ev_test) { do_test<cstyle_test>(); } BOOST_AUTO_TEST_CASE(carrier_char_test) { do_test<char_test>(); }

6 20

[boost][multiprecision] compile error with gcc 4.8.4
by Rob Conde 24 Sep '16

24 Sep '16

Please see the scenario below...am I doing something wrong or is this a gcc or multiprecision bug? Thanks, Rob Conde given the following code (multiPrecisionTest.cpp): #include <boost/multiprecision/cpp_int.hpp> #include <boost/multiprecision/cpp_bin_float.hpp> typedef boost::multiprecision::int128_t int128_t; typedef boost::multiprecision::cpp_bin_float_quad float128_t; int main() { int128_t intVal; float128_t floatVal(intVal.convert_to<float128_t>()); return 0; } -------------------------------------------------------------------------- g++ -std=c++0x -c multiPrecisionTest.cpp I get the following error: In file included from ./boost/multiprecision/cpp_int.hpp:1936:0, from multiPrecisionTest.cpp:1: ./boost/multiprecision/cpp_int/misc.hpp: In instantiation of ‘typename boost::enable_if_c<(boost::multiprecision::backends::is_trivial_cpp_int<boost::multiprecision::backends::cpp_int_backend<MinBits1, MaxBits1, SignType1, Checked1, Allocator1> >::value && boost::multiprecision::is_signed_number<boost::multiprecision::backends::cpp_int_backend<MinBits1, MaxBits1, SignType1, Checked1, Allocator1> >::value)>::type boost::multiprecision::backends::eval_convert_to(R*, const boost::multiprecision::backends::cpp_int_backend<MinBits1, MaxBits1, SignType1, Checked1, Allocator1>&) [with R = boost::multiprecision::number<boost::multiprecision::backends::cpp_bin_float<113u, (boost::multiprecision::backends::digit_base_type)2u, void, short int, -16382, 16383>, (boost::multiprecision::expression_template_option)0u>; unsigned int MinBits1 = 128u; unsigned int MaxBits1 = 128u; boost::multiprecision::cpp_integer_type SignType1 = (boost::multiprecision::cpp_integer_type)1u; boost::multiprecision::cpp_int_check_type Checked1 = (boost::multiprecision::cpp_int_check_type)0u; Allocator1 = void; typename boost::enable_if_c<(boost::multiprecision::backends::is_trivial_cpp_int<boost::multiprecision::backends::cpp_int_backend<MinBits1, MaxBits1, SignType1, Checked1, Allocator1> >::value && boost::multiprecision::is_signed_number<boost::multiprecision::backends::cpp_int_backend<MinBits1, MaxBits1, SignType1, Checked1, Allocator1> >::value)>::type = void]’: ./boost/multiprecision/number.hpp:585:40: required from ‘void boost::multiprecision::number<Backend, ExpressionTemplates>::convert_to_imp(T*) const [with T = boost::multiprecision::number<boost::multiprecision::backends::cpp_bin_float<113u, (boost::multiprecision::backends::digit_base_type)2u, void, short int, -16382, 16383>, (boost::multiprecision::expression_template_option)0u>; Backend = boost::multiprecision::backends::cpp_int_backend<128u, 128u, (boost::multiprecision::cpp_integer_type)1u, (boost::multiprecision::cpp_int_check_type)0u, void>; boost::multiprecision::expression_template_option ExpressionTemplates = (boost::multiprecision::expression_template_option)0u]’ ./boost/multiprecision/number.hpp:601:29: required from ‘T boost::multiprecision::number<Backend, ExpressionTemplates>::convert_to() const [with T = boost::multiprecision::number<boost::multiprecision::backends::cpp_bin_float<113u, (boost::multiprecision::backends::digit_base_type)2u, void, short int, -16382, 16383>, (boost::multiprecision::expression_template_option)0u>; Backend = boost::multiprecision::backends::cpp_int_backend<128u, 128u, (boost::multiprecision::cpp_integer_type)1u, (boost::multiprecision::cpp_int_check_type)0u, void>; boost::multiprecision::expression_template_option ExpressionTemplates = (boost::multiprecision::expression_template_option)0u]’ multiPrecisionTest.cpp:10:54: required from here ./boost/multiprecision/cpp_int/misc.hpp:533:138: error: no type named ‘type’ in ‘struct boost::common_type<boost::multiprecision::number<boost::multiprecision::backends::cpp_bin_float<113u, (boost::multiprecision::backends::digit_base_type)2u, void, short int, -16382, 16383>, (boost::multiprecision::expression_template_option)0u>, __int128 unsigned>’ typedef typename common_type<R, typename cpp_int_backend<MinBits1, MaxBits1, SignType1, Checked1, Allocator1>::local_limb_type>::type common_type; ^

2 17

[Ranges] Range adaptors and range lifetimes
by Álex Puchades 23 Sep '16

23 Sep '16

Hi boost users! I'm having some lifetime issues with range adaptors. It seems boost adaptors (at least, transformed_range) only store iterators from the original range, letting it go out of scope [1]. Unfortunately, this makes boost adaptors not compatible with ranges that return iterators that are only valid while the original range is in scope (ie: any iterator that references the original range). This type of ranges are useful to avoid the fat-iterator problem, as seen here [2]. Is there any reason for the current behaviour? Should I file a bug or has it been discussed before? Thanks for your help [1] https://github.com/boostorg/range/blob/develop/include/boost/range/adaptor/… [2] http://ericniebler.com/2013/11/07/input-iterators-vs-input-ranges/ -- Álex Puchades

1 0

boost coroutine 1.62 b2 deprecation typo
by Jason Mancini 23 Sep '16

23 Sep '16

Just noticing that there's probably a typo in one of the deprecation warnings, as it wants both defined: BOOST_COROUTINE_NO_DEPRECATION_WARNING BOOST_COROUTINES_NO_DEPRECATION_WARNING Jason

1 0

[Parallel BGL] Poor scalability of dijkstra and delta stepping parallel graph algorithms
by Alexander Frolov 21 Sep '16

21 Sep '16

Hi! I am evaluating scalability on various graph algorithms and found that base parallel SSSP algorithms in PBGL does not scale well in my cases. The plots for rmat (scale=20 and 22) are attached. The source code for the benchmark are attached as well. The main issue that makes me think that I'm doing smth wrong is that execution time of delta stepping algorithm is _increasing_ with node number. I tried to check the code but has not found anything suspicious. Can anybody help me with this issue? Best, Alexander

1 0

[Interprocess]: using condition variables with readers-writer lock (named_sharable_mutex)
by Chris Evans 21 Sep '16

21 Sep '16

Hi, I am trying to use condition variables to signify updated data in a managed_shared_memory segment. I have one "writer" and multiple "readers" of the shared state, so I am using a readers-writer lock as follows: using SharedMutex = bi::named_sharable_mutex; using ReadLock = bi::sharable_lock<SharedMutex>; using WriteLock = bi::scoped_lock<SharedMutex>; using NewEntryCondition = bi::named_condition_any; // With a "writer" block as follows: { WriteLock w_lock( sh_mut_ ); // Update the shared memory object sh_cond_.notify_all(); } // And a "reader" block as follows (many processes call the following simultaneously): { ReadLock r_lock( sh_mut_ ); sh_cond_.wait( r_lock, []() { std::cout << "checking predicate..." << std::endl; // predicate logic goes here... }); // Access object in shared memory here } Unfortunately, although the code compiles, the reader processes are never awakened from wait() and block forever. According to the following thread from 2011: http://lists.boost.org/boost-users/2011/02/66053.php "POSIX does not support condition variables with read-write locks (although I think Windows Vista does) so Interprocess does not offer any support for this." At the time, it appears named_condition_any didn't yet exist. Has the status of this changed in the last 5 years? Is there a suggested way of implementing readers-writer locks with condition variables using boost::interprocess? Thanks! -- Chris Evans Systems Engineer Azure Summit Technology, Inc. 3050 Chain Bridge Road, Suite 600 Fairfax, VA 22030

2 2

[compute] extending meta_kernel functionality
by Oswin Krause 20 Sep '16

20 Sep '16

Hi, I am trying to use boost.compute to extend my linear algebra library to GPUs. so far it helped me a lot with vectors as i can directly use the iterator interface. Matrices are harder. for matrices i need to overload the operator matrix(i,j)-> return the element (i,j). For this i have to return an expression which then offers operator<< with meta_kernel, for example template<class T, class IndexExpr1, class IndexExpr2> inline meta_kernel& operator<<(boost::compute::detail::meta_kernel &kernel, const matrix_element_expr<T, IndexExpr1, IndexExpr2> &expr) { return kernel << kernel.get_buffer_identifier<T>(expr.m_buffer, expr.m_address_space) << '[' << expr.m_expr1 <<"*" <<expr.m_stride1<<"+"<<expr.m_expr2<< "*"<<expr.m_stride2 << ']'; } Unfortunately all of this is in namespace boost::compute::detail, making it a no-go area. Therefore two questions: 1. How stable is i?/can meta_kernel be moved into a normal namespace? 2. Is there a different way to achieve this? (Note that the code above is only an example. I could hack it in this case using the return type of buffer_iterator but not in all cases unfortunately...)

1 0

boost::context "main" stack
by Michael Steinberg 20 Sep '16

20 Sep '16

Hello, is there some way to temporarily run a function on the main stack? I played around a bit, but failed ultimately since the first stub function to be called is getting a "null" context which I assume to be only a valid "return-context". We're facing a problem where a dialog run modally inside a context runs webkit, which triggers garbage collection, which fails miserably since it assumes we're on the "native" stack. If it were possible to run something "on-top" of the main stack, this could maybe be circumvented. Thank you, Michael

2 2