- Boost - lists.boost.org

Re: [boost] C++Now 2021 -- Library in a Week: Boosting Boost
by Bjorn Reese 02 May '21

02 May '21

On 2021-05-01 00:55, Jeff Garland via Boost wrote: > Every year at the end of the session, I solicit ideas from the community > about what 'library' we should work on in the following year. One Boost.Tokenizer could do with a modernization. It generates a lot of code for even simple tokenizations, which makes it unsuitable for embedded devices. Some issues to consider: * Separate the browsing API from the conversion API. ** The browsing API should use string_view. ** The conversion API should use output buffers instead of returing a string. * Provide an API with narrow contracts * Provide a constexpr API.

2 2

C++Now 2021 -- Library in a Week: Boosting Boost
by Jeff Garland 01 May '21

01 May '21

C++Now 2021 is next week. For those that have never been, every year we have a workshop session called Library in a Week. While the goal of the session might be obvious from the title, needless to say, final Boost libraries don't happen in a week. So, actually, the real underlying goal is to build boost community and discuss c++ library design with projects that don't conflict with attendees day jobs. Every year at the end of the session, I solicit ideas from the community about what 'library' we should work on in the following year. One consistent suggestion has been to work on boost community maintenance. With the conference all virtual this year, I think this is the year to do it. The goal will be to generate pull requests from new or even old boost participants to improve our code base. While I'm sure we could wander around the various libraries and find issues that need some work to generate pull requests, I'm posting this looking for suggestions from the bigger community. Note that this doesn't need to be exclusive to new code -- it can be documentation or tests. Are there particular libraries we should look at? Are there particular issues that someone would like a hand tackling? Are there some upgrades to newer c++ features that someone could jump in on? Thanks, Jeff

2 2

Boost N-Dimensional Array Library
by pencilcaseman＠gmail.com 28 Apr '21

28 Apr '21

Hi All, Would there be any interest in an n-dimensional array library for boost? There is Boost.MultiArray library, but as far as I can tell, this only supports containing the arrays, not performing arithmetic on them. It would provide an interface similar to what Numpy provides, would be fully templated and might, if possible, support BLAS routines to accelerate the functions. Thanks, Toby

2 2

[ci][security] Codecov security breach
by Andrey Semashev 27 Apr '21

27 Apr '21

Hi, I found this in my news feed today: The codecov-bash script that is used to upload codecov reports from CI to codecov.io was maliciously modified to collect sensitive information and send to a third party server. Things like private keys, credentials, auth tokens used in the CI might be compromised. https://discuss.hashicorp.com/t/hcsec-2021-12-codecov-security-event-and-ha… https://about.codecov.io/security-update/ I'm not using codecov, and I have vague understanding how it works, but I've seen it used in Boost libraries' CI. I don't know if they are affected, this is an FYI to the maintainers.

1 0

Fwd: [BOOST][GIL][Histogram]Ordered Maps in place of unordered maps
by sayan chaudhuri 26 Apr '21

26 Apr '21

---------- Forwarded message --------- From: sayan chaudhuri <sayanchaudhuri758(a)gmail.com> Date: Sat, Apr 24, 2021 at 3:08 PM Subject: [BOOST][GIL][Histogram]Ordered Maps in place of unordered maps To: <boost-gil(a)lists.boost.org> Dear Matseuz, The histogram implemented in boost gil uses an unordered map.Wont it have been better with an ordered map? Because the worst case time complexity is better in case of ordered maps. Regards, Yours sincerely, Sayan Chaudhuri

3 2

[Boost][Multiarray]Move for_each.hpp from examples to boost/multi_array
by sayan chaudhuri 25 Apr '21

25 Apr '21

Hello Everyone, I wish to draw attention to the fact that the for_each header file for multiarrays in boost is not present in the include/boost section of the boost multiarray repository. Also, the header file does not have a namespace defined inside it and so the compiler becomes confused as to which for_each function to follow, the one from stl or this one. The for_each is a great utility for boost multiarrays reducing code size and increasing readability. I would like to what others would like to say about these changes. Making these changes allows contributors to other boost libraries to use that functionality in a proper manner. Thanking everyone, Yours sincerely, Sayan Chaudhuri

1 0

[iostreams] [build] Why do iostream tests link against static libraries ?
by Brian Kuhl 22 Apr '21

22 Apr '21

