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

[multi_array] Feature request: constructor and resize from values
by Eugenio Bargiacchi 22 Nov '20

22 Nov '20

I'd love to be able to use multi_array with classes that do not have a default constructor. At the moment, this is impossible, as both the constructor and resize functions only take extents as arguments (and possibly some other options), but no value_type, as for example std::vector does. Thus, trying to store objects without a default constructor in a multi_array results in hard compiler errors, with no workaround that I know of. This happens to me fairly often, as I use multi_array to organize sets of complex objects. If there is a technical reason why this is not possible, I would also be happy to learn it. Best regards, Eugenio Bargiacchi

2 2

[xpressive] I got a crash in after i upgrade from 1.44 to 1.74
by forston_shi＠trendmicro.com 20 Nov '20

20 Nov '20

Hi Boost Users I met a crash in following code after I upgrade from 1.44 to 1.74, When I used "-O1 -DNDEBUG" to compile, it will crash. But when I used "-O1" or "-DNDEBUG" or "-O0 -DNDEBUG", it will not crash. In 1.44, all of them are ok. My GCC version is 4.1.2 and test in redhat-AS 4 32 bit. callstack #0 at ./boost_1_74_0_bk/boost/xpressive/detail/static/transmogrify.hpp:160 160 char const *name_end = m.name_ + std::strlen(m.name_); #1 at ./boost_1_74_0_bk/boost/proto/transform/detail/preprocessed/fold_impl.hpp:80 #2 at ./boost_1_74_0_bk/boost/proto/transform/detail/preprocessed/fold_impl.hpp:80 #3 at ./boost_1_74_0_bk/boost/xpressive/detail/static/compile.hpp:79 #4 at ./boost_1_74_0_bk/boost/xpressive/detail/static/compile.hpp:99 #5 0x08049d5f in main () at ./boost_1_74_0_bk/boost/xpressive/basic_regex.hpp:252 Can you help to check this problem? Best regards Forston callstack Following is source code. #include <boost/xpressive/basic_regex.hpp> #include <boost/xpressive/regex_primitives.hpp> #include <boost/xpressive/match_results.hpp> #include <boost/xpressive/regex_algorithms.hpp> int main(int argc, char* argv[]) { std::wstring uri_string = L"https://192.168.1.1/test"; printf("begin regex_match %ls \n ", uri_string.c_str()); using namespace boost::xpressive; static wsregex const uri_regex = bos >> (s1 = (alpha >> *(alnum | L'+' | L'-' | L'.'))) >> L"://" >> (s2 = *(alnum | L'-' | L'.' | L':' | L'@' | L'[' | L']' | L'_')) >> !(as_xpr(L'/') >> (s3 = (*_))) >> eos ; wsmatch result; try { if (!regex_match(uri_string, result, uri_regex)) { printf( "regex_match failed %ls \n ", uri_string.c_str()); return -1; } } catch (std::exception& e) { printf("regex_match failed %ls \n ", uri_string.c_str()); return -1; } printf("end regex_match success %ls \n ", uri_string.c_str()); return 0; } TREND MICRO EMAIL NOTICE The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. For details about what personal information we collect and why, please see our Privacy Notice on our website at: Read privacy policy<http://www.trendmicro.com/privacy>

1 0

[asio] Prevent socket inheritance on Windows
by Klebsch, Mario 17 Nov '20

17 Nov '20

Hello everybody, I am using boost as communication framework in a library for Windows. I am getting problems, when the client code, that uses our library, creates windows processes and inherits handles, e.g. by using popen(). I currently observing two problems. 1. Even though my library has closed the socket, the peer keeps an active connection. 2. When there is a pending async read operation, calling close() does not lead to the read handler being invoked with an error. My library closes a socket in its shutdown process and because it also terminates the io_service during shutdown, it waits for the termination of the pending read operation. The second problem is the one, that is visible to the client, since our library hands during shutdown. Unfortunately it is not triggered by just inheriting a socket handle to a child process. I know, the socket handle gets inherited to the child process and when I kill the child process, the pending async operation terminates. I also have seen the pending read operation to terminate, then the peer system sends some data. The data seems to be read fine, although the socket has already been closed by our library. The io_service is blocked in the call to GetQueuedCompletionStatus() on its io completion port. It seems, the io completion port still is linked the the socket, although the socket has been closed. The problem is triggered reliably, when using my fully integrated library, but I have not yet managed to write a small simple sand alone program to demonstrate this problem. * Does anybody on this mailing list has a clue, what may cause the 2nd problem, where the async operation does not terminate upon closing the socket. * Does anybody know of a reliable way to prevent an asio socket from being inherited. I found some web pages mentioning WSA_FLAG_NO_HANDLE_INHERIT, but have not found a way to get boots to use this flag other than patching my boost source code. Thanks to everybody, 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 Germany

