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

Boost 1.75.0 Release Candidate 1 -- macOS (gcc 10.2.0)
by DV Henkel-Wallace 10 Dec '20

10 Dec '20

> Date: Thu, 3 Dec 2020 06:54:13 -0800 > From: Marshall Clow <mclow.lists(a)gmail.com <mailto:mclow.lists@gmail.com>> > > [release] Boost 1.75.0 Release Candidate 1 > Built fine on macOS 11.0.1 using brew-installed g++-10 ./b2 cxxstd=2a boost.locale.icu=off boost.locale.std=off threading=multi -sNO_COMPRESSION=1 Darwin KA-19.local 20.1.0 Darwin Kernel Version 20.1.0: Sat Oct 31 00:07:11 PDT 2020; root:xnu-7195.50.7~2/RELEASE_X86_64 x86_64 gcc version 10.2.0 (Homebrew GCC 10.2.0) Target: x86_64-apple-darwin19 Lots of deprecated warnings for #pragma GCC diagnostic ignored "-Wdeprecated-copy", use of boost/bind.hpp and boost/detail/iterator.hpp. But otherwise OK. Net: Apple's clang and g++ generated pretty similar warnings. Clang-11 did not.

1 0

Boost 1.75.0 Release Candidate 1 -- macOS (system compiler)
by DV Henkel-Wallace 10 Dec '20

10 Dec '20

> Date: Thu, 3 Dec 2020 06:54:13 -0800 > From: Marshall Clow <mclow.lists(a)gmail.com <mailto:mclow.lists@gmail.com>> > > [release] Boost 1.75.0 Release Candidate 1 > Built fine on macOS 11.0.1 using the system compiler installed with latest Xcode (12.2) ./b2 cxxstd=2a boost.locale.icu=off boost.locale.std=off threading=multi -sNO_COMPRESSION=1 Darwin KA-19.local 20.1.0 Darwin Kernel Version 20.1.0: Sat Oct 31 00:07:11 PDT 2020; root:xnu-7195.50.7~2/RELEASE_X86_64 x86_64 Apple clang version 12.0.0 (clang-1200.0.32.27) Target: x86_64-apple-darwin20.1.0 Lots of deprecated warnings for #pragma GCC diagnostic ignored "-Wdeprecated-copy", use of boost/bind.hpp and boost/detail/iterator.hpp. But otherwise OK.

1 0

Boost 1.75.0 Release Candidate 1 -- macOS
by DV Henkel-Wallace 10 Dec '20

10 Dec '20

> Date: Thu, 3 Dec 2020 06:54:13 -0800 > From: Marshall Clow <mclow.lists(a)gmail.com <mailto:mclow.lists@gmail.com>> > > > [release] Boost 1.75.0 Release Candidate 1 > Built fine on macOS 11.0.1 using llvm 11.0.0 ./b2 cxxstd=2a boost.locale.icu=off boost.locale.std=off threading=multi -sNO_COMPRESSION=1 Darwin KA-19.local 20.1.0 Darwin Kernel Version 20.1.0: Sat Oct 31 00:07:11 PDT 2020; root:xnu-7195.50.7~2/RELEASE_X86_64 x86_64 clang version 11.0.0 Target: x86_64-apple-darwin20.1.0 Lots of deprecated warnings for use of boost/bind.hpp and boost/detail/iterator.hpp as well as using enums as bitfields. But otherwise OK.

2 1

QT MinGW32 : bootstrap stacktrace (header only) not showing function names and lines numbers shows only address
by Mehdi Est 05 Dec '20

05 Dec '20

Hi Everyone, I am trying to print stack-trace using boost *HEADER-ONLY. *I am using descriptions under Configuration and Build <https://www.boost.org/doc/libs/1_74_0/doc/html/stacktrace/configuration_and…> to compile a simple code using QT MinGW32 I also use the below macros to tune boost: -DBOOST_STACKTRACE_USE_WINDBG -DBOOST_STACKTRACE_USE_ADDR2LINE -DBOOST_STACKTRACE_ADDR2LINE_LOCATION I have no clue why the function names and line numbers are not showing up. Any comment is appreciated. Mike *Below are compile and build instructions:* g++ -g3 -DBOOST_STACKTRACE_USE_WINDBG -DBOOST_STACKTRACE_USE_ADDR2LINE -DBOOST_STACKTRACE_ADDR2LINE_LOCATION=C:\Qt_5_12\Tools\mingw730_32\bin\addr2line.exe -I../../../boost_1_73_0 -c main.cpp -omain.o g++ main.o -o stack_traces.exe -L"C:\Program Files (x86)\Windows Kits\10\Lib\10.0.19041.0\um\x86" -L"C:\temp\libbacktrace" -lkernel32 -luser32 -lgdi32 -lwinspool -lcomdlg32 -ladvapi32 -lshell32 -lole32 -luuid -lodbc32 -lodbccp32 -lDbgEng *And here is the output ... * 0# 0x00402C75 in stack_traces 1# 0x00401602 in stack_traces 2# 0x004016CE in stack_traces 3# 0x0040138B in stack_traces 4# _BaseThreadInitThunk in KERNEL32 5# _RtlGetAppContainerNamedObjectPath in ntdll 6# _RtlGetAppContainerNamedObjectPath in ntdll 1 + 2 = 3 *The code (main.cpp)* Is fairly simple as below: #include <iostream> #include <boost/stacktrace.hpp> double add(double a, double b){ std::cout << boost::stacktrace::stacktrace(); std::cout << a << " + " << b << " = " << (a+b) << std::endl; return a+b; } int main(){ add(1,2); return 0; }

