- Boost - lists.preview.boost.org

[release] 1.71.0 closed for Beta
by Michael Caisse 19 Jul '19

19 Jul '19

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

5 8

Any sample code to configure boost log for syslog?
by JH 18 Jul '19

18 Jul '19

Hi, I am using boost log to write log file in the disk of the desktop, but for an embedded system application where the NAND flash is used, to prolong the flash service life time, I try not to write log files in flash, but use journalctl to view the log in RAM. Are there any simple example to configure boost log for syslog? Thank you. - jh

2 2

Something off my chest about Boost
by Maarten Verhage 18 Jul '19

18 Jul '19

Dear Boost people, Sorry but I need to get something off my chest regarding the Boost culture. To start of with something nice: I’m convinced Boost provides really useful facilities for C++ and some of them even make it into the standard C++ library. I do believe I can also contribute in a reasonable way. But the terse documentation keeps me from advancing. How it is currently stated on https://www.boost.org/users/faq.html “What about documentation? A very simple library might be accepted with only a well commented header file. For more substantial libraries, some form of documentation is certainly going to be expected. HTML is the preferred form.” To make Boost more accessible to people I believe Boost should ask more on this from current and new library authors. Speaking for myself. I think the first bits to get started with a library are on a sufficient level. You know the tutorial and the example code. But I get lost when I want to use the library for my own application domain. Then I do need library facilities not covered in the example code and sometimes the documentation mentions only the syntax. As I would imagine the library author working on his/her library judging whether to add a facility or not. Finally decided to add something: *the thought/motivation that goes along with that*, that would be so valuable for me to read that in the documentation!! Yes, I’m annoyed that I cannot read that in the documentation. Another issue is when example code introduces three or more facilities at once. Then it is very hard for me to see how these bits relate to each other to make it useful for myself. Ok, a few examples for what I would like to ask the Boost community to demand from the library authors: 1) In general, for the classes/functions where the user should directly deal with documentation like cppreference.com. So, with function prototypes showing the argument- and return types and a complete list of members along with what they do. 2) Specifically for Spirit X3, a part on Parser Directives: https://www.boost.org/doc/libs/develop/libs/spirit/doc/x3/html/spirit_x3/qu… I would very much like that the reason why each directive is added along with a minimal example that shows how to use just that directive. Anyway, I hope people are also interested to discus documentation policies on this mailing list. I do believe it is important. Best regards, Maarten Verhage

10 17

ASIO socket termination crashed at boost::asio::async_read
by JH 17 Jul '19

17 Jul '19

Hi, I use boost TCP socket for months, it works well until I call a termination of smart pointer which is running at boost::asio::async_read. Could anyone explain what could be the cause for the following errors? void Comms::HandleReadBody(const boost::system::error_code &error, const uint32_t length) { ................ boost::asio::async_read(this->mHandler->Socket(), boost::asio::buffer(this->mHeader, sizeof(this->mHeader)), [=](const boost::system::error_code &status, const uint32_t length) {this->HandleReadHeader(status, length);}); ............... } (gdb) run 2019-07-15 11:47:32.396184: Sanity check socket connection and terminate it when it is inactive ............. pure virtual method called terminate called without an active exception Program received signal SIGABRT, Aborted. (gdb) backtrace #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00007ffff7a24801 in __GI_abort () at abort.c:79 #2 0x00007ffff5565957 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #3 0x00007ffff556bab6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x00007ffff556baf1 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x00007ffff556c8bf in __cxa_pure_virtual () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #6 HandleReadHeader(boost::system::error_code const&, unsigned int) () #7 0x00007ffff679a116 in boost::asio::detail::read_op<boost::asio::ssl::stream<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > >, boost::asio::mutable_buffers_1, boost::asio::detail::transfer_all_t, HandleReadBody(boost::system::error_code const&, unsigned int)::{lambda(boost::system::error_code const&, unsigned int)#1}>::operator()(boost::system::error_code const&, unsigned long, int) () #8 0x00007ffff6799c20 in boost::asio::ssl::detail::io_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> >, boost::asio::ssl::detail::read_op<boost::asio::mutable_buffers_1>, boost::asio::detail::read_op<boost::asio::ssl::stream<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > >, boost::asio::mutable_buffers_1, boost::asio::detail::transfer_all_t, HandleReadBody(boost::system::error_code const&, unsigned int)::{lambda(boost::system::error_code c---Type <return> to continue, or q <return> to quit--- onst&, unsigned int)#1}> >::operator()(boost::system::error_code, unsigned long, int) () #9 0x00007ffff679b547 in boost::asio::detail::reactive_socket_recv_op<boost::asio::mutable_buffers_1, boost::asio::ssl::detail::io_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> >, boost::asio::ssl::detail::read_op<boost::asio::mutable_buffers_1>, boost::asio::detail::read_op<boost::asio::ssl::stream<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > >, boost::asio::mutable_buffers_1, boost::asio::detail::transfer_all_t, HandleReadBody(boost::system::error_code const&, unsigned int)::{lambda(boost::system::error_code const&, unsigned int)#1}> > >::do_complete(boost::asio::detail::task_io_service*, boost::asio::detail::task_io_service_operation*, boost::system::error_code const&, unsigned long) () #10 0x000055555559f5c0 in boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock<boost::asio::detail::posix_mutex>&, boost::asio::detail::task_io_service_thread_info&, boost::system::error_code const&) () #11 0x000055555559f747 in boost::asio::detail::task_io_service::run(boost::system::error_code&) ()

