July 2022 - Boost - lists.boost.org

C++11 or C++14?
by Vinnie Falco 25 Jul '22

25 Jul '22

I'm considering bumping up the C++ language requirement for Boost.URL from C++11 to C++14. I have concerns about doing this, because it affects all my downstream libraries (HTTP.Proto, HTTP.IO, Websocket.Proto, Websocket.IO, and any examples or complete clients/servers that I write). My main fear is that there are still a considerable number of individuals or corporations who, for whatever reason, cannot build with -std=c++14 or later despite having access to newer compilers. I don't mind if there is a small percentage of loss but I do mind if 20% or more of potential users will be locked out. The questions are: 1. Would you or your company be prevented from using Boost.URL if it required C++14? 2. Do you know any other organizations who cannot use C++14 or later? 3. Do you know of any regional or global metrics on who _cannot_ use libraries which require C++14? See also, this reddit thread on r/cpp: <https://www.reddit.com/r/cpp/comments/w6zuo5/c11_or_require_c14/> -- Regards, Vinnie Follow me on GitHub: https://github.com/vinniefalco

2 1

xproc: get process information from foreign processes
by Samuel Venable 20 Jul '22

20 Jul '22

Hi all. The main developer of the boost process library liked what he saw when I showed him my xproc API. He recommended me to send it to the boost mailing list and see what the other developers at boost think of it and whether it could be modified and adjusted into making it worthy of becoming an official part of the boost libraries. The Windows build currently only works with MSYS2/MinGW, see the open issue here for the full details on what works and what doesn't on the Windows platform and why: currently known Windows-related bugs · Issue #1 · time-killer-games/xproc (github.com)<https://github.com/time-killer-games/xproc/issues/1> The build.sh to build and example.sh to test is all you need to test all features, the only thing that isn't verified by the scripts is whether any memory leaks exist, and afaik in my testing Windows might be the only platform whith memory leaks, but its very unclear to me how to debug the source of them, because the code looks very correct, as I'm freeing memory everywhere online Microsoft documentation tells me to. Also supports Mac, Linux, FreeBSD, DragonFly BSD, NetBSD, and OpenBSD. If I ever find hardware that will work with an Illumos-based Operating System, then that will be added to the mix, (I refuse to use a VM, my personal hang-up). If the libprocps library the linux version depends on were ported to Android, that is another potential platform, but the "Enable Windowing Macro" will need to not be defined as that is more of a desktop-related thing. iOS can work with windowing disabled as well, but some sysctl() with KERN_PROCARGS2 may only work when running in developer/debug mode due to Apple's publishing restrictions. Linux and android are the only platforms with the third party library dependency. All other platforms only rely on dependencies already provided by the OS base and/or kernel. Here's everything you need for the API to work on most platforms, source & header... * xproc/process.cpp at main · time-killer-games/xproc (github.com)<https://github.com/time-killer-games/xproc/blob/main/apiprocess/process.cpp> * xproc/process.h at main · time-killer-games/xproc (github.com)<https://github.com/time-killer-games/xproc/blob/main/apiprocess/process.h> And only on Windows you will need these helper blobs generated by the build script... * xproc/process32.h at main · time-killer-games/xproc (github.com)<https://github.com/time-killer-games/xproc/blob/main/apiprocess/process32.h> * xproc/process64.h at main · time-killer-games/xproc (github.com)<https://github.com/time-killer-games/xproc/blob/main/apiprocess/process64.h> Here's an example of how to use the library and repository source tree... * xproc/main.cpp at main · time-killer-games/xproc (github.com)<https://github.com/time-killer-games/xproc/blob/main/main.cpp> * time-killer-games/xproc (github.com)<https://github.com/time-killer-games/xproc> * You guys have my permission to relicense this code under any version of the Boost license we can agree on if this work gets accepted at any point in time. All functions get process information in their current state at the time the functions are called expect on macOS KERN_PROCARGS2 gets the cmdline and environ of the process in its initial state when the process first launched, so if the cmdline or environ get modified after initialization or process lanch, you will have no way to get the updated values (OS-level limitation of macOS). Lastly, I have helper functions to optionally suspend and resume foreign processes to avoid race conditions where applicable. Let me know what you think and if you have any critiques or questions regarding my code do not hesitate to address that with me in a reply to this email! Thanks! Samuel

1 0

[Spirit] '_' parsed as '\0' with qi::phrase_parse
by Olaf van der Spek 19 Jul '22

19 Jul '22

Hi, The underscore is parsed as a null character. Is this expected. A bug? If a full repro is needed I can create one. qi::rule<iterator_t, std::string(), Skip> identifier; identifier %= lexeme[alpha >> *(alnum | '.' | '_')]; typedef boost::spirit::classic::position_iterator<const char*> iterator_t; std::string s = "a_b blah"; iterator_t is(s.c_str(), s.c_str() + s.size(), "<name>"); std::string out; bool res = qi::phrase_parse(is, iterator_t(), identifier, skip, out); if (!res && is != iterator_t()) error_handler_::err(is); cout << out.size() << "|" << out << "|\n"; cout << int(out[0]) << " " << int(out[1]) << " " << int(out[2]) << "\n"; Output: // 3|ab| // 97 0 98 Greetings, -- Olaf

