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

A new home for Boost releases
by Marshall Clow 12 Apr '21

12 Apr '21

We’ve been using BinTray to host our releases for a few years, and it’s worked well for us However, JFrog is shutting down BinTray soon (at the end of this month). We have moved all the releases that were hosted on BinTray over to JFrog Artifactory. They are at https://boostorg.jfrog.io/artifactory/main/release <https://boostorg.jfrog.io/artifactory/main/release> For example, instead of: https://dl.bintray.com/boostorg/release/1.74.0/source/boost_1_74_0.tar.gz <https://dl.bintray.com/boostorg/release/1.74.0/source/boost_1_74_0.tar.gz> You should now use: https://boostorg.jfrog.io/artifactory/main/release/1.74.0/source/boost_1_74… <https://boostorg.jfrog.io/artifactory/main/release/1.74.0/source/boost_1_74…> I’ll be updating the web site soon, but if you have automation that relies on BinTray, you should update it to use the new home. — Marshall P.S. The “nightly” snapshots will live there too, as soon as we get that set up.

1 0

[release] Boost 1.76.0 Release Candidate 1
by Marshall Clow 10 Apr '21

10 Apr '21

IMPORTANT NOTE: This will be the last RC posted on BinTray! The first release candidates for the 1.76.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.76.0/source/> The SHA256 checksums are as follows: aaf920e31ae815ff6b55d70a28bb614a6aa6f5cd2f6e4543461d20a4fe39df4e boost_1_76_0_rc1.7z 5dd0c91e1f0f18d452fcaa772d9c30815e449dd4fe99fadf224cca180d98cee3 boost_1_76_0_rc1.zip 5b9844335bc327272030b8050cf417178d26c8abbc64ed7aefc4d818facc1c10 boost_1_76_0_rc1.tar.gz cea1cf7609daf5bb285a625530e8d660dca51816007da7f5eb3f577b685a888d boost_1_76_0_rc1.tar.bz2 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 2

Multiprecision
by shady mohamed 09 Apr '21

09 Apr '21

I need to talk with mentor of this project to discuss the competency test

2 1

does boost::variant support 128 bit integer?
by David Frank 09 Apr '21

09 Apr '21

especially the gnu __int128?Thanks,David.

6 16

Multiprecision
by shady mohamed 07 Apr '21

07 Apr '21

I need to understand the competency test of multiprecision project

1 0

select_stdlib_config.hpp and <version> 1.73
by Allen Sanderson 05 Apr '21

05 Apr '21

Hello, A casual boost user and abuser here. Some specifics on my OS OS X Big Sur 11.2 Xcode 12.4 Compiler clang : Apple land version 12.0.0 Boost 1.73 - forward When select_stdlib_config.hpp is included it gets to this initial code to include the file “version" ... #if defined(__cplusplus) && defined(__has_include) # if __has_include(<version>) // It should be safe to include `<version>` when it is present without checking // the actual C++ language version as it consists solely of macro definitions. // [version.syn] p1: The header <version> supplies implementation-dependent // information about the C++ standard library (e.g., version number and release date). # include <version> ... The issue is that many projects have a file “VERSION” in their top level src directory. On a traditional Linux system the case sensitivity would make sure the right file is included. However, many/most OS X file systems are case insensitive. As such, the file VERSION gets included instead. And does not compile. I have no solution to the issue but wanted to raise it. Cheers, Allen Sanderson SCI Institute University of Utah

1 0

std::any serialization
by Isaac Lascasas 04 Apr '21

04 Apr '21

Hello, I wonder if there is a workaround to serialize std::any objects. I want to replace some old code that had similar functionality and all the types were registered via BOOST_CLASS_EXPORT_GUID. Regards.

1 0

Tried to unzip a file , and followed the example in the boost.org as well, but it doesn't work
by asfskfdjkj kfasjfkasjf 03 Apr '21

03 Apr '21

Hi guys I tried to unzip a file with code below which exactly like the example from boost.org, but it doesn't work the example is in the link which is Zlib Filters | | | | Zlib Filters | | | I tried the code like the below try{ ifstream file("d:\\202012303333629003180526491.txt.zip", ios_base::in | ios_base::binary); boost::iostreams::filtering_streambuf<boost::iostreams::input> in; in.push(boost::iostreams::zlib_decompressor()); in.push(file); boost::iostreams::copy(in, cout); return 0;}catch (const std::exception& error) { std::cerr << error.what() << std::endl; return (EXIT_FAILURE); } it's not working, it get exception when it excuted boost::iostreams::copy(in, cout); I got the zlib error: iostream stream error exception thoughwhat wrong I have done though? thank you

2 2

[Spirit] [Fusion] Concise way to construct attribute object
by Phil Endecott 28 Mar '21

28 Mar '21

Dear Experts, I currently have something like: struct S { string name; string value; }; BOOST_FUSION_ADAPT_STRUCT( S, name, value ) using S_rule = qi::rule<ITER, skipper, S()>; S_rule r %= identifier >> lit(':') >> identifier; Note that I can use %= here and I don't need to write an explicit semantic action to assign to S. Now say I modify S: class S { public: S(string name_, string value_); // May be default-constructable, copyable, assignable etc. // - but name and value are not individually assignable. }; Question: what is the best way to use that with the qi parser rule? I was hoping to find something in Fusion that would allow me to adapt the new class so that it can be used with %= as before, but I don't see anything appropriate. Currently the best that I can think of is: S_rule r = ( identifier >> lit(':') >> identifier ) [ _val = boost::phoenix::construct<S>(_1,_2) ]; How can I improve on that? Thanks, Phil.

1 0

[Core] scoped_enum and template arguments
by Alan Barr 24 Mar '21

24 Mar '21

Hi, I'm a little confused about the following statement in the docs for scoped enum: > The emulated scoped enum can not be used in switch nor in > template arguments. https://www.boost.org/doc/libs/1_75_0/libs/core/doc/html/core/scoped_enum.h… I understand the rationale for the switch statement part (and indeed it won't compile in C++03). However, I'm struggling to grasp the template argument part (and I'll be the first to admit I'm not particularly strong with templates). Unlike the switch case, any basic scenario I've thrown at it compiles. So I'm not sure if this is a case of "should not" vs "can not". When would using a "scoped_enum_type" in a template argument as opposed to "BOOST_SCOPED_ENUM_NATIVE(scoped_enum_type)" become a problem? Or, why should I use "boost::optional<BOOST_SCOPED_ENUM_NATIVE(future_errc)>" over "boost::optional<future_errc>" ? I've got a compiler explorer link with some test code here if it helps: https://godbolt.org/z/dfr6M6vrW Regards, Alan

1 0