1 0

[release] Boost 1.74.0 beta 1 released
by Marshall Clow 14 Nov '20

14 Nov '20

Boost release 1.75.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.75.0.beta1/source/> The SHA256 checksums are as follows: 3f01d3e5dc822e151892040d4667e364ea808d208d2e49cc7a1802bd4da3d4cc boost_1_75_0_b1.7z 9b75a80f845d4ae312e3c9151ffdfe3fed450973095e0a15c68d0be394f2f2df boost_1_75_0_b1.tar.bz2 123519d4b056fbbd69e452db880abe2c7e55f21779d44a4d6b6c714d5c13c3ee boost_1_75_0_b1.tar.gz b73e01d22d5b3d2ff82f14a371e3974fab30448bf6ff5ac8b9c829539a19c2d7 boost_1_75_0_b1.zip For details of what's in the release, see <https://www.boost.org/users/history/version_1_75_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

1 0

[release] Boost 1.75.0 Beta 1 Release Candidate 2
by Marshall Clow 13 Nov '20

13 Nov '20

The second release candidates for the 1.75.0 beta release are now available at: <https://dl.bintray.com/boostorg/beta/1.75.0.beta1/source/> The SHA256 checksums are as follows: 3f01d3e5dc822e151892040d4667e364ea808d208d2e49cc7a1802bd4da3d4cc boost_1_75_0_b1_rc2.7z 9b75a80f845d4ae312e3c9151ffdfe3fed450973095e0a15c68d0be394f2f2df boost_1_75_0_b1_rc2.tar.bz2 123519d4b056fbbd69e452db880abe2c7e55f21779d44a4d6b6c714d5c13c3ee boost_1_75_0_b1_rc2.tar.gz b73e01d22d5b3d2ff82f14a371e3974fab30448bf6ff5ac8b9c829539a19c2d7 boost_1_75_0_b1_rc2.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

3 5

Compile issues when cross compiling for iOS with external dependencies
by Ardavon Falls 10 Nov '20

10 Nov '20

When attempting to cross-compile boost 1.69.0 for iOS (with clang) and using external dependencies it fails to compile because when it tests to see if the dependencies are valid, it fails to compile the test program correctly due to it attempting to add incorrect linker flags. I tried modifying the boost.build to not add those flags but it seemed to unravel a rat's nest of issues (attempting to link with librt even though its for iOS, compiled the test program for x86 and not arm, etc.., etc..) The error I keep getting is... ld: unknown option: --start-group Thank you for your help. I am using the following b2 options.. ./b2 --prefix=/Users/afalls/delete-me/build-boost/install/ \ --build-dir=/Users/afalls/delete-me/build-boost/build/ \ --user-config=/Users/afalls/delete-me/build-boost/ios-config.jam \ --with-math \ --with-wave \ --with-container \ --with-contract \ --with-exception \ --with-graph \ --with-iostreams \ --with-locale \ --with-log \ --with-program_options \ --with-random \ --with-regex \ --with-mpi \ --with-serialization \ --with-coroutine \ --with-fiber \ --with-context \ --with-timer \ --with-thread \ --with-chrono \ --with-date_time \ --with-atomic \ --with-filesystem \ --with-system \ --with-graph_parallel \ --with-stacktrace \ --with-test \ --with-type_erasure \ -q \ -j 16 \ toolset=clang \ threading=multi \ architecture=arm \ abi=aapcs \ binary-format=mach-o \ address-model=64 \ cxxflags="${IOS_CXXFLAGS}" \ cflags="${IOS_CFLAGS}" \ target-os=iphone \ link=static \ variant=release \ define=_LITTLE_ENDIAN \ install My user-config.jam file is below... import os ; using clang : : /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -arch arm64 -DBOOST_AC_USE_PTHREADS -DBOOST_SP_USE_PTHREADS -Wno-unused-local-typedef -Wno-nullability-completeness -miphoneos-version-min=9.0 -fPIC : <stripper> <root>/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk <architecture>arm <target-os>iphone <include>/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/usr/include ; using zlib : 1.2.11 : <include>/Users/afalls/.conan/data/zlib/1.2.11/channel/niantic/package/d522642044ded35b1d89ab2201a41e2c5d74a0b0/include <search>/Users/afalls/.conan/data/zlib/1.2.11/channel/niantic/package/d522642044ded35b1d89ab2201a41e2c5d74a0b0/lib <name>z ; using lzma : 5.2.4 : <include>/Users/afalls/.conan/data/xz_utils/5.2.4/channel/niantic/package/d522642044ded35b1d89ab2201a41e2c5d74a0b0/include <search>/Users/afalls/.conan/data/xz_utils/5.2.4/channel/niantic/package/d522642044ded35b1d89ab2201a41e2c5d74a0b0/lib <name>lzma ; using bzip2 : 1.0.8 : <include>/Users/afalls/.conan/data/bzip2/1.0.8/channel/niantic/package/d522642044ded35b1d89ab2201a41e2c5d74a0b0/include <search>/Users/afalls/.conan/data/bzip2/1.0.8/channel/niantic/package/d522642044ded35b1d89ab2201a41e2c5d74a0b0/lib <name>bz2 ; using zstd : 1.4.4 : <include>/Users/afalls/.conan/data/zstd/1.4.4/channel/niantic/package/d522642044ded35b1d89ab2201a41e2c5d74a0b0/include <search>/Users/afalls/.conan/data/zstd/1.4.4/channel/niantic/package/d522642044ded35b1d89ab2201a41e2c5d74a0b0/lib <name>zstd ;

