November 2021 - Boost - lists.boost.org

conversion of catched exception to shared_ptr
by rajesh daggumati 08 Nov '21

08 Nov '21

rajesh daggumati <rajeshdaggumati9999(a)gmail.com> 09:59 (4 hours ago) to boost-users HI, please help me to solve below issue. Shared pointers are used in my code. class Exception : public virtual std::exception,public virtual boost::exception { --- }; class ExceptionTestException : public Exception { --- }; boost::shared_ptr<Exception> exceptionptr_t; try { Boost_Throw_function(ExceptionTestException("Hiii")); } catch(...) { boost::exception_ptr exceptionptr = boost::current_exception(); try { boost::rethrow(exceptionptr) } catch(boost::exception &e) { //here i need to assign this 'e' to shared pointer but this e is not in heap so then how to assign this e to sharedptr(exceptionptr_t). 1 way is : boost::exception *ep = new ExceptionTestException(e); exceptionptr_t(ep); here we know that exception_ptr is having ExceptionTestException but in some cases, we dont know which type of excepiton we have in exception_ptr in runtime. then how to assign to shared_ptr

4 4

Library category error handling
by Emil Dotchevski 07 Nov '21

07 Nov '21

Should we add a formal category for error handling libraries in https://www.boost.org/development/library_metadata.html?

5 6

Does boost have a way to get type name at compile time?
by Ivan Matek 04 Nov '21

04 Nov '21

I am aware of hacks/magic with __PRETTY_FUNCTION__ <https://stackoverflow.com/questions/69624128/parameter-pack-sorting-or-equi…>but I wonder if there is a portable boost way to do that?

2 1

Header-only libraries linking to compiled libraries...
by Peter Dimov 03 Nov '21

03 Nov '21

... create problems (at least) for CMake users, because a project using a header-only library must link to its compiled dependencies by hand. (Important Note: this is not about the CMake build of Boost. It's about the b2 build of Boost, and the CMake configuration files it generates.) Compiled libraries don't have this problem, because they have CMake targets, and linking to the library target automatically links to the dependencies. For instance, linking to Boost::filesystem would automatically link to Boost::atomic (and on Windows, to bcrypt.lib) as needed. However, as pointed out in https://github.com/boostorg/boost_install/issues/54, header-only libraries such as Process or UUID have no CMake targets. Consequently, it's not possible for the CMake project to link to Boost::uuid and automatically inherit the dependency to bcrypt.lib, or to link to Boost::process and automatically acquire a dependency to Boost::filesystem. Since the CMake configuration files that are generated by `b2 install` define CMake targets based on the b2 targets, it's not possible to fix this just on the boost-install side. If we want Boost::process to appear as a target in CMake, we need boost_process to appear as a target in b2, that is, we need libs/process/build/Jamfile to exist. The easiest way to fix it - if we decide to do something about it - is to create dummy compiled libraries for each such header-only library that isn't really header-only because of dependencies. A number of Boost libraries are already header-only with a stub library for backward compatibility (System, DateTime, Regex), so this wouldn't be something novel.

6 17

Reminder: The master branch will be closing for the 1.78.0 beta release TOMORROW
by Marshall Clow 03 Nov '21

03 Nov '21

If you have changes for the beta, they need to be merged to master before the end of day tomorrow. See https://www.boost.org/development/index.html <https://www.boost.org/development/index.html> for the full calendar — The Release managers

1 0

Boost libraries packaged for build2
by Boris Kolpackov 02 Nov '21

02 Nov '21

We have added support for the build2 build systems to 136 out of 145 Boost libraries and version 1.77.0 is now available from the cppget.org package repository. For details, see: https://build2.org/blog/build2-boost.xhtml Folks on this mailing list may be particularly interested in the "Implementation Details" section where we go deeper into how this conversion was accomplished: https://build2.org/blog/build2-boost.xhtml#impl-details (There is also the README-DEV file in the repository linked from this section which has even more details.) Also, let me add that this is not a call to convert Boost to build2. While we would gladly assist with this effort if the Boost community so wishes, we are also happy to continue our work out of tree.

1 0