2 2

[release] Boost 1.80.0 beta 1 released
by Glen Fernandes 14 Jul '22

14 Jul '22

Boost release 1.80.0 beta 1 is now available at: https://boostorg.jfrog.io/artifactory/main/beta/1.80.0.beta1/source/ The SHA256 checksums are: boost_1_80_0_b1.tar.bz2 - b29191c1bd4504511f9b1155c6f79f06cc7044444780392ed7358f5778ac7d16 boost_1_80_0_b1.tar.gz - ad3df9f63acd667dcf13375fa0e90e7303f851251e91d1505974bdbbf1f94907 boost_1_80_0_b1.7z - 7bfdf705b1d058c3525be90ed5cb47aacf919cd74aa7d5752d55e78aa60880ba boost_1_80_0_b1.zip - 1b509ed848f153086984658d4d4a57af6230f496a53bf88aba805bb49039012d Release notes (still need updates): https://www.boost.org/users/history/version_1_80_0.html Please try the beta and report any problems you encounter. Thanks, -- Boost Release Team

5 10

[release] Boost 1.80.0 Beta 1 Release Candidate 1 is available
by Marshall Clow 14 Jul '22

14 Jul '22

Available at: <https://boostorg.jfrog.io/ui/native/main/beta/1.80.0.beta1/source> The SHA256 checksums are as follows: b29191c1bd4504511f9b1155c6f79f06cc7044444780392ed7358f5778ac7d16 boost_1_80_0_b1.tar.bz2 7bfdf705b1d058c3525be90ed5cb47aacf919cd74aa7d5752d55e78aa60880ba boost_1_80_0_b1.7z ad3df9f63acd667dcf13375fa0e90e7303f851251e91d1505974bdbbf1f94907 boost_1_80_0_b1.tar.gz 1b509ed848f153086984658d4d4a57af6230f496a53bf88aba805bb49039012d boost_1_80_0_b1.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release Managers

5 6

[Graph] Can users on Xcode 7-10 help out?
by Jeremy Murphy 12 Jul '22

12 Jul '22

Dear Boost.Graph users, Is anyone that uses old Xcode 7-10 able to help out with some curious compilation errors? https://github.com/boostorg/graph/issues/298 We'll do our best to fix them but I assume it might be easier for someone that actually uses these particular platforms. Thanks, cheers. Jeremy

1 0

static_string
by Gero Peterhoff 10 Jul '22

10 Jul '22

Hello, if i include <boost/static_string.hpp> i get errors in std::variant: /usr/include/c++/12/variant:774:72: Fehler: Templateargument 4 ist ungültig 774 | void_t<decltype(_Arr<_Ti>{{std::declval<_Tp>()}})>> | ^~ /usr/include/c++/12/variant:804:76: Fehler: Templateargument 3 ist ungültig 804 | struct __accepted_index<_Tp, _Variant, void_t<_FUN_type<_Tp, _Variant>>> | ^ Can you retrace that? boost 1.79 gcc 12.1 -std=gnu++2b openSuse Tumbleweed thx Gero

3 2

[process] Process.Spawn leaves the child in zombie state on posix
by Benedek Tass 08 Jul '22

08 Jul '22

Hi, everyone! This bug was observed in 2022.07.05, using boost version 1.79.0. Similar behaviour was commented on before on online messageboards. Bug description When starting a new, detached process with Process.Spawn in a posix system, if the parent process outlives the child, the child process remains in zombie state for the parent process' lifetime. The bug described above is demonstrated in the CMake project attached to this document. Analysis The spawn function injects the syscall "signal(SIGCHLD, SIG_IGN)" with a functor of type boost::process::detail::posix::sig_init_. This is done to the forked child process, to no avail. And this is not done (and should not be done) in the parent process being too intrusive. Possible mitigation Introducing an in-between forked process that serves as the parent of the to-be-spawned process with SIGCHLD set to SIG_IGN would prevent the spawned process to become zombie, and simultaneously does not disturb the parent process' signal handlers. Introducing another class alternative to sig_init_ with the functionality described above would be a reasonable approach. An implementation sketch of the double fork method can be found in the attached project. System used OS: Ubuntu 18.04.6 LTS arch: x86_64 compiler: gcc-7.5.0 libc: libc-2.27 boost: 1.79.0 (built from source) Best regards, Benedek Tass

3 6

Boost 1.80.0 closed for beta
by Glen Fernandes 07 Jul '22

07 Jul '22

Master is closed for all changes. See the release schedule at: https://www.boost.org/development/index.html -- Release managers

2 1

Boost 1.80 closed for all major changes
by Glen Fernandes 05 Jul '22

05 Jul '22

The next deadlines: - On 2022-07-06 master is closed for all changes. - On 2022-07-13 the beta is published -- Release Managers

3 6