1 0

Boost version not matching according to the manual
by Arnab Chaudhuri 08 Nov '20

08 Nov '20

To whom it may concern, I have installed boost and to the version is 1.65.1.0ubuntu1 . It is written while installing that the minimum requirement is 1.66. Can you please tell me how to update my version. The commands I used to install boost are as follows: *sudo apt install libboost-dev**sudo apt install libboost-all-dev* *Thanking you,* *Arnab Chaudhuri.*

1 0

Validating downloads on Windows
by Kenneth Porter 08 Nov '20

08 Nov '20

I thought I had a corrupted download and wanted to relate my experience on how to validate the zip file downloads on Windows. The Boost archives (tar, zip, etc.) all have a matching small .json file that contains a SHA256 hash of the archive file. Under Windows 10, you can use certutil.exe from a command line to compute the hash for the archive and compare it to the value in the .json file: C:\Users\ken\Downloads>certutil -hashfile boost_1_75_0_b1_rc1.zip SHA256 SHA256 hash of boost_1_75_0_b1_rc1.zip: 07ddca7c39ea9152bad73bee4f10f2c9c8e3a2d7e153aa945a343f83eca5db59 CertUtil: -hashfile command completed successfully. (I thought my download was corrupted because I was using an ancient version (5.50) of InfoZip's unzip program and it was reporting errors. I updated to version 6 and it unpacked the same file just fine.)

1 0

[release] Boost 1.75.0 Beta 1 Release Candidate 1
by Marshall Clow 07 Nov '20

07 Nov '20

The first release candidates for the 1.75.0 beta release are now available at: <https://dl.bintray.com/boostorg/release/1.75.0.beta1/source/> The SHA256 checksums are as follows: c271f488c7c8de7c147bf8675d578fb2f06c6c171d9547c5a40cddccb9f2a6c4 boost_1_75_0_b1_rc1.7z 0db0944e9d2250907e011900eea304ca055d1c418d38b3fbb1eee692a6b851a6 boost_1_75_0_b1_rc1.tar.bz2 624bd6b03d86bf1387b4e8927dab16b4198f255f15dd71d6a8c1c5ec270584b3 boost_1_75_0_b1_rc1.tar.gz 07ddca7c39ea9152bad73bee4f10f2c9c8e3a2d7e153aa945a343f83eca5db59 boost_1_75_0_b1_rc1.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

2 4

Why did ip::basic_resolver::query get depreciated in 1.66?
by Luke Knoble 06 Nov '20

06 Nov '20

I ask because I replaced its return value with an endpoint in a tcp resolver function and my dns resolution started working..! Cheers, Luke Knoble

1 0