August 2019 - Boost - lists.boost.org

Expansion of Boost.Algorithm
by ATHARVA VEER 06 Aug '19

06 Aug '19

Greetings to all! I am planning to expand Boost.Algorithm by including more of general purpose algorithms to it. But since I don't know the future roadmap of the module, I cannot suggest changes right now. Also I have couple of algorithms in my mind that I think would be great if they are part of Boost but I don't know if Boost.Algorithm is the right place to include them. So I was wondering if anyone is willing to mentor me (as in review my work and suggest changes before merging) and we could discuss what we could include in Boost.Algorithm or appropriate module to include them. Brief about myself:- I am junior year college student and I have some experience working in open-source. I haven't contributed to Boost before but have used Boost libraries in day to day life. Thank you!!

1 0

Boost 1.71.0 Beta 1 and Quantlib 1.15
by Cg K 06 Aug '19

06 Aug '19

Gentlemen, Please read this message from Quantlib Dev board <https://sourceforge.net/p/quantlib/mailman/message/36730686/> In short, I was not able to compile Quantlib 1.15 with Boost 1_71_0_b1_rc1 I was able to compile it with 1.70 with some creativity. See here. <https://sourceforge.net/p/quantlib/mailman/message/36732240/> I have a complete list of the errors and messages. It is some 36 pages long and thought it best not to attach. If anyone wants it I will gladly send it to them privately. kaucher(a)gmail.com

4 5

[quickbook] build errors on master
by Raffi Enficiaud 05 Aug '19

05 Aug '19