Cross-posting since boost-build is quiet these days. I’m trying to get iostreams working with shared libraries on VxWorks The tests will compile with clang 11 if I comment out the forced dependency on static libraries But I’d like to understand the reason for forcing a link of static libraries with a dynamic executable? https://github.com/boostorg/iostreams/blob/4d2e763ba8b88f3350fbea29b54507a3… rule test-iostreams ( sources * : requirements * : target-name ? ) { return [ run $(sources) /boost/test//boost_unit_test_framework # /<link>static /boost/filesystem//boost_filesystem # /<link>static : # command : # input files : # build requirements <toolset>msvc:<define>_CRT_SECURE_NO_DEPRECATE <toolset>msvc:<define>_SCL_SECURE_NO_DEPRECATE <toolset>cw-9.3,<os>darwin:<runtime-link>static <define>BOOST_IOSTREAMS_NO_LIB <link>shared:<define>BOOST_IOSTREAMS_DYN_LINK=1 $(requirements) : $(target-name) ] ; } If I don’t comment, I get a link error. VxWorks only supports -fpic vs -fPIC clang-vxworks.compile.c++ ../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/unit_test_parameters.o "wr-c++" -x c++ -Wno-c99-extensions -Wno-variadic-macros -O3 -finline-functions -Wno-inline -Wall -pedantic -g -Wno-inline -DBOOST_ALL_NO_LIB=1 -DBOOST_BEAST_ALLOW_DEPRECATED -DBOOST_BEAST_SEPARATE_COMPILATION -I".." -c -o "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/unit_test_parameters.o" "../libs/test/src/unit_test_parameters.cpp" clang-vxworks.archive ../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/libboost_unit_test_framework.a "wr-ar" rcu "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/libboost_unit_test_framework.a" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/compiler_log_formatter.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/debug.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/decorator.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/execution_monitor.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/framework.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/plain_report_formatter.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/progress_monitor.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/results_collector.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/results_reporter.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/test_framework_init_observer.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/test_tools.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/test_tree.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/unit_test_log.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/unit_test_main.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/unit_test_monitor.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/unit_test_parameters.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/junit_log_formatter.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/xml_log_formatter.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/xml_report_formatter.o" clang-vxworks.link ../bin.v2/libs/iostreams/test/array_test.test/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/array_test.vxe "wr-c++" -o "../bin.v2/libs/iostreams/test/array_test.test/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/array_test.vxe" "../bin.v2/libs/iostreams/test/array_test.test/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/array_test.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/libboost_unit_test_framework.a" "../bin.v2/libs/filesystem/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/libboost_filesystem.a" -shared --start-group --end-group -fpic /opt/git/vx7/compilers/llvm-11.0.0.1/LINUX64/bin/ldarm: ../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/libboost_unit_test_framework.a(test_tools.o): relocation R_ARM_MOVW_ABS_NC against `a local symbol' can not be used when making a shared object; recompile with -fPIC /opt/git/vx7/compilers/llvm-11.0.0.1/LINUX64/bin/ldarm: ../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/libboost_unit_test_framework.a(test_tree.o): relocation R_ARM_MOVW_ABS_NC against `a local symbol' can not be used when making a shared object; recompile with -fPIC

1 0

Reminder: BinTray is shutting down 1-May
by Marshall Clow 21 Apr '21

21 Apr '21

Bintray is “sunsetting” on the 1st of May. At that time, you will be unable to download boost releases from there. Before that time, their service will be occasionally interrupted. We will be updating the web site before then, but the new location is: https://boostorg.jfrog.io/artifactory/main/release/ <https://boostorg.jfrog.io/artifactory/main/release/> So instead of downloading from: https://dl.bintray.com/boostorg/release/1.76.0/source/boost_1_76_0.tar.gz You should download from: https://boostorg.jfrog.io/artifactory/main/release/1.76.0/source/boost_1_76… This applies to all releases from 1.63.0 onward — Marshall

1 0

Master branch now open for merging
by Marshall Clow 19 Apr '21

19 Apr '21

No restrictions; the release calendar is up to date. https://boost.org/development <https://boost.org/development> Next milestone: 23-Jun Boost 1.77.0 closed for new libraries and breaking changes — Marshall

1 0

Re: [boost] [Boost-users] [release] Boost 1.76.0
by Glen Fernandes 17 Apr '21

17 Apr '21

On Fri, Apr 16, 2021 at 7:28 PM Edward Diener wrote: > I noticed on the main web page where it has under > "News" the "Version 1.76.0" that "Updated Libraries:" list nothing even > though there are plenty of updates for libraries at > https://www.boost.org/users/history/version_1_76_0.html. The fix for this has been committed; it should take effect automatically in about an hour or so. Glen

1 0