- Boost-users - lists.boost.org

Re: [Boost-users] <boost/timer/timer.hpp> deprecated ?
by Kenneth Porter 23 Sep '19

23 Sep '19

--On Friday, September 13, 2019 3:35 PM +0100 "avib369 . via Boost-users" <boost-users(a)lists.boost.org> wrote: > How do I get rid of this message ? You could do what it says to do?

2 1

Community blog or tutorial posting for C++
by Matt Zand 22 Sep '19

22 Sep '19

Hi, Does anyone know if there is a way for members to post blogs or tutorials on C++ in the Boost community or website? -- Cheers, Matt Zand Cell: 202-420-9192 Work: 240-200-6131 High School Technology Services <https://myhsts.org/> DC Web Makers <https://dcwebmakers.com/> Coding Bootcamps <https://coding-bootcamps.com/>

4 4

<boost/timer/timer.hpp> deprecated ?
by avib369 . 13 Sep '19

13 Sep '19

How do I get rid of this message ? /tmp/ma0/boost/gcc-7.3/boost_1_71_0/boost/timer.hpp:21:70: note: #pragma message: This header is deprecated. Use the facilities in <boost/timer/timer.hpp> instead. BOOST_HEADER_DEPRECATED( "the facilities in <boost/timer/timer.hpp>" ) Ta, Avi

1 0

boost.asio: win_iocp_serial_port_service::open changes broke FTDI support
by Michael Steinberg 12 Sep '19

12 Sep '19

Hello, the changes to win_iocp_serial_port_service::open in commit c113adc19004770d945672009b3d26f9498099cd broke at least FTDI 4232H but probably all FTDI support for me. SetCommState(handle, &dcb) in new line 99 fails with error code 57. Reverting the commit seems to recover correct behaviour. Kind Regards Michael

1 0

Building Boost with C++17 standard
by Osman Zakir 12 Sep '19

12 Sep '19

Okay, so how do I build Boost under the C++17 standard? There's something I need to do in the configuration file, right?

4 4

Compile error using property_tree
by Rui Pedro 11 Sep '19

11 Sep '19

Hello guys, I wanted to use boost to parse an INI file. in my code i used this includes: #include "boost/property_tree/ptree.hpp" #include "boost/property_tree/ini_parser.hpp" when I compile my code "g++ test.cpp -o Test" with only this two includes I get an error from one of the included files: In file included from test.cpp:15:0: boost/property_tree/ptree.hpp:15:45: fatal error: boost/property_tree/ptree_fwd.hpp: File or directory not found #include <boost/property_tree/ptree_fwd.hpp> ^ compilation terminated. This is an error in the ptree.hpp imported file. Maybe this has a quick fix but I'm kinda new to C++. I've checked and both files exist (boost/property_tree/ptree and boost/property_tree/ptree_fwd.hpp). Thanks, Rui

3 3

[asio] using fork in coroutine composed operations
by Stephan Menzel 11 Sep '19

11 Sep '19

Hello all, my experiments with custom composed operations in asio have led me to another question regarding the use of such methods. What do I do in order to have multiple handlers in flight, e.g. for a timer? My example is here: https://github.com/MrMoose/moose_tools/blob/master/TimedConnect.hpp I'm trying to realize an old dream in asio. A function that will take a socket and asynchronously do a resolve and connect to the result while having a timeout around the operation. Here in the test cases (lower part) is how I imagine usage: https://github.com/MrMoose/moose_tools/blob/master/test/TestAsioHelpers.cpp… This works (the unit test does...) but I think it's no good and illustrate the problem. In the coroutine impl I can safely jump in and out and resume the code represented by the coroutine object as was explained to me yesterday. But what can I do with the timer? I cannot std::move(self) into it because it gets moved again moments later and I cannot yield on the timer wait operation. I want the timer handler and the async ops handlers both be in flight and have called whichever completes first. I tried coroutine fork thinking it might be the right tool but that seems to clash with the move-self-ahead pattern which is used here. If I don't yield and set the timer to a fixed lambda (as in the example above) it seems to work but I guess that's not how it's supposed to be, right? Any hints as to how I can make this better? Cheers, Stephan

4 12

Program Options MacOS Error
by Michael Chiu 10 Sep '19

10 Sep '19

Hi All, I was trying to use boost program options to capture a std::string like the examples in the documentation. However I keep getting the error: libc++abi.dylib: terminating with uncaught exception of type boost::wrapexcept<boost::bad_any_cast> when i try to retrieve the value from the valuemap, i.e. vm["source"].as<std::string>(); The code that I have (which right now is essentially the tutorial example) runs fine on linux but has the above error on macos. Am i doing something wrong or is this a genuine platform specific bug? Sincerely, --Michael

1 0

Re: [Boost-users] xlcpp: use of undeclared identifier 'decltype' used in boost/thread/lockable_traits.hpp
by Roy Musselman 10 Sep '19

10 Sep '19

Greetings, While attempting to build boost 1.70.0 for IBM Power9 using the IBM XL compilers using the SPACK tool, the following errors occur repeatedly for every header file that eventually includes boost/thread/lockable_traits.hpp In file included from ./boost/thread/lock_types.hpp:14: ./boost/thread/lockable_traits.hpp:157:11: error: use of undeclared identifier 'decltype' decltype(void(boost::declval<T&>().lock())) ^ ./boost/thread/lockable_traits.hpp:165:11: error: use of undeclared identifier 'decltype' decltype(void(boost::declval<T&>().unlock())) ^ ./boost/thread/lockable_traits.hpp:173:11: error: use of undeclared identifier 'decltype' decltype(bool(boost::declval<T&>().try_lock())) ^ These errors could be resolved if the -std=c++11 compiler option is used. Attempting to use SPACK options cxxflags=-std=c++11 or cxxstd=11 failed as if they were ignored. I was able to work-around this pervasive error by adding the following line to the file tools/build/src/tools/xlcpp.jam flags xlcpp.compile.c++ OPTIONS <cxxstd>11 : -std=c++11 ; Can you update the xlcpp.jam file to support the cxxstd=11 option, similar to what is implemented in pgi.jam? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Roy Musselman IBM HPC Application Analyst at Lawrence Livermore National Lab email: roymuss(a)us.ibm.com

2 3

[asio] writing composed operations example
by Stephan Menzel 03 Sep '19

03 Sep '19

Hi everyone, as a long time asio user I often had needs to wrap up repeating patterns of async calls for re-use. Normally I went for some kind of specialized object that wraps smaller pieces but I recently came across a series of examples which try to explain how own composed operations may be created. https://www.boost.org/doc/libs/1_71_0/doc/html/boost_asio/examples/cpp11_ex… Now, looking at the examples they are of course way over my head but since own composed operations would be very much exactly what I need I thought I'd give it a shot. But as I now look at this example here: https://www.boost.org/doc/libs/1_71_0/doc/html/boost_asio/example/cpp11/ope… I notice something that I hope somebody can explain. In the coroutine implementation it says: delay_timer_->expires_after(std::chrono::seconds(1)); yield delay_timer_->async_wait(std::move(self)); if (error) break; yield boost::asio::async_write(socket_, boost::asio::buffer(*encoded_message_), std::move(self)); I'm puzzled about the double std::move() of self. In the comments above it says that self is a reference to an intermediate completion handler. How can this be moved twice? Can anyone give me hint about what this means? I would also appreciate any hints in general about own composed operations. Perhaps there are other approaches that are a bit less intimidating? Cheers, Stephan

3 3