- Boost - lists.preview.boost.org

Header-only Boost.System
by Ashish Singh 25 Oct '21

25 Oct '21

Hi All, In my application, I'm trying to use Boost ASIO via boost 1.66 and defining the following two macros in the Makefile. Basically trying to use the header-only approach. CFLAGS += \ -DBOOST_ERROR_CODE_HEADER_ONLY \ -DBOOST_SYSTEM_NO_DEPRECATED But then I came across this thread: https://lists.boost.org/Archives/boost/2017/10/239106.php "In header only mode, multiple instances may appear and thus no longer be proper singletons. Stuff breaks in this situation, badly." Is the above applicable to 1.66 too?How can I safely use the header-only approach in boost 1.66? Thanks,Ashish

2 8

Boost.URL: Something Wicked This Way Comes! (Was: Needs Review)
by Vinnie Falco 21 Oct '21

21 Oct '21

Folx: Well, I was on a pause but I picked Boost.URL back up and whipped it into shape. The good news, this Belle is ready for the Ball ! I invite you to kick the tires and light the fires on the next major component in my line of network and protocol libraries: Repository <https://github.com/CPPAlliance/url/> Documentation <https://master.url.cpp.al/> Docs are still being worked on, of course (docs are never "done"). `url_view`, `url`, `static_url`, and `authority_view` should be completely solid and ready to get beat up. And I'm ready for all that lovely negative feedback !!! If a kind soul would like to volunteer to be the review manager, that would be swell. I'm very happy to answer any questions about the library, and happy to get feedback regarding the design and implementation. -- Regards, Vinnie Follow me on GitHub: https://github.com/vinniefalco

12 79

Opinions on introduction of string_view in Core
by Andrey Semashev 21 Oct '21

21 Oct '21

Hi, Recently, a new implementation of string_view was introduced in Boost.Core: https://github.com/boostorg/core/blob/d5bd40e5280487fb29a108eb42e6c4f0bef69… Most of you probably know there is also a string_view implementation in Boost.Utility: https://github.com/boostorg/utility/blob/05e0d1688dcfcd3fdd65bdb6884b7edd1a… The main motivation for introducing the new implementation is adding conversions to/from std::string_view, which were proposed to Boost.Utility and rejected a while ago: https://github.com/boostorg/utility/pull/51 Another notable deviation of boost::core::string_view from std::string_view and boost::string_view is that it only accepts the character type in template parameters and not char_traits. This choice was made to simplify implementation. I have concerns that introducing yet another string_view type (3rd in Boost, after boost::string_ref and boost::string_view, not counting std::string_view) is not good for the ecosystem and interoperability, as this will require adding explicit support in some code bases. One example that I readilly have is Boost.Log: https://github.com/boostorg/log/blob/4c54e4ca4c31f18ce2e451e8d0abf88054242d… std::string_view was supposed to make user's code simpler by removing the need to provide a multitude of function overloads accepting string arguments. boost::string_view (and boost::string_ref before it) was a prototype implementation before introduction of std::string_view and served a similar purpose. In the age with std::string_view, boost::string_view is still useful as a drop-in replacement for std::string_view to lower C++ requirements in libraries and projects, like this: #if !defined(BOOST_NO_CXX17_HDR_STRING_VIEW) using std::basic_string_view; using std::string_view; using std::string_view; #else using boost::basic_string_view; using boost::string_view; using boost::string_view; #endif Introducing boost::core::string_view, which is not a drop-in replacement, does not make users' code simpler as it requires adding yet another set of overloads and specializations to users' APIs. I should stress that I'm not opposing because I don't want to make changes to Boost.Log, I'm opposing because I don't think those changes will be for the better, and because I view this as potentially destructive to the wide adoption of one common string_view type (be it std::string_view or boost::string_view, depending on the conventions taken in the project) to accept string arguments. Please, express your opinions on this matter, in particular: - Do you think it is good/ok/bad to have yet another string_view in Boost? - Is it ok that boost::core::string_view is not a drop-in replacement for std::string_view? Should it be changed to be one? - Should we, perhaps, do something with boost::string_view from Boost.Utility? Deprecate? - Should we reopen the discussion to add conversion to/from std::string_view to boost::string_view, which led to this fork? Perhaps, hold a vote to make this change as widely requested? - Any other course of action or thoughts? Thanks. PS: This post was made after an initial discussion in this commit: https://github.com/boostorg/core/commit/95924b1329da49e70c9c8485b87e066895d…

12 57

hash_value( complex<T> )
by Peter Dimov 19 Oct '21

19 Oct '21

At the moment, boost::hash_value for complex<T> is specified as When T is a built in type and val.imag() == 0, the result is equal to hash_value(val.real()). Otherwise an unspecified value, except that equal arguments shall yield the same result. This is a bit odd; the natural implementation for a two-argument point/tuple type is std::size_t seed = 0; boost::hash_combine( seed, v.real() ); boost::hash_combine( seed, v.imag() ); return seed; Can anyone offer an opinion on whether or why the original behavior is preferable?

3 6

regarding boost::exception
by rajesh daggumati 18 Oct '21

18 Oct '21