2 2

[release] Boost 1.75.0 Release Candidate 1
by Marshall Clow 04 Dec '20

04 Dec '20

[release] Boost 1.75.0 Release Candidate 1 The first release candidates for the 1.75.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.75.0/source/> The SHA256 checksums are as follows: caf36d7c13b3d8ce62282a64a695113945a13b0f1796a45160726d04295f95ed boost_1_75_0_rc1.zip aeb26f80e80945e82ee93e5939baebdca47b9dee80a07d3144be1e1a6a66dd6a boost_1_75_0_rc1.tar.gz 953db31e016db7bb207f11432bef7df100516eeb746843fa0486a222e3fd49cb boost_1_75_0_rc1.tar.bz2 3a8b314871646e7404886736273c053278ba71b11347f72d4751411d65d6d1a5 boost_1_75_0_rc1.7z 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 4

Boost.Numeric.Interval: Please specify rounding control mechanism
by Bastien Commelongue 01 Dec '20

01 Dec '20

Hello, I am building an app for IOS (ARM) and I had this issue while compiling: *Boost.Numeric.Interval: Please specify rounding control mechanism.* C99 version should be used in this case but __USE_ISOC99 is not defined. Modifying the condition with this code (using __cplusplus) fixed the issue: *boost/numeric/interval/hw_rounding.hpp(36)* *#if defined(BOOST_NUMERIC_INTERVAL_NO_HARDWARE) && (defined(__USE_ISOC99) || defined(__MSL__) || (defined __cplusplus && __cplusplus >= 201103L))# include <boost/numeric/interval/detail/c99_rounding_control.hpp>#endif* Let me know if I missed something or if you plan to integrate this modification in a next version. Cheers, Bastien Commelongue

2 1

PolyCollection
by Brian Wood 30 Nov '20

30 Nov '20

Shalom Hey, is anyone using PolyCollection? I have serialization support for it: https://github.com/Ebenezer-group/onwards/tree/master/example/poly If you considered it, but chose an alternative library, what was the reason? Thanks. Brian Ebenezer Enterprises - Enjoying programming again. https://webEbenezer.net

1 0

Re: [Boost-users] [multi_array] Feature request: constructor and resize from values
by DV Henkel-Wallace 30 Nov '20

30 Nov '20

If an object does not have a default constructor what could it mean to have a block of memory holding one that has not been initialized? How would your program know if the object had been properly initialized or not? There are three ways to address this: 1 - A pointer, as already mentioned. A null pointer means the spot does not refer to ("contain") a valid object -- or any object at all. 2 - use a variant 3 - create a default constructor (which you could do by changing the signature of your constructor to something like (int = 0) or (int = -1) assuming those values are invalid). In all cases, regardless of semantics or implementation you'll either have to check at runtime for a valid object OR, if you know for other reasons which locations are valid, use the default constructor with any value you'd like. If you don't want to use pointers there are a couple of other possibilities: > > Date: Sun, 22 Nov 2020 12:06:04 +0100 > From: Eugenio Bargiacchi <svalorzen(a)gmail.com <mailto:svalorzen@gmail.com>> > > Ah, sorry, I thought it would have been automatically clear. Consider this > example: > > class A { > public: > A(int) {} > }; > > boost::multi_array<A,2> array(boost::extents[2][2]); // Compiler error > boost::multi_array<A,2> array(boost::extents[2][2], A(3)); // What I would > like > > array.resize(boost::extents[2][2]); // Again, compiler error > array.resize(boost::extents[2][2], A(2)); // What I would like > > The variable `array` cannot be constructed in any way, as multi_array will > try to default-construct it, and that will fail. Trying to simply create > `array` with its default constructor works (although it will obviously be a > zero-sized array), but when trying to resize it (to actually store things), > the same thing will happen.

2 1

[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