4 5

Useful Release Notes
by James E. King III 13 Jul '19

13 Jul '19

I'd suggest we make sure our release notes are useful to end users; I found some examples that are in the 1.71 that are not useful when reading the notes: * [phrase library..[(a)/libs/flyweight/index.html Flyweight]:] * Maintenance work. * [phrase library..[@/libs/poly_collection/ PolyCollection]:] * Maintenance work. Thanks, Jim

2 1

meeting today
by Robert Ramey 12 Jul '19

12 Jul '19

I was impressed with your presentation today. you can find current renderings at this link: https://we.tl/t-TDoBHgw9AF Robert Ramey

1 1

The out_ptr review is now over
by Zach Laine 11 Jul '19

11 Jul '19

Thanks to all that participated. A review result with be posted sometime in the next couple of weeks (the upcoming C++ standards meeting next week will delay it a bit). Zach

1 0

Failed reconnection
by JH 11 Jul '19

11 Jul '19

Sorry for keeping posting questions about ASIO TCP socket reconnection regarding to network interface changes, I am very much stuck at the moment. As I described in other emails, when one network interface WiFi failed, the network interface Ethernet takes over, the client application using boost ASIO TCP socket cannot detect the broken of WiFi, it continually sent messages to the remote server via the broken WiFi interface without triggering errors but obviously the server could not receive messages any more. So my solution is prior to send message, it ping to 8.8.8.8 via the network interface WiFi, if it failed, it called the SetConnection again to close the socket binding to WiFi interface and to start reconnection to bind to Ethernet interface: void SetConnection(void) { if (this->mSocket.lowest_layer().is_open()) { std::cout << "Set connection close socket" << std::endl; this->mSocket.lowest_layer().close(); } boost::asio::ip::tcp::resolver resolver(this->mIoService); boost::asio::ip::tcp::resolver::query query(this->mHost, this->mPort); this->mIterator = resolver.resolve(query); this->mContext.load_verify_file("ssl/ca.pem"); this->mSocket.set_verify_mode(boost::asio::ssl::verify_peer); this->mSocket.set_verify_callback(boost::bind(&client::verify_certificate, this, _1, _2)); boost::asio::async_connect(mSocket.lowest_layer(), this->mIterator, boost::bind(&client::handle_connect, this, boost::asio::placeholders::error)); } But it did not work, the error: handle_connect connect failed: Network is unreachable What I am missing here? How can I make the TCP socket reconnection? Thank you. Kind regards, - jupiter

2 3

Link problem with graph and pending still appears unresolved?
by pbristow＠hetp.u-net.com 10 Jul '19

10 Jul '19

I have been bitten by this problem, again ☹ error: Cannot create link boost\pending\detail\disjoint_sets.hpp to libs\graph\include\boost\pending\detail\disjoint_sets.hpp. error: Link previously defined to another file, libs\disjoint_sets\include\boost\pending\detail\disjoint_sets.hpp. that was discussed https://lists.boost.org/Archives/boost/2019/04/246083.php I have got going again by deleting the contents of boost/boost/ containing the symlinks. But I note that a folder pending still exists, but not graph. Is this unresolved? Should it be fixed for the next release? Paul Paul A. Bristow Prizet Farmhouse Kendal, Cumbria LA8 8AB UK

5 14

[releaase] 1.71.0 closed for major changes
by Marshall Clow 09 Jul '19

09 Jul '19

The master branch is now closed for new libraries and breaking changes, and will be closing for the beta in one week. Also, if you're ready, you can also add your libraries' changes to the release notes at: < https://github.com/boostorg/website/blob/master/feed/history/boost_1_71_0.q… > After editing the release notes, you should get a form to create a pull request, remember to submit it, otherwise I won't see your change. As always, the calendar for the release cycle is available at: https://www.boost.org/development/ Thanks, -- The Boost Release Team

3 2