Hi, I just merged develop to master and I have quickbook errors on my CI (see errors below). The exact same code compiled at 27. July 2019 at 13:47:19 CEST. Does anyone know something about this? Thanks, Raffi 05-Aug-2019 21:44:37 /Users/bambooagent/bamboo-agent-home/xml-data/build-dir/RS-BCB-DOX/library/tools/quickbook/src/include_paths.cpp:160:18: error: no member named 'directory_iterator' in namespace 'boost::filesystem'; did you mean 'directory_entry'? 05-Aug-2019 21:44:37 for (fs::directory_iterator dir_i(base_dir), dir_e; dir_i != dir_e; 05-Aug-2019 21:44:37 ~~~~^ 05-Aug-2019 21:44:37 ../../../boost/filesystem/path_traits.hpp:48:9: note: 'directory_entry' declared here 05-Aug-2019 21:44:37 class directory_entry; 05-Aug-2019 21:44:37 ^ 05-Aug-2019 21:44:37 /Users/bambooagent/bamboo-agent-home/xml-data/build-dir/RS-BCB-DOX/library/tools/quickbook/src/include_paths.cpp:160:61: error: use of undeclared identifier 'dir_i' 05-Aug-2019 21:44:37 for (fs::directory_iterator dir_i(base_dir), dir_e; dir_i != dir_e; 05-Aug-2019 21:44:37 ^ 05-Aug-2019 21:44:37 /Users/bambooagent/bamboo-agent-home/xml-data/build-dir/RS-BCB-DOX/library/tools/quickbook/src/include_paths.cpp:160:70: error: use of undeclared identifier 'dir_e' 05-Aug-2019 21:44:37 for (fs::directory_iterator dir_i(base_dir), dir_e; dir_i != dir_e; 05-Aug-2019 21:44:37 ^ 05-Aug-2019 21:44:37 /Users/bambooagent/bamboo-agent-home/xml-data/build-dir/RS-BCB-DOX/library/tools/quickbook/src/include_paths.cpp:161:16: error: use of undeclared identifier 'dir_i' 05-Aug-2019 21:44:37 ++dir_i) { 05-Aug-2019 21:44:37 ^ 05-Aug-2019 21:44:37 /Users/bambooagent/bamboo-agent-home/xml-data/build-dir/RS-BCB-DOX/library/tools/quickbook/src/include_paths.cpp:162:26: error: use of undeclared identifier 'dir_i' 05-Aug-2019 21:44:37 fs::path f = dir_i->path().filename(); 05-Aug-2019 21:44:37 ^ 05-Aug-2019 21:44:37 /Users/bambooagent/bamboo-agent-home/xml-data/build-dir/RS-BCB-DOX/library/tools/quickbook/src/include_paths.cpp:170:41: error: use of undeclared identifier 'dir_i' 05-Aug-2019 21:44:37 if (fs::is_regular_file(dir_i->status())) { 05-Aug-2019 21:44:37 ^ 05-Aug-2019 21:44:37 /Users/bambooagent/bamboo-agent-home/xml-data/build-dir/RS-BCB-DOX/library/tools/quickbook/src/include_paths.cpp:178:42: error: use of undeclared identifier 'dir_i' 05-Aug-2019 21:44:37 if (!fs::is_regular_file(dir_i->status())) { 05-Aug-2019 21:44:37 ^ 05-Aug-2019 21:44:37 7 errors generated.

2 1

[release] 1.71.0 post-beta merges
by Michael Caisse 05 Aug '19

05 Aug '19

The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/boost/wiki/Releases%3A-Beta-Merge-Policy> Thanks, -- The Boost Release Team

7 17

Expansion of Boost.Algorithm
by ATHARVA VEER 04 Aug '19

04 Aug '19

Greetings to all! I am planning to expand Boost.Algorithm by including more of general purpose algorithms to it. But since I don't know the future roadmap of the module, I cannot suggest changes right now. Also I have couple of algorithms in my mind that I think would be great if they are part of Boost but I don't know if Boost.Algorithm is the right place to include them. So *I was wondering if anyone is willing to mentor me (as in review my work and suggest changes before merging) and we could discuss what we could include in Boost.Algorithm.* Brief about myself:- I am junior year college student and I have some experience working in open-source. I haven't contributed to Boost before but have used Boost libraries in day to day life.

1 0

Boost.Accumulators regression in Boost 1.71 beta 1 on VC++17/19
by Luigi Ballabio 04 Aug '19

04 Aug '19

Hello, the attached minimal file fails to compile on VC++17/19 when using Boost 1.71.0b1. It compiles successfully with Boost 1.70.0. I also attach the compiler errors. Cheers, Luigi

1 1

ASIO socket wired observation
by JH 03 Aug '19

03 Aug '19

Hi, I have been using asio tcp socket on desktop Ubuntu for years, but I have never seriously run interface connections in a LTE embedded system, here is what I have observed wired thing: - Client initialized TCP socket connection to remote server, the connection was established. - Client sent data to server via Internet every one minute, all good. - Somehow, the LTE connection dropped, there was no any network connection available, but the client keep sent messages, there was no error about the network connection, the message obvious could not go Internet, it accumulated in the RAM, the original each message size was 79 bytes, the size was accumulated became 52790 bytes, it kept going for ever until I terminate the client program. ....... Send message size: 52790 Send message size: 52869 Send message size: 52948 ..... Is it normal behavior of ASIO socket or what I did wrong here? Appreciate your insight tips to fix this problem to trig client socket error not keeping sending message going no way. Thank you. Kind regards, - jupiter

2 1

How safer to use boos::shared_from_this() from derived class inherited from based class?
by JH 02 Aug '19

02 Aug '19

Hi, I have a derived base class: class Base : boost::enable_shared_from_this<Base> { public: Base(); virtual ~Base(); virtual boost::shared_ptr<Base> SharedFromThis(void) {return shared_from_this();} private: } class Derived : public Base { public: Derived(); ~Derived(); // boost::shared_ptr<Derived> SharedFromThis(void) {return boost::static_pointer_cast<Derived>(shared_from_this());} private: }; Applications are sharing the derived class, it can either use shared_ptr<Derived> or shared_ptr<Base> by calling the SharedFromThis(), three options: (1) Don't define derived class own SharedFromThis(), always call Base SharedFromThis() to pass shared_ptr<Base> as Derived shared_ptr, the reference count will be shared_ptr<Base>. (2) Define derived class its own SharedFromThis() and pass shared_ptr<Derived> to applications: boost::shared_ptr<Derived> SharedFromThis(void) {return boost::static_pointer_cast<Derived>(shared_from_this());} That one cannot be virtual as conflicted to Base SharedFromThis(), the reference count will always be boost::shared_ptr<Derived> (3) Mixed both boost::shared_ptr<Derived> and boost::shared_ptr<Base> in applications, that could be a bad option to cause segmentation as one shared_ptr could be ended before another shared_ptr. Which option will be safer? Thank you. Kind regards, - jupiter

2 2

Norton blocking Appveyor?
by John Maddock 01 Aug '19

01 Aug '19

Hi all, I see that my browser is just started blocking ci.appveyor.com which is a bit of a problem for CI to say the least. Is anyone else seeing this? Any ideas whether it's justified or spurious? Thanks, John. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

3 2