Hi Team, I need to create an object for catched exception . class exception: virtual public std::exception ,virtual public boost::exception {} inside my application code, try{ boost::rethrow_exception(exceptr)} catch(std::exception &e) { std::exception *e = stacktoHeapObject(e); } static std::exception* stacktoHeapObj(std::exception* e) { if (dynamic_cast<std::bad_alloc*>(e)) { return new std::bad_alloc(*(dynamic_cast<std::bad_alloc*>(e))); } else if (dynamic_cast<std::bad_cast*>(e)) { return new std::bad_cast(*(dynamic_cast<std::bad_cast*>(e))); } else if (dynamic_cast<std::bad_typeid*>(e)) { return new std::bad_typeid(*(dynamic_cast<std::bad_typeid*>(e))); } else if (dynamic_cast<std::bad_exception*>(e)) { return new std::bad_exception(*(dynamic_cast<std::bad_exception*>(e))); } else if (dynamic_cast<std::domain_error*>(e)) { return new std::domain_error(*(dynamic_cast<std::domain_error*>(e))); } else if (dynamic_cast<std::invalid_argument*>(e)) { return new std::invalid_argument(*(dynamic_cast<std::invalid_argument*>(e))); } else if (dynamic_cast<std::length_error*>(e)) { return new std::length_error(*(dynamic_cast<std::length_error*>(e))); } else if (dynamic_cast<std::out_of_range*>(e)) { return new std::out_of_range(*(dynamic_cast<std::out_of_range*>(e))); } else if (dynamic_cast<std::overflow_error*>(e)) { return new std::overflow_error(*(dynamic_cast<std::overflow_error*>(e))); } else if (dynamic_cast<std::range_error*>(e)) { return new std::range_error(*(dynamic_cast<std::range_error*>(e))); } else if (dynamic_cast<std::underflow_error*>(e)) { return new std::underflow_error(*(dynamic_cast<std::underflow_error*>(e))); } else if (dynamic_cast<std::runtime_error*>(e)) { return new std::runtime_error(*(dynamic_cast<std::runtime_error*>(e))); } else if (dynamic_cast<std::exception*>(e)) { return new std::exception(*(dynamic_cast<std::exception*>(e))); } } I have coded by taking order reference of below pic. please help me to get classes names in boost:exception which are not in std::exception . if they are in boost::exception only then how to catch that and send to stackToHeapObj and what order i need to follow to add those if checks. try { boost::rethrow_exception(exptr) } here in catch block , we don't know which exception type we have in exptr(ie. std:: or boost:;) then How to catch them. if i use std::exception in catch block then if exptr throws boost::exception type then ... and viceversa..? Please help me to clarify above queries [image: image.png]

3 6

Opinions on merging Assert, StaticAssert, ThrowException into Core
by Nikita Kniazev 17 Oct '21

17 Oct '21

Recently Core grew with additional dependencies on StaticAssert (in 1.76) and ThrowException (in the next release), previously it was only depending on Assert and Config. That made a lot of libraries checkout the same four repositories, three of them containing only a few headers. Merging into a single dependency will affect mostly positive about 100 libraries and negative 1: StlInterfaces (depends on Assert, and will on Core). Please leave a comment at https://github.com/boostorg/core/issues/97 if you think it is a good idea, or have concerns against doing that.

7 14

No more cycles going forward
by Glen Fernandes 16 Oct '21

16 Oct '21

Boost 1.77.0 released with no dependency cycles between libraries. This wasn't easy to achieve and we want to preserve it, going forward. We should not regress and allow libraries to introduce dependency cycles in any future Boost release. i.e. Doing so should be considered a release blocker. Currently, such a regression exists (introduced last month in Context): Asio -> Coroutine -> Context -> Asio It should be fixed before we lock the branches for the 1.78 release, or we should not take this change in the release. Glen

3 3

[Q] Help needed with boost::log, filters and a custom sink backend
by Volker 15 Oct '21

15 Oct '21

Dear Boost experts! I'm new to this list, so please have mercy if I'm not yet familiar with your best practices. Recently, I have been pulling my hair out while trying to use boost::log for a severity-logger-type functionality where the sink backend is not compatible with std::ostream. Best bet was to implement a custom sink backend that does the job in its consume() member. However, I can't get the attribute value for the severity level extracted to an int. For sure, there's something totally obvious I'm missing... Here's the source code (slightly abbreviated): #include <string> #include <boost/log/core.hpp> #include <boost/log/expressions.hpp> #include <boost/log/sinks/basic_sink_backend.hpp> #include <boost/log/sinks/sync_frontend.hpp> #include <boost/log/sources/logger.hpp> #include <boost/log/sources/severity_logger.hpp> #include <boost/log/trivial.hpp> #include <boost/smart_ptr/make_shared_object.hpp> #include <boost/smart_ptr/shared_ptr.hpp> namespace logging = boost::log; namespace sinks = boost::log::sinks; void SomeLogChannel(int severity, const std::string& message) {} class SinkBackend : public sinks::basic_sink_backend<sinks::synchronized_feeding> { public: explicit SinkBackend() {} void consume(logging::record_view const& rec) { std::string message = *rec[boost::log::expressions::smessage]; int severity = 0; if (rec.attribute_values().count("Severity")) { // severity = rec.attribute_values()["Severity"].extract<int>(); // cannot convert from 'boost::log::v2s_mt_nt6::value_ref<T,TagT>' to 'int' with T=int, TagT=void } SomeLogChannel(severity, message); } }; void init_logging() { typedef sinks::synchronous_sink<SinkBackend> sink_t; boost::shared_ptr<logging::core> core = logging::core::get(); boost::shared_ptr<SinkBackend> backend(new SinkBackend()); boost::shared_ptr<sink_t> sink(new sink_t(backend)); core->add_sink(sink); core->set_filter(logging::trivial::severity >= logging::trivial::error); } int main(int, char* []) { init_logging(); boost::log::sources::severity_logger< logging::trivial::severity_level > lg; BOOST_LOG_SEV(lg, logging::trivial::trace) << "Trace message"; BOOST_LOG_SEV(lg, logging::trivial::error) << "Error message"; return 0; } If this is a clumsy approach and there's a more elegant solution to feed log messages into SomeLogChannel() (in reality, it's a bit more complex because it involves a class, a couple interfaces, etc.), don't hesitate to comment as well. I'm still trying to wrap my mind around the topic. Thanks a bunch in advance and greets, Volker -- @: boost(a)bartheld.net

