- Boost - lists.boost.org

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