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

[Boost.Python] C++/Python Hybrid App in 2020
by Andrew McFarlane 22 Feb '20

22 Feb '20

Hi all, I read on the Boost.Python FAQ that for Mac OSX users, the library is currently known only to work with the GCC compiler. Thus far, I have been using clang++. I will make the switch, so long that it does increase my odds of encountering difficulties down the road. What do we think here? In the context of front-end dev in Python for a C++ application, is Boost.Python worth making the switch from clang++ to gcc? Would I be better off using something else (i.e. wxPython)? I really love using Boost (I've found use for Test, Signals2, and Asio), but I don't want to let my Boost bias lead me to make a poor choice. I know this question is a tad subjective; I apologize for that. I would like the Python extension to be as seamless as possible, and I am only going to be using Python for front-end code. The interface between the two would likely be with sockets. I am sure I could answer this myself via experimentation, but I wanted to get a feel from the Boost community before doing so. Thanks in advance! *- AJ*

2 2

Newbie Question Shared Memory Containers/Allocators
by Da Xu 14 Feb '20

14 Feb '20

Hi everybody, how are you? I am a completely noob when it comes to Boost. :D But not a noob when it comes to C++. Though, am a bit noobish when it comes to C++14 and beyond :D I am trying to construct a complex data container, which has a vector of floats, on managed shared memory. I followed the documentation, added the appropriate headers and made the following declarations: typedef managed_windows_shared_memory::segment_manager segment_manager_t; typedef allocator<void, segment_manager_t> void_allocator; typedef basic_string<char, std::char_traits<char>, char_allocator> shared_string; typedef allocator<float, segment_manager_t> float_allocator; typedef vector<float, float_allocator> float_vector; typedef allocator<float_vector, segment_manager_t> float_vector_allocator; class ComplexContainer {shared_string name;float_vector channelData; public:ComplexContainer(const char * name_, const float* data_start, const float* data_end, const void_allocator& void_alloc) : name(name_), channelData(data_start, data_end, void_alloc) {} ComplexContainer(const void_allocator& void_alloc) : name(void_alloc), channelData(void_alloc){} ComplexContainer() {} } but I am getting these errors at compile: 1>D:\Libraries\boost_1_72_0\boost\container\vector.hpp(310,23): error C2512: 'boost::interprocess::allocator<float,segment_manager_t>::allocator': no appropriate default constructor available1>D:\Libraries\boost_1_72_0\boost\container\vector.hpp(308): message : while compiling class template member function 'boost::container::vector_alloc_holder<boost::interprocess::allocator<float,segment_manager_t>,unsigned __int64,boost::move_detail::integral_constant<unsigned int,2>>::vector_alloc_holder(void) noexcept(false)'1>D:\Libraries\boost_1_72_0\boost\container\vector.hpp(832): message : see reference to function template instantiation 'boost::container::vector_alloc_holder<boost::interprocess::allocator<float,segment_manager_t>,unsigned __int64,boost::move_detail::integral_constant<unsigned int,2>>::vector_alloc_holder(void) noexcept(false)' being compiled1>D:\Libraries\boost_1_72_0\boost\container\vector.hpp(779): message : see reference to class template instantiation 'boost::container::vector_alloc_holder<boost::interprocess::allocator<float,segment_manager_t>,unsigned __int64,boost::move_detail::integral_constant<unsigned int,2>>' being compiled message : see reference to class template instantiation 'boost::container::vector<float,float_allocator,void>' being compiled That doesn't make a whole lot of sense, since it seems to be referring to the "float_allocator" typedef. But float is not an object, it has no constructor. Any help would be greatly appreciated! Thank you! Da.

2 1

Re: [Boost-users] boost float128 and Intel's _Quad with Tux Eigen
by Alex.Durie 04 Feb '20

04 Feb '20

Thanks John, >The good news is that Intel on Linux does support GCC's __float128 type, >so my suggestion would be to: >* Remove the #define BOOST_MP_USE_QUAD >* Build with -std=gnu++14 rather than -std=c++14 >* Remove the -Qoption,cpp,--extended_float_type option. Unfortunately that didn't work, I get the new compiler error; /home/alex/boost/boost_1_71_0/boost/multiprecision/detail/number_base.hpp(216): error: static assertion failed with "is_integral<T>::value || is_enum<T>::value || std::numeric_limits<T>::is_specialized" BOOST_STATIC_ASSERT(is_integral<T>::value || is_enum<T>::value || std::numeric_limits<T>::is_specialized); Are you able to help? Many thanks, Alex ________________________________ From: Boost-users <boost-users-bounces(a)lists.boost.org> on behalf of boost-users-request(a)lists.boost.org <boost-users-request(a)lists.boost.org> Sent: 04 February 2020 10:56 To: boost-users(a)lists.boost.org <boost-users(a)lists.boost.org> Subject: Boost-users Digest, Vol 5318, Issue 1 CAUTION: This mail comes from outside the University. Please consider this before opening attachments, clicking links, or acting on the content. Send Boost-users mailing list submissions to boost-users(a)lists.boost.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.boost.org/mailman/listinfo.cgi/boost-users or, via email, send a message with subject or body 'help' to boost-users-request(a)lists.boost.org You can reach the person managing the list at boost-users-owner(a)lists.boost.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Boost-users digest..." Today's Topics: 1. boost float128 and Intel's _Quad with Tux Eigen (Alex.Durie) 2. [boost build] - How to create symbols (.pdb) files on windows using VS2017 Community Edition? (Eko palypse) 3. Re: [boost build] - How to create symbols (.pdb) files on windows using VS2017 Community Edition? (Mateusz Loskot) 4. Re: [boost build] - How to create symbols (.pdb) files on windows using VS2017 Community Edition? (Eko palypse) 5. Re: boost float128 and Intel's _Quad with Tux Eigen (John Maddock) ---------------------------------------------------------------------- Message: 1 Date: Mon, 3 Feb 2020 21:33:13 +0000 From: Alex.Durie <alex.durie(a)open.ac.uk> To: "boost-users(a)lists.boost.org" <boost-users(a)lists.boost.org> Subject: [Boost-users] boost float128 and Intel's _Quad with Tux Eigen Message-ID: <CWLP265MB0244A9FE67071B7EE7C7E2BFA3000(a)CWLP265MB0244.GBRP265.PROD.OUTLOOK.COM> Content-Type: text/plain; charset="iso-8859-1" Hi, I have written a short program utilising boost::float128 together with tux Eigen which successfully compiles and runs using g++, however it fails when I use icc. The compiler error is /home/alex/boost/boost_1_71_0/boost/multiprecision/float128.hpp(727): error: no suitable constructor exists to convert from "const _Quad" to "boost::multiprecision::number<boost::multiprecision::backends::float128_backend, boost::multiprecision::et_off>" static number_type (min)() BOOST_NOEXCEPT { return BOOST_MP_QUAD_MIN; } ^ How can I resolve this? My example code is; #include <iostream> #include <cmath> #include <Eigen/Dense> #include <Eigen/Eigenvalues> #include <iomanip> #include <boost/cstdfloat.hpp> #include <boost/multiprecision/float128.hpp> #include <boost/math/special_functions.hpp> #include <boost/math/constants/constants.hpp> #include <quadmath.h> #define BOOST_MP_USE_QUAD using namespace Eigen; using namespace std; int main(){ typedef Matrix<complex<boost::multiprecision::float128>, Dynamic, Dynamic> MatrixXcmp; MatrixXcmp C = MatrixXcmp::Random(8,8); cout<<setprecision(128)<<C<<endl<<endl; ComplexEigenSolver<MatrixXcmp> ces; ces.compute(C); return 0; } It only fails compilation when I put in the line 'ces.compute(C);'. I compile with icpc quadtest.cpp -std=c++14 -Qoption,cpp,--extended_float_type -O2 -DMKL_LP64 -lmkl_intel_lp64 -fp-model precise -lmkl_sequential -lmkl_core -lpthread -lm -ldl -lquadmath Many thanks in advance, Alex

2 2

boost float128 and Intel's _Quad with Tux Eigen
by Alex.Durie 04 Feb '20

04 Feb '20

Hi, I have written a short program utilising boost::float128 together with tux Eigen which successfully compiles and runs using g++, however it fails when I use icc. The compiler error is /home/alex/boost/boost_1_71_0/boost/multiprecision/float128.hpp(727): error: no suitable constructor exists to convert from "const _Quad" to "boost::multiprecision::number<boost::multiprecision::backends::float128_backend, boost::multiprecision::et_off>" static number_type (min)() BOOST_NOEXCEPT { return BOOST_MP_QUAD_MIN; } ^ How can I resolve this? My example code is; #include <iostream> #include <cmath> #include <Eigen/Dense> #include <Eigen/Eigenvalues> #include <iomanip> #include <boost/cstdfloat.hpp> #include <boost/multiprecision/float128.hpp> #include <boost/math/special_functions.hpp> #include <boost/math/constants/constants.hpp> #include <quadmath.h> #define BOOST_MP_USE_QUAD using namespace Eigen; using namespace std; int main(){ typedef Matrix<complex<boost::multiprecision::float128>, Dynamic, Dynamic> MatrixXcmp; MatrixXcmp C = MatrixXcmp::Random(8,8); cout<<setprecision(128)<<C<<endl<<endl; ComplexEigenSolver<MatrixXcmp> ces; ces.compute(C); return 0; } It only fails compilation when I put in the line 'ces.compute(C);'. I compile with icpc quadtest.cpp -std=c++14 -Qoption,cpp,--extended_float_type -O2 -DMKL_LP64 -lmkl_intel_lp64 -fp-model precise -lmkl_sequential -lmkl_core -lpthread -lm -ldl -lquadmath Many thanks in advance, Alex

2 1

[boost build] - How to create symbols (.pdb) files on windows using VS2017 Community Edition?
by Eko palypse 03 Feb '20

03 Feb '20

How can I build pdb files using b2 tool? If I run b2 -a --with-regex toolset=msvc-14.1 debug-symbols=on address-model=64 architecture=ia64 variant=debug it creates the needed lib but no pdb files are created. Thank you Eren

2 2

Re: [Boost-users] Boost-users Digest, Vol 5315, Issue 1
by Andrew McFarlane 31 Jan '20

31 Jan '20

@Gavin @Edward: Success! The program is now executing as expected, *thanks to all of your helpful suggestions.* Here's what I did: 1. added --with-chrono to my b2 command, which placed .a and .dylib files for chrono in stage/lib. 2. after invoking the following compiler command: g++ -v -Wall -L ${BOOST_ROOT}/stage/lib -lboost_chrono -lboost_date_time -lboost_system -lboost_system -I${BOOST_ROOT} -o main main.cpp I added to my RPATH using install_name_tool: sudo install_name_tool -add_rpath ${BOOST_ROOT}/stage/lib main >From what I have read from this article here: https://medium.com/@donblas/fun-with-rpath-otool-and-install-name-tool-e3e4… This command appends to the RPATH (@rpath), which is used by LC_LOAD_DYLIB to locate shared library dependencies for the executable. After executing these two commands, my program runs successfully! *Thank you.* However, the learning never ends. That said, I have a bit of an unrelated follow-up question if that is okay. If not, feel free to shun me and I will look elsewhere for an answer. Running these two commands from my terminal is painful and tedious. For troubleshooting, I don't mind, but I want to move toward automation. 1. I tried putting these two commands into a simple script. When I ran the script, main could not be found. *How would I ensure that the main executable from the g++ invocation is outputted into the cwd before the install_name_tool command is executed?* The script I wrote here is just for the sake of experimentation and learning. Ideally, I would use a build tool (i.e. make) for this sort of thing, which I am actually reading about right now. It should be okay to close this issue after my last question is answered/shunned. Thanks again for all of your helpful suggestions, I am starting to like this community already. - AJ On Fri, Jan 31, 2020 at 4:01 AM <boost-users-request(a)lists.boost.org> wrote: > Send Boost-users mailing list submissions to > boost-users(a)lists.boost.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.boost.org/mailman/listinfo.cgi/boost-users > or, via email, send a message with subject or body 'help' to > boost-users-request(a)lists.boost.org > > You can reach the person managing the list at > boost-users-owner(a)lists.boost.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Boost-users digest..." > > > Today's Topics: > > 1. [Newbie][Interprocess] Placing a boost interprocess vector in > an existing (not managed) shared memory (Gaier, Bjoern) > 2. Re: [Boost.Asio] tutorial #1 code does not compile (g++) > (Andrew McFarlane) > 3. Re: [Boost.Asio] tutorial #1 code does not compile (g++) > (Edward Diener) > 4. Re: [Boost.Asio] tutorial #1 code does not compile (g++) > (Gavin Lambert) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 30 Jan 2020 08:19:02 +0000 > From: "Gaier, Bjoern" <Bjoern.Gaier(a)horiba.com> > To: "boost-users(a)lists.boost.org" <boost-users(a)lists.boost.org> > Subject: [Boost-users] [Newbie][Interprocess] Placing a boost > interprocess vector in an existing (not managed) shared memory > Message-ID: > < > OSAPR01MB3171A3A1ED46336ACEDE2786E2040(a)OSAPR01MB3171.jpnprd01.prod.outlook.com > > > > Content-Type: text/plain; charset="iso-8859-1" > > Hello Boost-Mailing-List, > > I have a question about the boost interprocess library - and I hope I can > explain it correctly. > > I looked at the "Quick guide for the impatient" about the interprocess > library - but I'm not sure if I can use this for our purpose. > The main goal is to insert a STL vector (or different container) in a > predefined portion of an already existing shared memory. The main problem > is, that we cannot use the managed_shared_memory code from boost, because > we rely on a different API to allocate the shared memory between Windows > and other devices. Also the container should be placed at a fixed offset > inside the created shared memory. > > I'm a complete newbie with boost and the interprocess library, that is why > I'm not sure which interface I have to provide for the interprocess vector > to be setup correctly. I hoped I could do something like: > > new (srh_mem_base + offset) boost::interprocess::vector<allocator>; > > I tried looking into the headers of the library to get an idea of that, > but I honestly got lost. > > I'm really sorry if this a stupid or obvious question - and I thank for > any help in advance! > > Kind greetings > Bj?rn > Als GmbH eingetragen im Handelsregister Bad Homburg v.d.H. HRB 9816, > USt.ID-Nr. DE 114 165 789 Gesch?ftsf?hrer: Dr. Hiroshi Nakamura, Dr. Robert > Plank, Markus Bode, Heiko Lampert, Takashi Nagano, Takeshi Fukushima. > Junichi Tajika >

1 0

Re: [Boost-users] [Boost.Asio] tutorial #1 code does not compile (g++)
by Andrew McFarlane 31 Jan '20

31 Jan '20

Okay, so I have made a bit of progress. After building Boost.Asio with: b2 --with-system --with-thread --with-date_time --with-regex --with-serialization stage , and building Boost.Chrono with (replacing bjam with b2): bjam libs/chrono/build The code is now compiling with the following g++ command: g++ -v -Wall -L ${BOOST_ROOT}/stage/lib -L ${BOOST_ROOT}/bin.v2/libs/chrono/build/clang-darwin-11.0/debug/threading-multi/visibility-hidden -lboost_chrono -lboost_date_time -lboost_system -I. -I${BOOST_ROOT} -o main main.cpp However, when I go to run main, the program crashes with the following message: dyld: Library not loaded: @rpath/libboost_chrono.dylib Referenced from: /Users/ajm/Projects/boost-threads/ex1/./main Reason: image not found Abort trap: 6 I suspect that there is something wrong with the Boost.Chrono dynamic library file that was built (probably because of how I built it), but I am not sure what it would be. Any suggestions? Thanks, *Andrew J. E. McFarlane*

3 2

Re: [Boost-users] [Boost.Asio] tutorial #1 code does not compile (g++)
by Andrew McFarlane 29 Jan '20

29 Jan '20

Hi Richard, I suspect you and David are both correct; I need to link boost_chrono. I found here https://www.boost.org/doc/libs/1_72_0/doc/html/chrono/users_guide.html "If BOOST_CHRONO_HEADER_ONLY <https://www.boost.org/doc/libs/1_72_0/doc/html/chrono/reference.html#chrono…> is not defined you need to compile it and build the library before use". This aligns with what you are saying. However, the command it mentions to use, >> bjam libs/chrono/build does not work, even when I am in the boost directory (bjam is not defined). In addition, adding -lboost_chrono or -L{BOOST_ROOT} does not help my case. After reading this article about static and dynamic linked libraries https://medium.com/@dkwok94/the-linking-process-exposed-static-vs-dynamic-l… I suspect I must append the path of boost_chrono to my LD_LIBRARY_PATH variable. Am I correct in this thinking? If so, where the heck is boost_chrono located? I could not find a .a or .so file in libs/chrono/ anywhere. Do I need to build the static/dynamic library myself? Please advise. I apologize for the elementary questions; my compiler and Unix knowledge could be way better, which is something I am working on. Thanks *Andrew J. E. McFarlane* *Cell: (236) 888-1376* On Tue, Jan 28, 2020 at 11:33 PM <boost-users-request(a)lists.boost.org> wrote: > Send Boost-users mailing list submissions to > boost-users(a)lists.boost.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.boost.org/mailman/listinfo.cgi/boost-users > or, via email, send a message with subject or body 'help' to > boost-users-request(a)lists.boost.org > > You can reach the person managing the list at > boost-users-owner(a)lists.boost.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Boost-users digest..." > > > Today's Topics: > > 1. [Boost.Asio] tutorial #1 code does not compile (g++) > (Andrew McFarlane) > 2. Re: [Boost.Asio] tutorial #1 code does not compile (g++) > (Vinnie Falco) > 3. Re: [Boost.Asio] tutorial #1 code does not compile (g++) > (Andrew McFarlane) > 4. Re: [Boost.Asio] tutorial #1 code does not compile (g++) > (Richard Hodges) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 28 Jan 2020 17:14:58 -0800 > From: Andrew McFarlane <andrew.mcfarlane52(a)gmail.com> > To: boost-users(a)lists.boost.org > Subject: [Boost-users] [Boost.Asio] tutorial #1 code does not compile > (g++) > Message-ID: > <CAG90r9SPGR= > wRUykmftmxTM6oUKbTZYoyat_BR9ufaNpQ0g4Rw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi All, > > I am attempting to get acquainted with C++ multithreaded network > programming. I have a background in such topics within Java but considering > how different C++ is, I am starting from ground zero. > > I have copied the code from tutorial #1 into my IDE, Timer.1: Using a timer > synchronously: > > https://www.boost.org/doc/libs/1_72_0/doc/html/boost_asio/tutorial/tuttimer… > (follow > the link for code). > > When I tried to compile this (using g++) with the following command: > > g++ -v -I${BOOST_ROOT} -I. -o main main.cpp > (BOOST_ROOT is where I have boost installed), I get the following output: > > Undefined symbols for architecture x86_64: > > "boost::chrono::steady_clock::now()", referenced from: > > boost::asio::detail::chrono_time_traits<boost::chrono::steady_clock, > boost::asio::wait_traits<boost::chrono::steady_clock> >::now() in > main-c86634.o > > ld: symbol(s) not found for architecture x86_64 > > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > Note this is the non-verbose output (I would rather not post the verbose > output, as I am trying to keep this post short). > > I did some digging of my own on Boost's steady_timer documentation and > tried to follow that style, as you can find here: > > https://www.boost.org/doc/libs/1_72_0/doc/html/boost_asio/reference/steady_… > In other words, I replace the two-parameter boost::asio::steady_timer ctor > call with a single-parameter ctor call in which I pass an io_context, > followed by > t.expires_after(std::chrono::seconds(5)); > > This generated another compiler error, this one to do with 'no viable > conversion'. See here: > > main.cpp:10:21: error: no viable conversion from 'std::chrono::seconds' > (aka > > 'duration<long long>') to 'const > > boost::asio::basic_waitable_timer<boost::chrono::steady_clock, > > boost::asio::wait_traits<boost::chrono::steady_clock>, > > boost::asio::executor>::duration' (aka 'const duration<long long, > > ratio<(1L), (1000000000L)> >') > > t.expires_after(std::chrono::seconds(5)); > Again, there is more output that I have omitted for brevity. If anyone > would like to see the rest of the output, I will gladly supply it. > > The bottom line is I am not sure what the problem is, or why I am having to > debug tutorial code in the first place. This should be relatively simple to > "plug & play", should it not? Does this have to do with my compiler? BTW, I > am running Mac OS X. > > Thanks in advance for the help. > > Sincerely, > > *AJ* >

2 1

[Boost.Asio] tutorial #1 code does not compile (g++)
by Andrew McFarlane 29 Jan '20

29 Jan '20

Hi All, I am attempting to get acquainted with C++ multithreaded network programming. I have a background in such topics within Java but considering how different C++ is, I am starting from ground zero. I have copied the code from tutorial #1 into my IDE, Timer.1: Using a timer synchronously: https://www.boost.org/doc/libs/1_72_0/doc/html/boost_asio/tutorial/tuttimer… (follow the link for code). When I tried to compile this (using g++) with the following command: g++ -v -I${BOOST_ROOT} -I. -o main main.cpp (BOOST_ROOT is where I have boost installed), I get the following output: Undefined symbols for architecture x86_64: "boost::chrono::steady_clock::now()", referenced from: boost::asio::detail::chrono_time_traits<boost::chrono::steady_clock, boost::asio::wait_traits<boost::chrono::steady_clock> >::now() in main-c86634.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) Note this is the non-verbose output (I would rather not post the verbose output, as I am trying to keep this post short). I did some digging of my own on Boost's steady_timer documentation and tried to follow that style, as you can find here: https://www.boost.org/doc/libs/1_72_0/doc/html/boost_asio/reference/steady_… In other words, I replace the two-parameter boost::asio::steady_timer ctor call with a single-parameter ctor call in which I pass an io_context, followed by t.expires_after(std::chrono::seconds(5)); This generated another compiler error, this one to do with 'no viable conversion'. See here: main.cpp:10:21: error: no viable conversion from 'std::chrono::seconds' (aka 'duration<long long>') to 'const boost::asio::basic_waitable_timer<boost::chrono::steady_clock, boost::asio::wait_traits<boost::chrono::steady_clock>, boost::asio::executor>::duration' (aka 'const duration<long long, ratio<(1L), (1000000000L)> >') t.expires_after(std::chrono::seconds(5)); Again, there is more output that I have omitted for brevity. If anyone would like to see the rest of the output, I will gladly supply it. The bottom line is I am not sure what the problem is, or why I am having to debug tutorial code in the first place. This should be relatively simple to "plug & play", should it not? Does this have to do with my compiler? BTW, I am running Mac OS X. Thanks in advance for the help. Sincerely, *AJ*

4 4

[Regex]: Can a possible non-matched group be prevented from being reported?
by Eko palypse 24 Jan '20

24 Jan '20

Hopefully I'm not posting this again. Hello, I'm wrapping boost::regex with cython to be able to call it from python. Assuming a "Hello World" text and a regex (\w+)*. This results in two matches. groups ('Hello', 'Hello') lastindex 1 group:0 Hello start 0 end 5 group:1 Hello start 0 end 5 groups ('', '') lastindex 1 group:0 start 5 end 5 group:1 start -1 end -1 I understand, that there is always the main match in group0 and matches from capturing groups in group1 ... As we see, the second match, the zero-length-width match, reports two groups but the second group returns -1. Is it possible to prevent such matches to be reported beforehand? Or is it needed to iterate over the groups to eliminate those? Just in case it is needed to see my code logic, this is what I'm doing currently def unicode_research_iter(const wchar_t* text, wchar_t* pattern, int flags): cdef: wcmatch what size_t _length size_t _position wcregex_iterator start, end try: start = make_regex_iterator(text, <wregex>pattern, match_flags.match_perl) end = wcregex_iterator() while (start != end): what = <wcmatch>deref(start) if not what.empty(): match_object = UnicodeMatch.from_instance(what) yield match_object else: print('Empty match result: ??') inc(start) # increment except Exception as e: raise RuntimeError(f'{e}') Thank you Eren

1 0

Fwd: [GSoC 2020][GIL] Mentors and project proposals
by Mateusz Loskot 17 Jan '20

17 Jan '20

FYI, https://lists.boost.org/boost-gil/2020/01/0372.php, copied below. ---------- Forwarded message --------- From: Mateusz Loskot <mateusz(a)loskot.net> Date: Fri, 17 Jan 2020 at 23:17 Subject: [GSoC 2020] Mentors and project proposals To: <boost-gil(a)lists.boost.org> Dear All, I have started collecting proposals of GIL projects for GSoC 2020. On the Boost official GSoC 2020 wiki, I've added Image Processing project as continuation of Miral's project from 2019: https://github.com/boostorg/boost/wiki/Google-Summer-of-Code:-2020 If Boost will participate, I should be able to mentor this year. Stefan, are you on board too? Who else? If there are students and mentors interested in GIL, it is time to stop being shy ;) Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 0

[Graph] Large incoming changes to Boost.Graph master.
by John Maddock 08 Jan '20

08 Jan '20

Dear all, Boost.Graph has had no maintainer for some time, but the CMT has been busy fixing bugs none the less. Unfortunately, other than some trivial fixes to docs and some directory refactoring, nothing much has been merged to master in a good while . On the plus side, develop is now in a better tested tested state than IMO it has ever been, however the change set is rather large so the potential to mess up somebodies code is certainly there: https://github.com/boostorg/graph/pull/196. So... this is both a heads up, and a plea: if you have any mission critical code using the Graph library, could you please test against current develop and report any problems? If you don't want to mess about with git, download from https://github.com/boostorg/graph/archive/develop.zip and place zipfile-contents/libs/graph/include in your include path ahead of that for Boost-1.72. Many thanks, John.

1 0

Re: [Boost-users] [boost] Retirement as Review Wizard
by Matt Calabrese 07 Jan '20

07 Jan '20

On Sat, Jan 4, 2020, 20:23 Ronald Garcia via Boost <boost(a)lists.boost.org> wrote: > Dear Boosters and Boost Steering Committee, > > After roughly 14 years as a Boost Co-Review Wizard, I feel that the time > has come for me to step down from the position, and make room for a new > face with fresh ideas. It has been my pleasure to serve in this position > for this time alongside first Tom Brinkman and now John Phillips. > I look forward to seeing what the next 14+ years of Boost brings! > Thanks for everything, Ron! >

1 0

Re: [Boost-users] [boost-steering] Retirement as Review Wizard
by Antony Polukhin 06 Jan '20

06 Jan '20

Many thanks for all your contributions! On Sat, Jan 4, 2020, 22:03 Ronald Garcia <rxg(a)cs.ubc.ca> wrote: > Dear Boosters and Boost Steering Committee, > > After roughly 14 years as a Boost Co-Review Wizard, I feel that the time > has come for me to step down from the position, and make room for a new > face with fresh ideas. It has been my pleasure to serve in this position > for this time alongside first Tom Brinkman and now John Phillips. > I look forward to seeing what the next 14+ years of Boost brings! > > > Sincerely, > Ron Garcia > Boost Co-Review Wizard > > > > > -- > The Boost Steering Committee webpage: > https://sites.google.com/a/boost.org/steering/ > --- > You received this message because you are subscribed to the Google Groups > "Boost Steering Committee" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to boost-steering+unsubscribe(a)googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/boost-steering/BFFCD488-2E57-4161-8D13-2D… > . >

1 0

Re: [Boost-users] [boost-steering] Retirement as Review Wizard
by Jon Kalb 06 Jan '20

06 Jan '20

Ron, For myself and on behalf of the Boost Steering Committee, thanks very much for both your effort on behalf of the Boost community and the leadership that you've demonstrated. Jon On Sat, Jan 4, 2020 at 2:03 PM Ronald Garcia <rxg(a)cs.ubc.ca> wrote: > Dear Boosters and Boost Steering Committee, > > After roughly 14 years as a Boost Co-Review Wizard, I feel that the time > has come for me to step down from the position, and make room for a new > face with fresh ideas. It has been my pleasure to serve in this position > for this time alongside first Tom Brinkman and now John Phillips. > I look forward to seeing what the next 14+ years of Boost brings! > > > Sincerely, > Ron Garcia > Boost Co-Review Wizard > > > > > -- > The Boost Steering Committee webpage: > https://sites.google.com/a/boost.org/steering/ > --- > You received this message because you are subscribed to the Google Groups > "Boost Steering Committee" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to boost-steering+unsubscribe(a)googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/boost-steering/BFFCD488-2E57-4161-8D13-2D… > . >

1 0

[Geometry] Trouble with adapting geometric objects to Eigen to use convex_hull on multiple polygons
by Rostyslav-Paul Wilhelm 06 Jan '20

06 Jan '20

1 0

Re: [Boost-users] [boost] Retirement as Review Wizard
by Glen Fernandes 05 Jan '20

05 Jan '20

On Ronald Garcia wrote: > > Dear Boosters and Boost Steering Committee, > > After roughly 14 years as a Boost Co-Review Wizard, I feel that the time has come for me to step down from the position, and make room for a new face with fresh ideas. It has been my pleasure to serve in this position for this time alongside first Tom Brinkman and now John Phillips. > I look forward to seeing what the next 14+ years of Boost brings! Many thanks for your service to Boost all these years, Ron. Glen

1 0

Re: [Boost-users] [boost] Retirement as Review Wizard
by Niall Douglas 05 Jan '20

05 Jan '20

On 04/01/2020 19:02, Ronald Garcia via Boost wrote: > After roughly 14 years as a Boost Co-Review Wizard, I feel that the time has come for me to step down from the position, and make room for a new face with fresh ideas. It has been my pleasure to serve in this position for this time alongside first Tom Brinkman and now John Phillips. Many Boost folk may not be aware, but Ron does a ton of stuff behind the scenes which no one publicly notices. I can think of at least two occasions during my time within Boost innards where Ron stepped in to defuse a problem, or found a solution which wasn't apparently possible. Boost will be the less for Ron's departure. Thank you for your service, and best of luck in your future endeavours! Niall

1 0

Re: [Boost-users] [boost] Retirement as Review Wizard
by Vinnie Falco 05 Jan '20

05 Jan '20

On Sat, Jan 4, 2020 at 5:23 PM Ronald Garcia via Boost <boost(a)lists.boost.org> wrote: > After roughly 14 years as a Boost Co-Review Wizard > I feel that the time has come for me to step down from the position, > and make room for a new face with fresh ideas. Thank you for your generous investment of time to act as a Boost Review Wizard! Does this mean that you are now available to act as a regular Review Manager? Because there's this library... Thanks

1 0

[review][STLInterfaces] STLInterfaces review results
by Barrett Adair 26 Dec '19

26 Dec '19

Many thanks are owed to all who participated in the formal review of Zach Laine's STLInterfaces library, especially during this busy holiday season: * Hadriel Kaplan - ACCEPT * Andreas Wass - ACCEPT * Rainer Deyke - ACCEPT * Arthur Gruzauskas - ACCEPT * Krystian Stasiowski - ACCEPT * Daniela Engert - CONDITIONALLY ACCEPT * Gavin Lambert - Technical comments First, a summary of the reviews: 1. Design Reviewers were unanimous in their appreciation for the design. Krystian had the only asterisk about the design, noting that derived class members should ideally be SFINAE-detected, where the library feature would SFINAE where the corresponding required derived feature detection fails. I have a different opinion about this, but we can discuss that elsewhere. 2. Implementation The container_interface destructor and the optional dependency on cmcstl2 were snags for multiple reviewers. Several compile errors were discovered that need to be addressed. 3. Documentation Reviewers found the documentation to be "ok". A common request was for better organization of derived-class requirements, particularly with the container_interface template. Reviewers also lamented the lack of training wheels for the subject matter. 4. Tests Hadriel noted the lack of non-copyable value_type tests, while Daniela noted the lack of Boost.Build support. Hadriel was the only one who commented on the quality of tests ("good"), and the only one who ran them. Arthur did his own testing, to satisfaction. I appreciate the presence of SFINAE-friendliness tests and the continuous integration. 5. Usefulness Reviewers appreciated the usefulness of the library. Arthur is "using it happily", while others found it "very useful", "fairly useful", or of "high" usefulness. However, Krystian's response implied that this library may not be as useful for containers needing extreme performance. The reviews clearly demonstrate a consensus. Accordingly, I'm pleased to announce that STLInterfaces is CONDITIONALLY ACCEPTED as a Boost library. Conditions for acceptance: 1. Remove optional dependency on cmcstl2 (issue #27) 2. Add Boost license comments to all files, including appveyor.yml, .travis.yml, README.md, */CMakeLists.txt (issue #26) 3. Support Boost.Build (issue #25) 4. Replace googletest with Boost equivalent (issue #24) 5. Remove usage of non-existent v2_dtl members in container_interface.hpp (issue #22) 6. Include <tuple> for std::tie usage in C++14 mode (issue #21) 7. Fix dangling parens in container_inteface.hpp:731 (issue #20) 8. Make Concepts usage C++20-conformant (issue #13) 9. Remove the destructor in container_interface (issue #12) 10. Add tests for non-copyable value types (issue #30) Suggestions: 1. Explicitly document the signatures and return types of functions provided by base class templates (issue #23) 2. Mention the C++20 generator pattern in documentation (issue #19) 3. Document the library's interactions with Ranges (issue #18) 4. Remove unnecessary comments (issue #17) 5. Investigate compile error in VS2015 (msvc 19.0.3) due to issues with noexcept() operator in function overloading (issue #16) 6. Rename container_interface to sequence_container_interface (issue #15) 7. Change the 'contiguous' bool to an enum (issue #14) 8. Document the relationship between value_type operator== and containter_interface-defined operator== (issue #11) 9. Improve table/section names for better navigation of container_interface tutorial (issue #10) 10. Clean up BOOST_STL_INTERFACES_DOXYGEN usage (issue #28) 11. Split up fwd.hpp into multiple headers (issue #29) 12. Document optimization trade-offs of proxy_iterator_interface (issue #30) Rationale: 1. Condition #1 is, I feel, the appropriate default as review manager. If Zach feels strongly about keeping the optional dependency on cmcstl2, we should discuss. 2. Unless the library requirements webpage has fallen out of date, new libraries must still support Boost.Build. 3. A not-so-quick grep of current Boost libraries yields no `gtest` results. I assume that we do not allow googletest as the sole test framework in a library. 4. The other conditions should be self-explanatory. Thank you Zach for your contributions, and I look forward to working with you to add this library into Boost. Regards, Barrett Adair

1 0

[boost] Merry Christmas!
by Vinnie Falco 25 Dec '19

25 Dec '19

Merry Christmas to all my fellow boost authors and wonderful users! God bless everyone as we celebrate the birth of Jesus Christ. And as we go into the new year I would like to give a humble and very friendly reminder: Boost.JSON needs a review manager! Blessings always Vinnie

2 2

Re: [Boost-users] Boost 1.72.0 build fail with Visual Studio 2019 16.4
by Leo Carreon 25 Dec '19

25 Dec '19

I was able to eliminate most of the error messages during compilation by modifying the contents of boost\asio\detail\config.hpp. I changed this line from: # define BOOST_ASIO_CONCEPT concept bool to # define BOOST_ASIO_CONCEPT concept After the above change, there are still two error messages from boost\asio\async_result.hpp lines 70 and 492. The issue in these lines is they are defining a concept that is also using a concept in one of their arguments which I think is not allowed by the standard. I am not up to speed yet with concept definitions therefore I have not been able to resolve this remaining issue. From: Leo Carreon Sent: Tuesday, December 24, 2019 2:37 PM To: Boost Users Mailing List Subject: Boost 1.72.0 build fail with Visual Studio 2019 16.4 Hi Boost Users, I am building Boost 1.72.0 in 64-bit mode with the flag /std:c++latest using Visual Studio 2019 16.4.2 and I am encountering the following issues: .\boost/asio/async_result.hpp(44): error C2062: type 'bool' unexpected .\boost/asio/async_result.hpp(45): error C2143: syntax error: missing ';' before '{' .\boost/asio/async_result.hpp(45): error C2447: '{': missing function header (old-style formal list?) .\boost/asio/async_result.hpp(56): error C7568: argument list missing after assumed function template 'callable_with' .\boost/asio/async_result.hpp(58): note: see reference to class template instantiation 'boost::asio::detail::is_completion_handler_for<T,R(Args...)>' being compiled .\boost/asio/async_result.hpp(56): error C2059: syntax error: '>' .\boost/asio/async_result.hpp(57): error C3770: 'unknown-type': is not a valid base class .\boost/asio/async_result.hpp(63): error C2062: type 'bool' unexpected .\boost/asio/async_result.hpp(64): error C2065: 'T': undeclared identifier .\boost/asio/async_result.hpp(64): error C2923: 'boost::asio::detail::is_completion_signature': 'T' is not a valid template type argument for parameter 'T' .\boost/asio/async_result.hpp(64): error C2955: 'boost::asio::detail::is_completion_signature': use of class template requires template argument list .\boost/asio/async_result.hpp(34): note: see declaration of 'boost::asio::detail::is_completion_signature' .\boost/asio/async_result.hpp(69): error C2061: syntax error: identifier 'completion_signature' .\boost/asio/async_result.hpp(70): error C2062: type 'bool' unexpected .\boost/asio/async_result.hpp(71): error C2065: 'T': undeclared identifier .\boost/asio/async_result.hpp(71): error C2065: 'Signature': undeclared identifier .\boost/asio/async_result.hpp(71): error C2923: 'boost::asio::detail::is_completion_handler_for': 'T' is not a valid template type argument for parameter 'T' .\boost/asio/async_result.hpp(71): error C2923: 'boost::asio::detail::is_completion_handler_for': 'Signature' is not a valid template type argument for parameter 'Signature' .\boost/asio/async_result.hpp(71): error C2955: 'boost::asio::detail::is_completion_handler_for': use of class template requires template argument list .\boost/asio/async_result.hpp(50): note: see declaration of 'boost::asio::detail::is_completion_handler_for' .\boost/asio/async_result.hpp(105): error C2039: 'completion_signature': is not a member of 'boost::asio' .\boost/asio/async_result.hpp(25): note: see declaration of 'boost::asio' .\boost/asio/async_result.hpp(105): error C2061: syntax error: identifier 'completion_signature' .\boost/asio/async_result.hpp(144): error C2061: syntax error: identifier 'completion_handler_for' .\boost/asio/async_result.hpp(190): note: see reference to class template instantiation 'boost::asio::async_result<CompletionToken>' being compiled .\boost/asio/async_result.hpp(144): error C2988: unrecognizable template declaration/definition .\boost/asio/async_result.hpp(144): error C2059: syntax error: ',' .\boost/asio/async_result.hpp(150): error C2334: unexpected token(s) preceding '{'; skipping apparent function body .\boost/asio/async_result.hpp(194): error C2039: 'completion_signature': is not a member of 'boost::asio' .\boost/asio/async_result.hpp(25): note: see declaration of 'boost::asio' .\boost/asio/async_result.hpp(194): error C2061: syntax error: identifier 'completion_signature' .\boost/asio/async_result.hpp(195): error C2065: 'Signature': undeclared identifier .\boost/asio/async_result.hpp(196): error C2977: 'boost::asio::async_result': too many template arguments .\boost/asio/async_result.hpp(107): note: see declaration of 'boost::asio::async_result' .\boost/asio/async_result.hpp(198): error C2913: explicit specialization; 'boost::asio::async_result' is not a specialization of a class template .\boost/asio/async_result.hpp(205): error C2039: 'completion_signature': is not a member of 'boost::asio' .\boost/asio/async_result.hpp(25): note: see declaration of 'boost::asio' .\boost/asio/async_result.hpp(205): error C2061: syntax error: identifier 'completion_signature' .\boost/asio/async_result.hpp(211): error C2065: 'Signature': undeclared identifier .\boost/asio/async_result.hpp(251): note: see reference to class template instantiation 'boost::asio::async_completion<CompletionToken>' being compiled .\boost/asio/async_result.hpp(250): error C2065: 'Signature': undeclared identifier .\boost/asio/async_result.hpp(250): error C2955: 'boost::asio::async_result': use of class template requires template argument list .\boost/asio/async_result.hpp(195): note: see declaration of 'boost::asio::async_result' .\boost/asio/async_result.hpp(258): error C2955: 'boost::asio::async_result': use of class template requires template argument list .\boost/asio/async_result.hpp(195): note: see declaration of 'boost::asio::async_result' .\boost/asio/async_result.hpp(259): note: see reference to class template instantiation 'boost::asio::detail::async_result_helper<CompletionToken,Signature>' being compiled .\boost/asio/async_result.hpp(288): error C2672: 'boost::asio::detail::async_result_initiate_memfn_helper': no matching overloaded function found .\boost/asio/async_result.hpp(292): note: see reference to class template instantiation 'boost::asio::detail::async_result_has_initiate_memfn<CompletionToken,Signature>' being compiled .\boost/asio/async_result.hpp(290): error C3206: 'boost::asio::detail::async_result_initiate_memfn_helper': invalid template argument for 'T', missing template argument list on class template 'boost::asio::async_result' .\boost/asio/async_result.hpp(281): note: see declaration of 'boost::asio::detail::async_result_initiate_memfn_helper' .\boost/asio/async_result.hpp(290): error C3206: 'boost::asio::detail::async_result_initiate_memfn_helper': invalid template argument for '<unnamed-symbol>', missing template argument list on class template 'boost::asio::async_result' .\boost/asio/async_result.hpp(278): note: see declaration of 'boost::asio::detail::async_result_initiate_memfn_helper' .\boost/asio/async_result.hpp(350): error C2039: 'completion_signature': is not a member of 'boost::asio' .\boost/asio/async_result.hpp(25): note: see declaration of 'boost::asio' .\boost/asio/async_result.hpp(350): error C2061: syntax error: identifier 'completion_signature' .\boost/asio/async_result.hpp(353): error C2065: 'Signature': undeclared identifier .\boost/asio/async_result.hpp(353): error C2923: 'boost::asio::detail::async_result_has_initiate_memfn': 'Signature' is not a valid template type argument for parameter 'Signature' .\boost/asio/async_result.hpp(354): error C2760: syntax error: unexpected token '>', expected 'expression' .\boost/asio/async_result.hpp(359): error C2065: 'Initiation': undeclared identifier .\boost/asio/async_result.hpp(359): error C2065: 'initiation': undeclared identifier .\boost/asio/async_result.hpp(360): error C2065: 'token': undeclared identifier .\boost/asio/async_result.hpp(361): error C2065: 'Args': undeclared identifier .\boost/asio/async_result.hpp(361): warning C4346: 'boost::asio::detail::async_result_has_initiate_memfn::value': dependent name is not a type .\boost/asio/async_result.hpp(361): note: prefix with 'typename' to indicate a type .\boost/asio/async_result.hpp(361): error C2988: unrecognizable template declaration/definition .\boost/asio/async_result.hpp(361): error C2059: syntax error: '...' .\boost/asio/async_result.hpp(362): error C2143: syntax error: missing ';' before '{' .\boost/asio/async_result.hpp(362): error C2447: '{': missing function header (old-style formal list?) .\boost/asio/async_result.hpp(370): error C2039: 'completion_signature': is not a member of 'boost::asio' .\boost/asio/async_result.hpp(25): note: see declaration of 'boost::asio' .\boost/asio/async_result.hpp(370): error C2061: syntax error: identifier 'completion_signature' .\boost/asio/async_result.hpp(373): error C2065: 'Signature': undeclared identifier .\boost/asio/async_result.hpp(373): error C2923: 'boost::asio::detail::async_result_has_initiate_memfn': 'Signature' is not a valid template type argument for parameter 'Signature' .\boost/asio/async_result.hpp(374): error C2065: 'Signature': undeclared identifier .\boost/asio/async_result.hpp(375): error C2065: 'Initiation': undeclared identifier .\boost/asio/async_result.hpp(375): error C2065: 'initiation': undeclared identifier .\boost/asio/async_result.hpp(376): error C2065: 'token': undeclared identifier .\boost/asio/async_result.hpp(377): error C2065: 'Args': undeclared identifier .\boost/asio/async_result.hpp(377): warning C4346: 'boost::asio::detail::async_result_has_initiate_memfn::value': dependent name is not a type .\boost/asio/async_result.hpp(377): note: prefix with 'typename' to indicate a type .\boost/asio/async_result.hpp(377): error C2988: unrecognizable template declaration/definition .\boost/asio/async_result.hpp(377): error C2059: syntax error: '...' .\boost/asio/async_result.hpp(378): error C2143: syntax error: missing ';' before '{' .\boost/asio/async_result.hpp(378): error C2447: '{': missing function header (old-style formal list?) .\boost/asio/async_result.hpp(483): error C7568: argument list missing after assumed function template 'completion_handler_for' .\boost/asio/async_result.hpp(487): note: see reference to class template instantiation 'boost::asio::detail::initiation_archetype<Signature>' being compiled .\boost/asio/async_result.hpp(484): error C2061: syntax error: identifier 'CompletionHandler' .\boost/asio/async_result.hpp(491): error C2061: syntax error: identifier 'completion_signature' .\boost/asio/async_result.hpp(492): error C2062: type 'bool' unexpected .\boost/asio/async_result.hpp(493): error C2143: syntax error: missing ';' before '{' .\boost/asio/async_result.hpp(493): error C2447: '{': missing function header (old-style formal list?) .\boost/asio/post.hpp(56): error C2039: 'completion_token_for': is not a member of 'boost::asio' .\boost/asio/post.hpp(27): note: see declaration of 'boost::asio' .\boost/asio/post.hpp(56): error C2061: syntax error: identifier 'completion_token_for' .\boost/asio/post.hpp(56): error C2988: unrecognizable template declaration/definition .\boost/asio/post.hpp(56): error C2059: syntax error: '>' .\boost/asio/post.hpp(94): error C2039: 'completion_token_for': is not a member of 'boost::asio' .\boost/asio/post.hpp(27): note: see declaration of 'boost::asio' .\boost/asio/post.hpp(94): error C2061: syntax error: identifier 'completion_token_for' .\boost/asio/post.hpp(95): error C2988: unrecognizable template declaration/definition .\boost/asio/post.hpp(95): error C2059: syntax error: '>' .\boost/asio/post.hpp(107): error C2039: 'completion_token_for': is not a member of 'boost::asio' .\boost/asio/post.hpp(27): note: see declaration of 'boost::asio' .\boost/asio/post.hpp(107): error C2061: syntax error: identifier 'completion_token_for' .\boost/asio/post.hpp(108): error C2988: unrecognizable template declaration/definition .\boost/asio/post.hpp(108): error C2059: syntax error: '>' .\boost/asio/impl/post.hpp(81): error C2039: 'completion_token_for': is not a member of 'boost::asio' .\boost/asio/impl/post.hpp(26): note: see declaration of 'boost::asio' .\boost/asio/impl/post.hpp(81): error C2061: syntax error: identifier 'completion_token_for' .\boost/asio/impl/post.hpp(81): error C2988: unrecognizable template declaration/definition .\boost/asio/impl/post.hpp(81): error C2059: syntax error: '>' .\boost/asio/impl/post.hpp(84): error C2143: syntax error: missing ';' before '{' .\boost/asio/impl/post.hpp(84): error C2447: '{': missing function header (old-style formal list?) .\boost/asio/impl/post.hpp(90): error C2039: 'completion_token_for': is not a member of 'boost::asio' .\boost/asio/impl/post.hpp(26): note: see declaration of 'boost::asio' .\boost/asio/impl/post.hpp(90): error C2061: syntax error: identifier 'completion_token_for' .\boost/asio/impl/post.hpp(90): error C2988: unrecognizable template declaration/definition .\boost/asio/impl/post.hpp(90): error C2059: syntax error: '>' .\boost/asio/impl/post.hpp(94): error C2143: syntax error: missing ';' before '{' .\boost/asio/impl/post.hpp(94): error C2447: '{': missing function header (old-style formal list?) .\boost/asio/impl/post.hpp(100): error C2039: 'completion_token_for': is not a member of 'boost::asio' .\boost/asio/impl/post.hpp(26): note: see declaration of 'boost::asio' .\boost/asio/impl/post.hpp(100): error C2061: syntax error: identifier 'completion_token_for' .\boost/asio/impl/post.hpp(100): error C2988: unrecognizable template declaration/definition .\boost/asio/impl/post.hpp(100): error C2059: syntax error: '>' .\boost/asio/impl/post.hpp(105): error C2143: syntax error: missing ';' before '{' .\boost/asio/impl/post.hpp(105): error C2447: '{': missing function header (old-style formal list?) .\boost/asio/detail/buffer_sequence_adapter.hpp(106): error C2955: 'boost::asio::detail::buffer_sequence_adapter_base': use of class template requires template argument list .\boost/asio/detail/buffer_sequence_adapter.hpp(30): note: see declaration of 'boost::asio::detail::buffer_sequence_adapter_base' .\boost/asio/detail/buffer_sequence_adapter.hpp(208): note: see reference to class template instantiation 'boost::asio::detail::buffer_sequence_adapter<Buffer,Buffers>' being compiled .\boost/asio/detail/buffer_sequence_adapter.hpp(116): error C2143: syntax error: missing ';' before '*' .\boost/asio/detail/buffer_sequence_adapter.hpp(116): fatal error C1003: error count exceeds 100; stopping compilation Has anyone else encountered the same issues and how to resolve them? It appears that the macro BOOST_ASIO_CONCEPT is the one causing the issue. This macro seems to have the value “concept bool” which causes the complaint from the compiler. Kind regards, Leo

2 2

Boost 1.72.0 build fail with Visual Studio 2019 16.4
by Leo Carreon 24 Dec '19

24 Dec '19

Hi Boost Users, I am building Boost 1.72.0 in 64-bit mode with the flag /std:c++latest using Visual Studio 2019 16.4.2 and I am encountering the following issues: .\boost/asio/async_result.hpp(44): error C2062: type 'bool' unexpected .\boost/asio/async_result.hpp(45): error C2143: syntax error: missing ';' before '{' .\boost/asio/async_result.hpp(45): error C2447: '{': missing function header (old-style formal list?) .\boost/asio/async_result.hpp(56): error C7568: argument list missing after assumed function template 'callable_with' .\boost/asio/async_result.hpp(58): note: see reference to class template instantiation 'boost::asio::detail::is_completion_handler_for<T,R(Args...)>' being compiled .\boost/asio/async_result.hpp(56): error C2059: syntax error: '>' .\boost/asio/async_result.hpp(57): error C3770: 'unknown-type': is not a valid base class .\boost/asio/async_result.hpp(63): error C2062: type 'bool' unexpected .\boost/asio/async_result.hpp(64): error C2065: 'T': undeclared identifier .\boost/asio/async_result.hpp(64): error C2923: 'boost::asio::detail::is_completion_signature': 'T' is not a valid template type argument for parameter 'T' .\boost/asio/async_result.hpp(64): error C2955: 'boost::asio::detail::is_completion_signature': use of class template requires template argument list .\boost/asio/async_result.hpp(34): note: see declaration of 'boost::asio::detail::is_completion_signature' .\boost/asio/async_result.hpp(69): error C2061: syntax error: identifier 'completion_signature' .\boost/asio/async_result.hpp(70): error C2062: type 'bool' unexpected .\boost/asio/async_result.hpp(71): error C2065: 'T': undeclared identifier .\boost/asio/async_result.hpp(71): error C2065: 'Signature': undeclared identifier .\boost/asio/async_result.hpp(71): error C2923: 'boost::asio::detail::is_completion_handler_for': 'T' is not a valid template type argument for parameter 'T' .\boost/asio/async_result.hpp(71): error C2923: 'boost::asio::detail::is_completion_handler_for': 'Signature' is not a valid template type argument for parameter 'Signature' .\boost/asio/async_result.hpp(71): error C2955: 'boost::asio::detail::is_completion_handler_for': use of class template requires template argument list .\boost/asio/async_result.hpp(50): note: see declaration of 'boost::asio::detail::is_completion_handler_for' .\boost/asio/async_result.hpp(105): error C2039: 'completion_signature': is not a member of 'boost::asio' .\boost/asio/async_result.hpp(25): note: see declaration of 'boost::asio' .\boost/asio/async_result.hpp(105): error C2061: syntax error: identifier 'completion_signature' .\boost/asio/async_result.hpp(144): error C2061: syntax error: identifier 'completion_handler_for' .\boost/asio/async_result.hpp(190): note: see reference to class template instantiation 'boost::asio::async_result<CompletionToken>' being compiled .\boost/asio/async_result.hpp(144): error C2988: unrecognizable template declaration/definition .\boost/asio/async_result.hpp(144): error C2059: syntax error: ',' .\boost/asio/async_result.hpp(150): error C2334: unexpected token(s) preceding '{'; skipping apparent function body .\boost/asio/async_result.hpp(194): error C2039: 'completion_signature': is not a member of 'boost::asio' .\boost/asio/async_result.hpp(25): note: see declaration of 'boost::asio' .\boost/asio/async_result.hpp(194): error C2061: syntax error: identifier 'completion_signature' .\boost/asio/async_result.hpp(195): error C2065: 'Signature': undeclared identifier .\boost/asio/async_result.hpp(196): error C2977: 'boost::asio::async_result': too many template arguments .\boost/asio/async_result.hpp(107): note: see declaration of 'boost::asio::async_result' .\boost/asio/async_result.hpp(198): error C2913: explicit specialization; 'boost::asio::async_result' is not a specialization of a class template .\boost/asio/async_result.hpp(205): error C2039: 'completion_signature': is not a member of 'boost::asio' .\boost/asio/async_result.hpp(25): note: see declaration of 'boost::asio' .\boost/asio/async_result.hpp(205): error C2061: syntax error: identifier 'completion_signature' .\boost/asio/async_result.hpp(211): error C2065: 'Signature': undeclared identifier .\boost/asio/async_result.hpp(251): note: see reference to class template instantiation 'boost::asio::async_completion<CompletionToken>' being compiled .\boost/asio/async_result.hpp(250): error C2065: 'Signature': undeclared identifier .\boost/asio/async_result.hpp(250): error C2955: 'boost::asio::async_result': use of class template requires template argument list .\boost/asio/async_result.hpp(195): note: see declaration of 'boost::asio::async_result' .\boost/asio/async_result.hpp(258): error C2955: 'boost::asio::async_result': use of class template requires template argument list .\boost/asio/async_result.hpp(195): note: see declaration of 'boost::asio::async_result' .\boost/asio/async_result.hpp(259): note: see reference to class template instantiation 'boost::asio::detail::async_result_helper<CompletionToken,Signature>' being compiled .\boost/asio/async_result.hpp(288): error C2672: 'boost::asio::detail::async_result_initiate_memfn_helper': no matching overloaded function found .\boost/asio/async_result.hpp(292): note: see reference to class template instantiation 'boost::asio::detail::async_result_has_initiate_memfn<CompletionToken,Signature>' being compiled .\boost/asio/async_result.hpp(290): error C3206: 'boost::asio::detail::async_result_initiate_memfn_helper': invalid template argument for 'T', missing template argument list on class template 'boost::asio::async_result' .\boost/asio/async_result.hpp(281): note: see declaration of 'boost::asio::detail::async_result_initiate_memfn_helper' .\boost/asio/async_result.hpp(290): error C3206: 'boost::asio::detail::async_result_initiate_memfn_helper': invalid template argument for '<unnamed-symbol>', missing template argument list on class template 'boost::asio::async_result' .\boost/asio/async_result.hpp(278): note: see declaration of 'boost::asio::detail::async_result_initiate_memfn_helper' .\boost/asio/async_result.hpp(350): error C2039: 'completion_signature': is not a member of 'boost::asio' .\boost/asio/async_result.hpp(25): note: see declaration of 'boost::asio' .\boost/asio/async_result.hpp(350): error C2061: syntax error: identifier 'completion_signature' .\boost/asio/async_result.hpp(353): error C2065: 'Signature': undeclared identifier .\boost/asio/async_result.hpp(353): error C2923: 'boost::asio::detail::async_result_has_initiate_memfn': 'Signature' is not a valid template type argument for parameter 'Signature' .\boost/asio/async_result.hpp(354): error C2760: syntax error: unexpected token '>', expected 'expression' .\boost/asio/async_result.hpp(359): error C2065: 'Initiation': undeclared identifier .\boost/asio/async_result.hpp(359): error C2065: 'initiation': undeclared identifier .\boost/asio/async_result.hpp(360): error C2065: 'token': undeclared identifier .\boost/asio/async_result.hpp(361): error C2065: 'Args': undeclared identifier .\boost/asio/async_result.hpp(361): warning C4346: 'boost::asio::detail::async_result_has_initiate_memfn::value': dependent name is not a type .\boost/asio/async_result.hpp(361): note: prefix with 'typename' to indicate a type .\boost/asio/async_result.hpp(361): error C2988: unrecognizable template declaration/definition .\boost/asio/async_result.hpp(361): error C2059: syntax error: '...' .\boost/asio/async_result.hpp(362): error C2143: syntax error: missing ';' before '{' .\boost/asio/async_result.hpp(362): error C2447: '{': missing function header (old-style formal list?) .\boost/asio/async_result.hpp(370): error C2039: 'completion_signature': is not a member of 'boost::asio' .\boost/asio/async_result.hpp(25): note: see declaration of 'boost::asio' .\boost/asio/async_result.hpp(370): error C2061: syntax error: identifier 'completion_signature' .\boost/asio/async_result.hpp(373): error C2065: 'Signature': undeclared identifier .\boost/asio/async_result.hpp(373): error C2923: 'boost::asio::detail::async_result_has_initiate_memfn': 'Signature' is not a valid template type argument for parameter 'Signature' .\boost/asio/async_result.hpp(374): error C2065: 'Signature': undeclared identifier .\boost/asio/async_result.hpp(375): error C2065: 'Initiation': undeclared identifier .\boost/asio/async_result.hpp(375): error C2065: 'initiation': undeclared identifier .\boost/asio/async_result.hpp(376): error C2065: 'token': undeclared identifier .\boost/asio/async_result.hpp(377): error C2065: 'Args': undeclared identifier .\boost/asio/async_result.hpp(377): warning C4346: 'boost::asio::detail::async_result_has_initiate_memfn::value': dependent name is not a type .\boost/asio/async_result.hpp(377): note: prefix with 'typename' to indicate a type .\boost/asio/async_result.hpp(377): error C2988: unrecognizable template declaration/definition .\boost/asio/async_result.hpp(377): error C2059: syntax error: '...' .\boost/asio/async_result.hpp(378): error C2143: syntax error: missing ';' before '{' .\boost/asio/async_result.hpp(378): error C2447: '{': missing function header (old-style formal list?) .\boost/asio/async_result.hpp(483): error C7568: argument list missing after assumed function template 'completion_handler_for' .\boost/asio/async_result.hpp(487): note: see reference to class template instantiation 'boost::asio::detail::initiation_archetype<Signature>' being compiled .\boost/asio/async_result.hpp(484): error C2061: syntax error: identifier 'CompletionHandler' .\boost/asio/async_result.hpp(491): error C2061: syntax error: identifier 'completion_signature' .\boost/asio/async_result.hpp(492): error C2062: type 'bool' unexpected .\boost/asio/async_result.hpp(493): error C2143: syntax error: missing ';' before '{' .\boost/asio/async_result.hpp(493): error C2447: '{': missing function header (old-style formal list?) .\boost/asio/post.hpp(56): error C2039: 'completion_token_for': is not a member of 'boost::asio' .\boost/asio/post.hpp(27): note: see declaration of 'boost::asio' .\boost/asio/post.hpp(56): error C2061: syntax error: identifier 'completion_token_for' .\boost/asio/post.hpp(56): error C2988: unrecognizable template declaration/definition .\boost/asio/post.hpp(56): error C2059: syntax error: '>' .\boost/asio/post.hpp(94): error C2039: 'completion_token_for': is not a member of 'boost::asio' .\boost/asio/post.hpp(27): note: see declaration of 'boost::asio' .\boost/asio/post.hpp(94): error C2061: syntax error: identifier 'completion_token_for' .\boost/asio/post.hpp(95): error C2988: unrecognizable template declaration/definition .\boost/asio/post.hpp(95): error C2059: syntax error: '>' .\boost/asio/post.hpp(107): error C2039: 'completion_token_for': is not a member of 'boost::asio' .\boost/asio/post.hpp(27): note: see declaration of 'boost::asio' .\boost/asio/post.hpp(107): error C2061: syntax error: identifier 'completion_token_for' .\boost/asio/post.hpp(108): error C2988: unrecognizable template declaration/definition .\boost/asio/post.hpp(108): error C2059: syntax error: '>' .\boost/asio/impl/post.hpp(81): error C2039: 'completion_token_for': is not a member of 'boost::asio' .\boost/asio/impl/post.hpp(26): note: see declaration of 'boost::asio' .\boost/asio/impl/post.hpp(81): error C2061: syntax error: identifier 'completion_token_for' .\boost/asio/impl/post.hpp(81): error C2988: unrecognizable template declaration/definition .\boost/asio/impl/post.hpp(81): error C2059: syntax error: '>' .\boost/asio/impl/post.hpp(84): error C2143: syntax error: missing ';' before '{' .\boost/asio/impl/post.hpp(84): error C2447: '{': missing function header (old-style formal list?) .\boost/asio/impl/post.hpp(90): error C2039: 'completion_token_for': is not a member of 'boost::asio' .\boost/asio/impl/post.hpp(26): note: see declaration of 'boost::asio' .\boost/asio/impl/post.hpp(90): error C2061: syntax error: identifier 'completion_token_for' .\boost/asio/impl/post.hpp(90): error C2988: unrecognizable template declaration/definition .\boost/asio/impl/post.hpp(90): error C2059: syntax error: '>' .\boost/asio/impl/post.hpp(94): error C2143: syntax error: missing ';' before '{' .\boost/asio/impl/post.hpp(94): error C2447: '{': missing function header (old-style formal list?) .\boost/asio/impl/post.hpp(100): error C2039: 'completion_token_for': is not a member of 'boost::asio' .\boost/asio/impl/post.hpp(26): note: see declaration of 'boost::asio' .\boost/asio/impl/post.hpp(100): error C2061: syntax error: identifier 'completion_token_for' .\boost/asio/impl/post.hpp(100): error C2988: unrecognizable template declaration/definition .\boost/asio/impl/post.hpp(100): error C2059: syntax error: '>' .\boost/asio/impl/post.hpp(105): error C2143: syntax error: missing ';' before '{' .\boost/asio/impl/post.hpp(105): error C2447: '{': missing function header (old-style formal list?) .\boost/asio/detail/buffer_sequence_adapter.hpp(106): error C2955: 'boost::asio::detail::buffer_sequence_adapter_base': use of class template requires template argument list .\boost/asio/detail/buffer_sequence_adapter.hpp(30): note: see declaration of 'boost::asio::detail::buffer_sequence_adapter_base' .\boost/asio/detail/buffer_sequence_adapter.hpp(208): note: see reference to class template instantiation 'boost::asio::detail::buffer_sequence_adapter<Buffer,Buffers>' being compiled .\boost/asio/detail/buffer_sequence_adapter.hpp(116): error C2143: syntax error: missing ';' before '*' .\boost/asio/detail/buffer_sequence_adapter.hpp(116): fatal error C1003: error count exceeds 100; stopping compilation Has anyone else encountered the same issues and how to resolve them? It appears that the macro BOOST_ASIO_CONCEPT is the one causing the issue. This macro seems to have the value “concept bool” which causes the complaint from the compiler. Kind regards, Leo

2 2

[Serialization] Serialize std::valarray of primitives
by Meik 23 Dec '19

23 Dec '19

Hello, I am new to C++ and thus new to Boost. My goal is to serialize a class containing multiple std::valarrays with primitives as content. The code I wrote to achieve that(minimal example to reproduce): #include <iostream> #include <boost/archive/text_oarchive.hpp> class A { valarray<int> member_one; valarray<float> member_two; friend class boost::serialization::access; template<class Archive> void serialize(Archive &ar, const unsigned int version){ ar & member_one; ar & member_two } } int main(int argc, char* argv[]) { boost::archive::text_oarchive oarchive(cout); oarchive << p; return 0; } When compiling this, the following error is given: error: class std::valarray<int> has no member names serialize I'd appreciate if you could let me know how to correctly serialize said std::valarray. Kind regards, Meik S. ||

2 1

[asio] asio::socket -> native handle ->asio::socket not working on windows
by Klebsch, Mario 21 Dec '19

21 Dec '19

Hello, I am using boost asio in a cross platform project. The project consists of two libraries, having a C call API in between. Until now, each of those two libraries uses boost::asio internally. Each of these libraries have their own instance of boost::asio::io_service. I now need to implement a change, that requires to pass a connected socket from one library to the other one via the C call API: This is what I want to do it. * Lib1 calls new method connect() in lib2 * lib2::connect() creates a boost::asio::ip::tcp::socket * lib2::connect() connects to a service * lib2::connect() does some async communication with that service. * when the service is initialized, lib2::connect() shall pass the native handle back to its caller (Lib1). * Lib1 then creates a boost::asio::ip::tcp::socket from the native handle I have learned, that there is no way to destroy a boost::asio::ip::tcp::socket without closing the native handle. So, I have to dup() it. No problem on POSIX systems, on Windows I can use a combination of WSADuplicateSocket () and WSASocket () to achieve the same. Everything works fine on Linux, but on Windows, the parts do not work together :) The individual parts are working find. * I can use the boost::asio::ip::tcp::socket to communicate with the service. * I can use WSADuplicateSocket () and WSASocket () to get a 2nd, native handle to the socket * I can use the 2nd, native handle to communicate to the service, even after destroying the boost::asio::ip::tcp::socket instance. * I also can create a working boost::asio::ip::tcp::socket from a native socket handle, created with socket() and connected to a service with connect(). BUT: If I try to create a boost::asio::ip::tcp::socket on the socket created by the WSADuplicateSocket () and WSASocket () sequence, I get an exception. The call to CreateIoCompletionPort() in win_iocp_io_service.ipp, win_iocp_io_service::register_handle() fails with error 87 (Invalid Parameter). I have no idea, why CreateIoCompletionPort() is failing and how to avoid this. Here is a sample program demonstrating my problem. If BUG is #defined, the code fails with std::exception "assign: Falscher Parameter" (invalid parameter). #ifdef _WIN32 #include <winsock2.h> #include <ws2tcpip.h> #else #include <sys/socket.h> #endif #include <boost/asio.hpp> #define ADDR "127.0.0.1" #define PORT "7" /* echo */ #include <stdio.h> #ifndef _WIN32 inline int WSAGetLastError() { return errno; } #endif int main() { char Request[]="Hello"; char Buffer[256]; int n; try { #ifdef _WIN32 SOCKET s1 = INVALID_SOCKET; #else int s1=-1; #endif #ifdef BUG { printf("The programm does not work with this code on windows :-(\n"); boost::asio::io_service IoService; boost::asio::ip::tcp::resolver Resolver(IoService); boost::asio::ip::tcp::resolver::query Query(ADDR, PORT); boost::asio::ip::tcp::socket s(IoService); s.connect(*Resolver.resolve(Query)); printf("connected\n"); #ifdef _WIN32 WSAPROTOCOL_INFO ProtocolInfo; DWORD MyProcId = GetCurrentProcessId(); int x = WSADuplicateSocket((SOCKET)s.native_handle(), MyProcId, &ProtocolInfo); if (x) throw boost::system::error_code(WSAGetLastError(), boost::system::system_category()); s1 = WSASocket(FROM_PROTOCOL_INFO, FROM_PROTOCOL_INFO, FROM_PROTOCOL_INFO, &ProtocolInfo, 0, WSA_FLAG_OVERLAPPED); #else /* !_WIN32 */ s1=dup(s.native_handle()); #endif /* !_WIN32 */ if (s1<0) throw boost::system::error_code(WSAGetLastError(), boost::system::system_category()); } #else s1 = socket(PF_INET, SOCK_STREAM, 0); if (s1 < 0) throw boost::system::error_code(WSAGetLastError(), boost::system::system_category()); struct sockaddr_in Addr; Addr.sin_family = AF_INET; Addr.sin_port = htons(atoi(PORT)); inet_pton(AF_INET, ADDR, &Addr.sin_addr); if (connect(s1, (struct sockaddr*)&Addr, sizeof(Addr)) < 0) throw boost::system::error_code(WSAGetLastError(), boost::system::system_category()); #endif printf("s1=%d\n", s1); { boost::asio::io_service IoService; boost::asio::ip::tcp::socket s(IoService, boost::asio::ip::tcp::v4(), (boost::asio::ip::tcp::socket::native_handle_type)s1); n = s.write_some(boost::asio::buffer(&Request, sizeof(Request))); printf("write_some() returned %d\n", n); n = s.read_some(boost::asio::buffer(Buffer, sizeof(Buffer))); printf("read_some() returned %d\n", n); } return 0; } catch (boost::system::error_code &ec) { fprintf(stderr, "boost::system::error_code: %s\n", ec.message().c_str()); return -1; } catch (std::exception &e) { fprintf(stderr, "std::exception: %s\n", e.what()); return -1; } } Thanks in advance, Mario -- Mario Klebsch Actia I+ME GmbH Mario.klebsch(a)ime-actia.de<mailto:Mario.klebsch@ime-actia.de> Dresdenstrasse 17/18 Fon: +49 531 38 701 716 38124 Braunschweig Fax: +49 531 38 701 88 German

2 1