1 0

regarding spurious wakeup in boost 1.76
by Daggumati, Rajesh 13 Oct '21

13 Oct '21

HI Team, I have been facing an issue regarding conditionvariable.timed_wait() This function is returning false everywhere in my code(windows platform). It not waiting for notify signal. conditionvariable.timed_wait(lock1,boost::posix_time::milliseconds(100)) I have found same issue information in google. [Thread] thousands of spurious wakeups from timed_wait() per second (narkive.com)<https://boost-users.boost.narkive.com/xu7advkY/thread-thousands-of-spurious…> did this issue get fixed in boost 1.76.0? Please help me how to fix this issue. Regards, Rajesh D Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.

1 2

Evolving Boost.ContainerHash
by Peter Dimov 13 Oct '21

13 Oct '21

I've been thinking of updating and evolving Boost.ContainerHash, so I e-mailed Daniel James to see what his thoughts on that are. He says he's not going to come back to it, since he's moved on from C++. (Why would anyone do so is beyond me. :-)) More specifically, what I'm envisaging is updating boost::hash to take a seed: template<class T> struct hash { hash(); // as before explicit hash( size_t seed ); size_t operator()(T const& v) { return detail::hash_combine(seed, hash_value(v)); } }; The public hash_combine then becomes: template<class T> void hash_combine( size_t& seed, T const& v ) { return hash<T>(seed)(v); } This allows passing seeded hashes to unordered containers, without any changes to the latter: std::unordered_map<std::string, int, boost::hash<std::string>> map( 0, boost::hash<std::string>( 0x12345678 ) ); Seeding user-exposed hash tables is a good security practice which prevents (or makes less likely) some DoS attacks. The combiner function, detail::hash_combine, will also need to be updated to something that is state of the art for 2021, rather than for 2004. (ContainerHash is already using a more modern implementation of hash_combine, but not in all cases.) The implementation can be cleaned up by removing the C++98 era workarounds for compilers not supporting partial specialization, function template ordering, or argument-dependent lookup. The documentation is also due to a refresh, as the mentions of TR1 are no longer relevant. I also think that Boost.ContainerHash should just be renamed to Boost.Hash as that's what it is - it defines boost::hash. So, I am thinking of taking over ContainerHash and doing all that, if there are no objections.

2 3

[CMake] Can/should we specify optional dependencies
by John Maddock 11 Oct '21

11 Oct '21

I have a regex bug report relating to linking to ICU when using CMake: https://github.com/boostorg/regex/issues/143 Is there a correct way to specify in the CMake file that if you use header X, then you should also link to library Y, but otherwise not? Thanks, John. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

5 9

Boost::posixtime issue
by mahesh pramod 07 Oct '21

07 Oct '21

Hi , I am getting false always for this timed_wait function . does posix_time supports in windows as its not looking for notify signal. scoped_lock_t lock(m_mutex); EXPECT_TRUE(m_condition_variable.timed_wait(lock, boost::posix_time::milliseconds(500))) << "Should get signalled (true) not time out";

1 0

boost::posix_time issue
by mahesh pramod 06 Oct '21

06 Oct '21

Hi , I am getting false always for this timed_wait function . does posix_time supports in windows as its not looking for notify signal. scoped_lock_t lock(m_mutex); EXPECT_TRUE(m_condition_variable.timed_wait(lock, boost::posix_time::milliseconds(500))) << "Should get signalled (true) not time out";

1 0

MSYS2 - MinGW64 - Windows 10 Pro - GCC 10.2.0 - undefined references
by Jens Kallup 05 Oct '21

05 Oct '21

Hello Community, I running Windows 10 Pro. MSYS2 - MinGW64-bit with gcc/g++ 10.2.0. I have download the 1_77 Version of Boost, compile it with b2 in the msys2 shell terminal. I could not replace cxx11 to cxx17. All options to build.bat, and b2.exe/sh to switch to cxx17 have not be worked. I downwrite the simple "Boost.program_options" example. I could compile it without any errors or warnings. But I ran into trouble at link stage. I have tried libs for x32/64, single/multi thread, debug/release, static/dynamic. All ends up with the same error of undefined reference explained below. Here comes the known source code to the problem: ---%<--- # include <boost/program_options.hpp> # include "common.h" namespace po = boost::program_options; int main(int argc, char *argv[]) { try { po::options_description desc("Allowed Options"); desc.add_options() ("help", "shows the help page") ("compression", po::value<int>(), "set compression level") ; po::variables_map vm; po::store(po::parse_command_line(argc, argv, desc), vm); po::notify(vm); if (vm.count("help")) { std::cout << desc << std::endl; return SUCCESS; } if (vm.count("compression")) { std::cout << "Compression level was set to " << vm["compression"].as<int>() << "." << std::endl; } else { std::cout << "Compression level was not set." << std::endl; } } catch(...) { std::cerr << "caugth a error.\n"; return FAILURE; } return SUCCESS; } --->%--- Here is a list of the files that are generated during the build time: devlab1@rk1700 MINGW64 /e/Projekte/news $ dir ../boost_1_77_0/stage/lib/ cmake libboost_atomic-mgw10-mt-d-x32-1_77.a libboost_atomic-mgw10-mt-d-x64-1_77.a libboost_atomic-mgw10-mt-s-x64-1_77.a libboost_atomic-mgw10-mt-x32-1_77.a libboost_atomic-mgw10-mt-x64-1_77.a libboost_chrono-mgw10-mt-d-x32-1_77.a libboost_chrono-mgw10-mt-d-x64-1_77.a libboost_chrono-mgw10-mt-s-x64-1_77.a libboost_chrono-mgw10-mt-x32-1_77.a libboost_chrono-mgw10-mt-x64-1_77.a libboost_container-mgw10-mt-d-x32-1_77.a libboost_container-mgw10-mt-d-x64-1_77.a libboost_container-mgw10-mt-s-x64-1_77.a libboost_container-mgw10-mt-x32-1_77.a libboost_container-mgw10-mt-x64-1_77.a libboost_context-mgw10-mt-d-x32-1_77.a libboost_context-mgw10-mt-d-x64-1_77.a libboost_context-mgw10-mt-s-x64-1_77.a libboost_context-mgw10-mt-x32-1_77.a libboost_context-mgw10-mt-x64-1_77.a libboost_contract-mgw10-mt-d-x32-1_77.a libboost_contract-mgw10-mt-d-x64-1_77.a libboost_contract-mgw10-mt-s-x64-1_77.a libboost_contract-mgw10-mt-x32-1_77.a libboost_contract-mgw10-mt-x64-1_77.a libboost_coroutine-mgw10-mt-d-x32-1_77.a libboost_coroutine-mgw10-mt-d-x64-1_77.a libboost_coroutine-mgw10-mt-s-x64-1_77.a libboost_coroutine-mgw10-mt-x32-1_77.a libboost_coroutine-mgw10-mt-x64-1_77.a libboost_date_time-mgw10-mt-d-x32-1_77.a libboost_date_time-mgw10-mt-d-x64-1_77.a libboost_date_time-mgw10-mt-s-x64-1_77.a libboost_date_time-mgw10-mt-x32-1_77.a libboost_date_time-mgw10-mt-x64-1_77.a libboost_exception-mgw10-mt-d-x32-1_77.a libboost_exception-mgw10-mt-d-x64-1_77.a libboost_exception-mgw10-mt-s-x64-1_77.a libboost_exception-mgw10-mt-x32-1_77.a libboost_exception-mgw10-mt-x64-1_77.a libboost_fiber-mgw10-mt-d-x64-1_77.a libboost_fiber-mgw10-mt-s-x64-1_77.a libboost_fiber-mgw10-mt-x64-1_77.a libboost_filesystem-mgw10-mt-d-x32-1_77.a libboost_filesystem-mgw10-mt-d-x64-1_77.a libboost_filesystem-mgw10-mt-s-x64-1_77.a libboost_filesystem-mgw10-mt-x32-1_77.a libboost_filesystem-mgw10-mt-x64-1_77.a libboost_graph-mgw10-mt-d-x32-1_77.a libboost_graph-mgw10-mt-d-x64-1_77.a libboost_graph-mgw10-mt-s-x64-1_77.a libboost_graph-mgw10-mt-x32-1_77.a libboost_graph-mgw10-mt-x64-1_77.a libboost_iostreams-mgw10-mt-d-x32-1_77.a libboost_iostreams-mgw10-mt-d-x64-1_77.a libboost_iostreams-mgw10-mt-s-x64-1_77.a libboost_iostreams-mgw10-mt-x32-1_77.a libboost_iostreams-mgw10-mt-x64-1_77.a libboost_json-mgw10-mt-d-x32-1_77.a libboost_json-mgw10-mt-d-x64-1_77.a libboost_json-mgw10-mt-s-x64-1_77.a libboost_json-mgw10-mt-x32-1_77.a libboost_json-mgw10-mt-x64-1_77.a libboost_locale-mgw10-mt-d-x32-1_77.a libboost_locale-mgw10-mt-d-x64-1_77.a libboost_locale-mgw10-mt-s-x64-1_77.a libboost_locale-mgw10-mt-x32-1_77.a libboost_locale-mgw10-mt-x64-1_77.a libboost_log-mgw10-mt-d-x32-1_77.a libboost_log-mgw10-mt-d-x64-1_77.a libboost_log-mgw10-mt-s-x64-1_77.a libboost_log-mgw10-mt-x32-1_77.a libboost_log-mgw10-mt-x64-1_77.a libboost_log_setup-mgw10-mt-d-x32-1_77.a libboost_log_setup-mgw10-mt-d-x64-1_77.a libboost_log_setup-mgw10-mt-s-x64-1_77.a libboost_log_setup-mgw10-mt-x32-1_77.a libboost_log_setup-mgw10-mt-x64-1_77.a libboost_math_c99-mgw10-mt-d-x64-1_77.a libboost_math_c99-mgw10-mt-s-x64-1_77.a libboost_math_c99-mgw10-mt-x64-1_77.a libboost_math_c99f-mgw10-mt-d-x64-1_77.a libboost_math_c99f-mgw10-mt-s-x64-1_77.a libboost_math_c99f-mgw10-mt-x64-1_77.a libboost_math_c99l-mgw10-mt-d-x64-1_77.a libboost_math_c99l-mgw10-mt-s-x64-1_77.a libboost_math_c99l-mgw10-mt-x64-1_77.a libboost_math_tr1-mgw10-mt-d-x64-1_77.a libboost_math_tr1-mgw10-mt-s-x64-1_77.a libboost_math_tr1-mgw10-mt-x64-1_77.a libboost_math_tr1f-mgw10-mt-d-x64-1_77.a libboost_math_tr1f-mgw10-mt-s-x64-1_77.a libboost_math_tr1f-mgw10-mt-x64-1_77.a libboost_math_tr1l-mgw10-mt-d-x64-1_77.a libboost_math_tr1l-mgw10-mt-s-x64-1_77.a libboost_math_tr1l-mgw10-mt-x64-1_77.a libboost_nowide-mgw10-mt-d-x32-1_77.a libboost_nowide-mgw10-mt-d-x64-1_77.a libboost_nowide-mgw10-mt-s-x64-1_77.a libboost_nowide-mgw10-mt-x32-1_77.a libboost_nowide-mgw10-mt-x64-1_77.a libboost_prg_exec_monitor-mgw10-mt-d-x32-1_77.a libboost_prg_exec_monitor-mgw10-mt-d-x64-1_77.a libboost_prg_exec_monitor-mgw10-mt-s-x64-1_77.a libboost_prg_exec_monitor-mgw10-mt-x32-1_77.a libboost_prg_exec_monitor-mgw10-mt-x64-1_77.a libboost_program_options-mgw10-mt-d-x32-1_77.a libboost_program_options-mgw10-mt-d-x64-1_77.a libboost_program_options-mgw10-mt-s-x64-1_77.a libboost_program_options-mgw10-mt-x32-1_77.a libboost_program_options-mgw10-mt-x64-1_77.a libboost_python39-mgw10-mt-d-x32-1_77.a libboost_python39-mgw10-mt-d-x64-1_77.a libboost_python39-mgw10-mt-x32-1_77.a libboost_python39-mgw10-mt-x64-1_77.a libboost_random-mgw10-mt-d-x32-1_77.a libboost_random-mgw10-mt-d-x64-1_77.a libboost_random-mgw10-mt-s-x64-1_77.a libboost_random-mgw10-mt-x32-1_77.a libboost_random-mgw10-mt-x64-1_77.a libboost_regex-mgw10-mt-d-x32-1_77.a libboost_regex-mgw10-mt-d-x64-1_77.a libboost_regex-mgw10-mt-s-x64-1_77.a libboost_regex-mgw10-mt-x32-1_77.a libboost_regex-mgw10-mt-x64-1_77.a libboost_serialization-mgw10-mt-d-x32-1_77.a libboost_serialization-mgw10-mt-d-x64-1_77.a libboost_serialization-mgw10-mt-s-x64-1_77.a libboost_serialization-mgw10-mt-x32-1_77.a libboost_serialization-mgw10-mt-x64-1_77.a libboost_stacktrace_basic-mgw10-mt-d-x32-1_77.a libboost_stacktrace_basic-mgw10-mt-x32-1_77.a libboost_stacktrace_noop-mgw10-mt-d-x32-1_77.a libboost_stacktrace_noop-mgw10-mt-d-x64-1_77.a libboost_stacktrace_noop-mgw10-mt-s-x64-1_77.a libboost_stacktrace_noop-mgw10-mt-x32-1_77.a libboost_stacktrace_noop-mgw10-mt-x64-1_77.a libboost_stacktrace_windbg-mgw10-mt-d-x64-1_77.a libboost_stacktrace_windbg-mgw10-mt-s-x64-1_77.a libboost_stacktrace_windbg-mgw10-mt-x64-1_77.a libboost_stacktrace_windbg_cached-mgw10-mt-d-x64-1_77.a libboost_stacktrace_windbg_cached-mgw10-mt-s-x64-1_77.a libboost_stacktrace_windbg_cached-mgw10-mt-x64-1_77.a libboost_system-mgw10-mt-d-x32-1_77.a libboost_system-mgw10-mt-d-x64-1_77.a libboost_system-mgw10-mt-s-x64-1_77.a libboost_system-mgw10-mt-x32-1_77.a libboost_system-mgw10-mt-x64-1_77.a libboost_test_exec_monitor-mgw10-mt-d-x32-1_77.a libboost_test_exec_monitor-mgw10-mt-d-x64-1_77.a libboost_test_exec_monitor-mgw10-mt-s-x64-1_77.a libboost_test_exec_monitor-mgw10-mt-x32-1_77.a libboost_test_exec_monitor-mgw10-mt-x64-1_77.a libboost_thread-mgw10-mt-d-x32-1_77.a libboost_thread-mgw10-mt-d-x64-1_77.a libboost_thread-mgw10-mt-s-x64-1_77.a libboost_thread-mgw10-mt-x32-1_77.a libboost_thread-mgw10-mt-x64-1_77.a libboost_timer-mgw10-mt-d-x32-1_77.a libboost_timer-mgw10-mt-d-x64-1_77.a libboost_timer-mgw10-mt-s-x64-1_77.a libboost_timer-mgw10-mt-x32-1_77.a libboost_timer-mgw10-mt-x64-1_77.a libboost_type_erasure-mgw10-mt-d-x32-1_77.a libboost_type_erasure-mgw10-mt-d-x64-1_77.a libboost_type_erasure-mgw10-mt-s-x64-1_77.a libboost_type_erasure-mgw10-mt-x32-1_77.a libboost_type_erasure-mgw10-mt-x64-1_77.a libboost_unit_test_framework-mgw10-mt-d-x32-1_77.a libboost_unit_test_framework-mgw10-mt-d-x64-1_77.a libboost_unit_test_framework-mgw10-mt-s-x64-1_77.a libboost_unit_test_framework-mgw10-mt-x32-1_77.a libboost_unit_test_framework-mgw10-mt-x64-1_77.a libboost_wave-mgw10-mt-d-x32-1_77.a libboost_wave-mgw10-mt-d-x64-1_77.a libboost_wave-mgw10-mt-s-x64-1_77.a libboost_wave-mgw10-mt-x32-1_77.a libboost_wave-mgw10-mt-x64-1_77.a libboost_wserialization-mgw10-mt-d-x32-1_77.a libboost_wserialization-mgw10-mt-d-x64-1_77.a libboost_wserialization-mgw10-mt-s-x64-1_77.a libboost_wserialization-mgw10-mt-x32-1_77.a libboost_wserialization-mgw10-mt-x64-1_77.a Here comes the command line for compile/link the application $ /mingw64/bin/x86_64-w64-mingw32-g++ -o winperm.exe ./tmp/main.o ./tmp/network.o ./tmp/threading.o ./tmp/translator.o ./tmp/tv_tui.o ./tmp/permutation.o -fopenmp -MD -I/E/Projekte/boost_1_77_0/stage/lib -L../boost_1_77_0/stage/lib -L../tvision/build -L/mingw64/lib -L/mingw64/x86_64-w64-mingw32/lib -ltvision -lkernel32 -luser32 -lwinmm -lws2_32 -lintl -lpthread -lboost_iostreams-mgw10-mt-x64-1_77 -lboost_program_options-mgw10-mt-x64-1_77 And here comes the error output from the linker LD: E:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32 /bin/ld.exe: ./tmp/main.o:main.cc: (.text$_ZN5boost15program_options25basic_command_line_parserIcE12extra_parserENS_9 function1ISt4pairISsSsERKSsEE[_ZN5boost15program_options25basic_command_line_parserIcE12 extra_parserENS_9function1ISt4pairISsSsERKSsEE]+0x41): undefined reference to `boost::program_options::detail::cmdline::set_additional_parser(boost::function1 <std::pair<std::string, std::string>, std::string const&>)' E:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32 /bin/ld.exe: ./tmp/main.o:main.cc: (.text$_ZN5boost15program_options11to_internalISsEESt6vectorISsSaISsEERKS2_IT_Sa IS5_EE[_ZN5boost15program_options11to_internalISsEESt6vectorISsSaISsEERKS2_IT_Sa IS5_EE]+0x48): undefined reference to `boost::program_options::to_internal (std::string const&)' E:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64- mingw32/bin/ld.exe: ./tmp/main.o:main.cc: (.text$_ZN5boost15program_options25basic_command_line_parserIcEC1EiPKPKc [_ZN5boost15program_options25basic_command_line_parserIcEC1EiPKPKc]+0xaf): undefined reference to `boost::program_options::detail::cmdline::cmdline(std::vector<std::string, std::allocator<std::string> > const&)' E:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32 /bin/ld.exe: ./tmp/main.o:main.cc:(.text.startup.main+0xb8): undefined reference to `boost::program_options::options_description::options_description(std::string const&, unsigned int, unsigned int)' E:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32 /bin/ld.exe: ./tmp/main.o:main.cc:(.text.startup.main+0x281): undefined reference to `boost::program_options::abstract_variables_map::operator[](std::string const&) const' E:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32 /bin/ld.exe: ./tmp/main.o:main.cc: (.text$_ZN5boost15program_options10validators17get_single_stringIcEERKSbIT_St11 char_traitsIS3_ESaIS3_EERKSt6vectorIS7_SaIS7_EEb[_ZN5boost15program_options10validators17 get_single_stringIcEERKSbIT_St11char_traitsIS3_ESaIS3_EERKSt6vectorIS7_SaIS7_EEb]+0xa1): undefined reference to `boost::program_options::validation_error::get_template(boost::program_options:: validation_error::kind_t)' E:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32 /bin/ld.exe: ./tmp/main.o:main.cc: (.text$_ZN5boost15program_options10validators17get_single_stringIcEERKSbIT_St11 char_traitsIS3_ESaIS3_EERKSt6vectorIS7_SaIS7_EEb[_ZN5boost15program_options10validators17 get_single_stringIcEERKSbIT_St11char_traitsIS3_ESaIS3_EERKSt6vectorIS7_SaIS7_EEb]+0xba): undefined reference to `boost::program_options::error_with_option_name::error_with_option_name(std::string const&, std::string const&, std::string const&, int)' E:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32 /bin/ld.exe: ./tmp/main.o:main.cc: (.text$_ZN5boost15program_options10validators17get_single_stringIcEERKSbIT_St11 char_traitsIS3_ESaIS3_EERKSt6vectorIS7_SaIS7_EEb[_ZN5boost15program_options10 validators17get_single_stringIcEERKSbIT_St11char_traitsIS3_ESaIS3_EERKSt6vectorIS7_SaIS 7_EEb]+0x199): undefined reference to `boost::program_options::validation_error::get_template(boost::program_options:: validation_error::kind_t)' E:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32 /bin/ld.exe: ./tmp/main.o:main.cc: (.text$_ZN5boost15program_options10validators17get_single_stringIcEERKSbIT_St11 char_traitsIS3_ESaIS3_EERKSt6vectorIS7_SaIS7_EEb[_ZN5boost15program_options10validators17 get_single_stringIcEERKSbIT_St11char_traitsIS3_ESaIS3_EERKSt6vectorIS7_SaIS7_EEb]+0x1b2): undefined reference to `boost::program_options::error_with_option_name::error_with_option_name(std::string const&, std::string const&, std::string const&, int)' E:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32 /bin/ld.exe: ./tmp/main.o:main.cc: (.text$_ZN5boost15program_options8validateIicEEvRNS_3anyERKSt6vectorISbIT0_St11 char_traitsIS5_ESaIS5_EESaIS9_EEPT_l[_ZN5boost15program_options8validateIicEEvRNS_3any ERKSt6vectorISbIT0_St11char_traitsIS5_ESaIS5_EESaIS9_EEPT_l]+0x5db): undefined reference to `boost::program_options::invalid_option_value::invalid_option_value(std::string const&)' E:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32 /bin/ld.exe: ./tmp/main.o:main.cc: (.rdata$_ZTVN5boost10wrapexceptINS_15program_options20invalid_option_valueEEE[_ZTVN5 boost10wrapexceptINS_15program_options20invalid_option_valueEEE]+0x60): undefined reference to `boost::program_options::error_with_option_name::substitute_placeholders(std::string const&) const' E:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32 /bin/ld.exe: ./tmp/main.o:main.cc: (.rdata$_ZTVN5boost10wrapexceptINS_15program_options16validation_errorEEE[_ZTVN5boost10 wrapexceptINS_15program_options16validation_errorEEE]+0x60): undefined reference to `boost::program_options::error_with_option_name::substitute_placeholders(std::string const&) const' E:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32 /bin/ld.exe: ./tmp/main.o:main.cc: (.rdata$_ZTVN5boost15program_options16validation_errorE[_ZTVN5boost15program_options16 validation_errorE]+0x30): undefined reference to `boost::program_options::error_with_option_name::substitute_placeholders(std::string const&) const' E:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32 /bin/ld.exe: ./tmp/main.o:main.cc: (.rdata$_ZTVN5boost15program_options20invalid_option_valueE[_ZTVN5boost15 program_options20invalid_option_valueE]+0x30): undefined reference to `boost::program_options::error_with_option_name::substitute_placeholders(std::string const&) const' E:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32 /bin/ld.exe: ./tmp/main.o:main.cc: (.rdata$_ZTVN5boost15program_options11typed_valueIicEE[_ZTVN5boost15 program_options11typed_valueIicEE]+0x38): undefined reference to `boost::program_options::value_semantic_codecvt_helper<char>::parse(boost::any&, std::vector<std::string, std::allocator<std::string> > const&, bool) const' E:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32 /bin/ld.exe: ./tmp/main.o:main.cc: (.rdata$.refptr._ZN5boost15program_options3argE[.refptr._ZN5boost15program_options3 argE]+0x0): undefined reference to `boost::program_options::arg' collect2.exe: error: ld returned 1 exit status Did I miss something ? The question is now, how can I use boost under msys2 with mingw64 ? Thanks for helping hands, paule32

1 0

cybersecuriy for boost
by rajesh daggumati 04 Oct '21

04 Oct '21

HI, Is there any group who supports on cyber security while we are using boost 1.76.0

4 3

queries regarding usage of boost 1.76.0 .
by mahesh pramod 04 Oct '21

04 Oct '21

Hi, I have below queries regarding boost 1.76.0. I have been faced these below queries. 1.how to check boost is statically binded or dynamically binded with my code? is this binding related to virtual concept? 2.how boost interacts with any software? 3. does boost takes our data for any use? ex: when we use sql servers they take our data for testing purpose. Like that does boost take?

2 1

Re: [boost] Simple boost fix for sparc64
by John Klos 30 Sep '21

30 Sep '21

>> Here's a failure example: >> https://ftp.ziaspace.com/pub/pkgsrc/reports/9.0_2021Q2/sparc64/boost-libs-1… > > Seems like it's already fixed: > https://github.com/boostorg/predef/commit/1be0e4a2d8db15a405f64a6f65507b87c… Excellent. I'll look for that in 1.78.0. Thanks, John Klos

1 0

regarding exception_ptr
by rajesh daggumati 30 Sep '21

30 Sep '21

Hi Team, PFB code snippet: try { BOOST_THROW_EXCEPTION(std::invalid_argument("Blah")); } catch(...) { boost::exception_ptr exception = boost::current_exception(); const std::invalid_arguement* p; try{ boost :: rethrow_exception(exceptionptr) } catch(std::invalid_argument &e) { p = dynamic_cast<const std::invalid_argument*>(&e) } const std::invalid_argument* actualStdPtr = ExceptionHelper::ExtractConstPtr<std::invalid_argument>(exceptionptr); EXPECT_TRUE(((void*)p) == ((void*)actualStdPtr)) << "Same Object"; //this condition is getting failed. }} static const t* ExtractConstPtr(boost::exception_ptr ep) { try { boost::rethrow_excepton(ep); } catch(T &e){ const T* exceptType = dynamic_cast<const T*>(&e); return exceptType; } catch (std::exception & e){ const T* exceptType = dynamic_cast<const T*>(&e); return exceptType; } } //EXPECT_TRUE(((void*)p) == ((void*)actualStdPtr)) -->what will be the reason to get failed as I do same thing in both cases. Regards, Rajesh D

2 2

conversion issues from boost::exception_ptr to exception class shared_ptr
by rajesh daggumati 29 Sep '21

29 Sep '21

HI Team, // i have caught exception in exception_ptr and I and trying to convert to ExceptionPtr_t but I am facing issue at below derived->severity(). * unknown file: error: SEH exception with code 0xc0000005 thrown in the test body.* *code snippet is :* *E*xceptionPtr_t ExceptionHelper::TryGetExceptionPtr(boost::exception_ptr exception) { ExceptionPtr_t result ; std::string res; if(!exception) return result; try { boost::rethrow_exception(exception) *}catch(boost::exception &e)* *{boost::throw_file::value_type const* throw_file_data = boost::get_error_info<boost::throw_file>(e);* *if(* *throw_file_data)* *{* * result = exceptionPtr_t(new ExceptionWrapper(exception,*throw_filed_data,true))* *}* *return result;* *}* class Exception : public virtual std::exception, public virtual boost::exception { protected: string what; serviorytype m_severity; public: explicit Exception(const std::string& what); virtual ~Exception() throw() {} // we have some member functions like severity(),setseverity(value)... } class ExceptionWrapper : public Exception { private: string m_what_inner; boost::exception_ptr m_inner; public: explict ExceptionWrapper(boost::exception_ptr inner,string &what() = std::string,bool copythrow = true); explict ExceptionWrapper(boost::exceptionPtr_t inner,string &what() = std::string,bool copythrow = true); virtual ~ExceptionWrapper() throw(){} // some methods like severity(),setSeverity(value),.....) } I was doing like: const Exception* derived = reinterPret_cast<const Exception*> (&exception)// here exception is type of exception_ptr if(derived) { derived->severity(); // here exception is coming... if i put this line in try block then its going for catch block and new exception is being rasied. if i dont put try block then *unknown file: error: SEH exception with code 0xc0000005 thrown in the test body.* } Please help me to resolve this issue

2 1

Simple boost fix for sparc64
by John Klos 27 Sep '21

27 Sep '21

Hello, boost people, This is a small, simple patch to make boost compile properly on NetBSD/sparc64, at very least, and on SPARC and UltraSPARC in general. Here's a failure example: https://ftp.ziaspace.com/pub/pkgsrc/reports/9.0_2021Q2/sparc64/boost-libs-1… Thanks very much, John Klos --- libs/predef/include/boost/predef/architecture/sparc.h.orig 2021-09-27 16:03:19.965761565 +0000 +++ libs/predef/include/boost/predef/architecture/sparc.h 2021-09-27 16:11:18.084758689 +0000 @@ -34,10 +34,10 @@ #if defined(__sparc__) || defined(__sparc) # undef BOOST_ARCH_SPARC -# if !defined(BOOST_ARCH_SPARC) && (defined(__sparcv9) || defined(__sparc_v9__) +# if !defined(BOOST_ARCH_SPARC) && (defined(__sparcv9) || defined(__sparc_v9__)) # define BOOST_ARCH_SPARC BOOST_VERSION_NUMBER(9,0,0) # endif -# if !defined(BOOST_ARCH_SPARC) && (defined(__sparcv8) || defined(__sparc_v8__) +# if !defined(BOOST_ARCH_SPARC) && (defined(__sparcv8) || defined(__sparc_v8__)) # define BOOST_ARCH_SPARC BOOST_VERSION_NUMBER(8,0,0) # endif # if !defined(BOOST_ARCH_SPARC)

2 1

access violation and data stealing
by rajesh daggumati 27 Sep '21

27 Sep '21

Hi Team, I am preparing a document for boost library(1.76.0) to be used in our organisation. as part of documnet, I need some information. 1.Regarding data integrity and security of gtest and how it interacts with any software. 2.if we use boost, we see any access violation or data stealing? 3.is there any group who supports on cyber security while we are using boost 1.76.0 Please kindly answer above 3 queries. Regards, Raesh D

2 1

please guide me to open source world
by Saurabh Tiwari 23 Sep '21

23 Sep '21

Hai SIR/MAAM this side SAURABH TIWARI currently I am in my 3rd year of Btech I don’t know much about the open source can you please help how to get started for the same I know C++, C, basic data structures and algorithms I would be very thankful if you please help me sir so that I can contribute to this open-source world.

4 5

New to boost
by rajesh daggumati 22 Sep '21

22 Sep '21

Hi Team, in my code,I had to write like below: const int* p = boost::get_error_info<boost::throw_line>(exception); But while building the code,I am facing issue like below: error C2683: 'dynamic_cast':'boost::exception_ptr' is not a polymorphic type.. Then I have added one dummy virtual function in exception_ptr class then this issue got resolved but I am getting some test cases failed at this line: Const int* p = boost::get_error_info<boost::throw_line>(exception); Please help me where will be the issue is.what will be the solution.

4 3

Published various template libraries...
by David Bien 22 Sep '21

22 Sep '21

That I have been working on over the past 23 years (when not working for actual money). Directed Graph Template Library: https://github.com/davidbien/dgraph Original email to boost mailing list from year 2000: https://lists.boost.org/Archives/boost/2000/04/2834.php Lexical Analyzer Generator Template Library: https://github.com/davidbien/lexang Original email to boost mailing list from year 2000: https://lists.boost.org/Archives/boost/2000/04/2837.php This depends on the dgraph git submodule above. The above are written in "old" C++ - but updated to compiler in the latest compilers (MSVC, clang11). Built on the above: XML Parser/Writer/DOM Template Library: https://github.com/davidbien/xmlpinc This I developed over the last winter. It is written in C++20 and requires msvc19 or clang11. I heavily use C++20 concepts. There is a lack of documentation. As well: XML Parser/Writer/DOM Development Environment: https://github.com/davidbien/xmlp This contains the LEX specifications (which are written using overridden C++ operators in a namespace) that produce the state machines for UTF8, UTF16 and UTF32 versions of the XML parser - which are then, upon modification, checked into: https://github.com/davidbien/xmlpinc This as well requires the nearly latest versions of MSVC or clang. Once again: There is a lack of documentation. I don't use boost in these libraries - preferring not to have a dependency on it. I also published: https://github.com/davidbien/bienutil Which contains a lot of stuff from year 2000, but also contains some new stuff which is pretty cool: 1. An actually performant and memory-conservative implementation of a Van Emde Boas Tree: https://github.com/davidbien/bienutil/blob/master/_vebtree.h 2. An "exponential chunked array" (misnamed as "logarray.h") that uses a single piece of memory initially: https://github.com/davidbien/bienutil/blob/master/_logarray.h 3. A bunch of other stuff that I wrote back in 2000 since there wasn't much available back then in terms of C++ utility templates. There is a testbed for the dgraph impl but I haven't yet converted them to CMAKE/googletest. There is also a testbed for the vebtree impl but once again not converted to CMAKE/googletest. (I only have so many fingers). Anyway, I'd like to know what people think. The XML parser is meant to be fully compliant with XML Version 1.0 and meant to be a development environment that can be used to extend to full compatibility. I am currently working on a Parser Generator Template Library (think replacement for yacc or bison) that will work with my LEX replacement and allow use of the LEX terminals in the EBNF for the parser specification (which will again be encoding using C++ overridden operators in a namespace). Sincerely, David Bien

2 2

Please guide me for open source
by Saurabh Tiwari 21 Sep '21

21 Sep '21

Hai SIR/MAAM this side SAURABH TIWARI currently I am in my 3rd year of Btech I don’t know much about open source can you please help how to get started for the same I know C++ ,C, basic data structures and algorithms, html , css (basics), and learning web development. I would be very thankful of you please help me sir so that I can contribute to this open source world.

1 0