May 2016 - Boost - lists.preview.boost.org

A GUI Library
by jinhao 09 Nov '17

09 Nov '17

Hi, all I am developing a GUI library, it takes aim at easy-to-use and portable library for modern C++ methods. The project at http://stdex.sourceforge.net A git repository at http://nanapro.codeplex.com A brief at http://nanaproject.wordpress.com/2011/12/16/preliminary-study-of-nana-c-lib… Is there any interest in this library? Regards Jinhao

8 8

Re: [boost] Boost CRC maintainer (Daryle Walker) missing in action?
by Olaf van der Spek 19 Jun '17

19 Jun '17

Hi Daryle, Any luck on your new setup? Gr, Olaf On Mon, Nov 28, 2011 at 1:11 AM, Daryle Walker <darylew(a)gmail.com> wrote: > I can look at it once I've finished my new setup. > > I had to reset my computer after a partial crash years ago. I never > got around to recreating my programming setup. My computer had been > at its maximum Operating System level back then, which is now 3 > versions behind. For the past few months, I've had my sister's old > laptop, with Windows Vista, and am trying to add a programming setup > to it now. > > > On Tue, Nov 22, 2011 at 7:18 AM, Beman Dawes <bdawes(a)acm.org> wrote: >> Hi Daryle, >> >> This guy has volunteered to take over maintenance of Boost CRC. Should >> we take him up on his offer? > >> ---------- Forwarded message ---------- >> From: >> Date: Wed, Nov 2, 2011 at 7:51 AM >> Subject: [boost] Boost CRC maintainer (Daryle Walker) missing in action? >> To: boost(a)lists.boost.org >> >> >> Hi, >> >> It looks like the Boost CRC maintainer (Daryle Walker) is missing in action? >> >> No response to tickets from the past 3 years. What's the procedure in this case? >> >> https://svn.boost.org/trac/boost/ticket/2492 >> https://svn.boost.org/trac/boost/query?component=crc&col=id&col=summary&col… > > -- > Daryle Walker > Mac, Internet, and Video Game Junkie > darylew AT gmail DOT com -- Olaf

2 2

[msm] [statechart] unmerged PRs
by András Kucsma 23 May '17

23 May '17

Hi Everyone, There are a couple of PRs for msm and statechart by me and others, which didn't get any attention for many months now. Can the maintainers please take a look at them? https://github.com/boostorg/msm/pulls https://github.com/boostorg/statechart/pulls Thank you, Andras

2 2

[clang] clang-cl expansion of macros
by Edward Diener 29 Apr '17

29 Apr '17

You can get clang-cl ( clang-win ) to show its VC++ emulated expansion of macros somewhat by passing the c++ option '-fmacro-backtrace-limit=0' to the compiler. It is still blessedly difficult to see the what and the why of clang's error messages when expanding macro using clang-cl, but at least it gives you a better chance of understanding where clang's emulation of VC++ has gone wrong. I have posted bug 27380 to the llvm/clang bug tracker at https://llvm.org/bugs/show_bug.cgi?id=27380 showing the main failure in VC++ emulation which I see when testing Boost PP with clang-cl.

3 8

[container] moving a pre-built vector into a flat_set
by Sam Kellett 12 Mar '17

12 Mar '17

a common problem i encounter is that i have two stage's w/r/t to a large collection of data: building and querying. vector is obviously the king of building. flat_set is the king of querying. so what i often tend to do is build up a very large vector, sort it then create a flat_set using the flat_set(ordered_unique_t) constructor. however this still copies the entire vector into the flat_set, right? what i would like to be able to do is move the vector straight into the flat_set, something like: std::vector<T> data; flat_set data_set1(std::move(data)) // move vector in and sort it // or: std::sort(data.begin(), data.end()); // sort vector flat_set data_set2(ordered_unique_t, std::move(data)) // and move it in is this doable (am i just being blind?) or is there plans/interest for this?

8 19

[nowide] Library Updates
by Artyom Beilis 04 Mar '17

04 Mar '17

Hello, Disclaimer: --------------- I recently discovered that virtually all e-mails sent from Yahoo account to any mailing lists go to user's spam due to recent Yahoo's DMARC policy. So I'm sending some important stuff from GMail account that almost certainly was missed: What is Boost.Nowide: -------------------------------- Boost.Nowide is a library that make cross platform Unicode aware programming easier. The library provides an implementation of standard C and C++ library functions, such that their inputs are UTF-8 aware on Windows without requiring to use Wide API. It was inspiration and inspired by http://utf8everywhere.org/ development ideas and policy. Some updates regarding Boost.Nowide ------------------------------- 1. Library moved to github and its format is converted to modular boost layout: https://github.com/artyom-beilis/nowide 2. Fixed unsupported std::ios::ate flag by boost::nowide::fstream 3. Added some C++11 interfaces to boost::nowide::fstream 4. Added integration functionality with boost::filesystem: https://github.com/artyom-beilis/nowide/blob/master/include/boost/nowide/in… Note: that the links to the source code on review schedule aren't relevant, it should be: - Code: https://github.com/artyom-beilis/nowide - Documentation: http://cppcms.com/files/nowide/html/ Also the library is still looking for review manager. Artyom Beilis P.S.: I'm sorry if you are getting this as "duplicate"

2 1

bad include guards
by Steven Watanabe 26 Jan '17

26 Jan '17

AMDG The following pairs of files have identical include guards ./boost/concept_check/general.hpp ./boost/concept/detail/msvc.hpp ./boost/concept_check/msvc.hpp ./boost/concept/detail/msvc.hpp ./boost/filesystem/cerrno.hpp ./boost/cerrno.hpp ./boost/interprocess/containers/tree.hpp ./boost/interprocess/containers/detail/tree.hpp ./boost/mpl/min_max.hpp ./boost/mpl/max.hpp ./boost/mpl/vector/aux_/front.hpp ./boost/mpl/list/aux_/front.hpp ./boost/multi_index/identity_fwd.hpp ./boost/multi_index/identity.hpp ./boost/python/pointee.hpp ./boost/python/detail/pointee.hpp ./boost/spirit/phoenix/closures.hpp ./boost/lambda/closures.hpp ./boost/xpressive/proto/v1_/proto_typeof.hpp ./boost/xpressive/proto/proto_typeof.hpp ./libs/config/test/boost_no_dep_nested_class.ipp ./libs/config/test/boost_has_vc6_mem_templ.ipp ./libs/config/test/boost_no_mem_templates.ipp ./libs/config/test/boost_has_vc6_mem_templ.ipp ./libs/config/test/boost_no_std_allocator.ipp ./libs/config/test/boost_has_vc6_mem_templ.ipp ./libs/conversion/test.hpp ./libs/any/test.hpp ./libs/interprocess/example/print_container.hpp ./libs/interprocess/example/printcontainer.hpp ./libs/interprocess/test/expand_bwd_test_template.hpp ./libs/interprocess/test/allocation_test_template.hpp ./libs/interprocess/test/printcontainer.hpp ./libs/interprocess/example/printcontainer.hpp ./libs/interprocess/test/print_container.hpp ./libs/interprocess/example/printcontainer.hpp ./libs/iostreams/test/detail/utf8_codecvt_facet.hpp ./boost/detail/utf8_codecvt_facet.hpp ./libs/regex/test/regress/test_regex_search.hpp ./libs/regex/test/regress/test_partial_match.hpp ./libs/serialization/test/C.hpp ./libs/serialization/test/A.hpp ./libs/xpressive/perf/regex_comparison.hpp ./libs/regex/performance/regex_comparison.hpp ./tools/inspect/time_string.hpp ./tools/common/time_string.hpp In Christ, Steven Watanabe

5 8

[MPL] A Proposal
by Bruno Dutra 16 Nov '16

16 Nov '16

Dear Community, About a year ago today, there was a proliferation of threads [1][2][3] in this mailing list concerning the future of Boost.MPL, or even whether it had a future at all, and opinions diverged widely on the matter. Many have expressed concerns about the fact Boost.MPL was long outdated and proposed major changes to open path for modernization, while some others argued against it, fearing unexpected and disastrous side-effects could propagate throughout the rest of Boost. A few questioned if it was worth it at all to spend any further resources on Boost.MPL given the fact new alternatives were coming up, such as Boost.Hana, which departed entirely from template metaprogramming, yet some argued TMP remained a competitive alternative for type computations in C++14 as it has been demonstrated by Peter Dimov in his impressive articles [4] on modern TMP. Amidst all this, a proposal by Robert Ramey [5] caught my attention and inspired me to develop what I call Metal [6], a template metaprogramming library designed on the same core principles as Boost.MPL, but written from the very beginning to take full advantage of C++11. Metal was not designed to be a strict drop in replacement for Boost.MPL though, it was rather meant to be regarded as a modern version of Boost.MPL's original API, diverging only where it could really benefit from modern C++ and that essentially means gains of several orders of magnitude in performance** and lower memory consumption. At this point Metal is very close to where I originally intended to bring it and I think it's time I gauge interest from the community on a modest proposal I've been maturing along the past year. As a modern approach to the same task that Boost.MPL was meant to address, I don't believe Boost would benefit at all from yet another TMP library that would essentially compete with Boost.MPL and even Boost.Hana in some cases, specially as maintainers of older code that depends on Boost.MPL would have to go through major refactoring efforts in order to benefit from such an addition to Boost. I would like to propose something different instead. My proposal is to make Metal officially into a new revision of Boost.MPL's API, essentially MPL2 as the original proposal by Robert Ramey put it, merging both into one single TMP library. The idea would be to provide a thin proxy for the current Boost.MPL API which would have two backends configurable by preprocessor switches: the original implementation and a another one based on Metal. This way older code using Boost.MPL could see immediate gains on performance by selecting the newer backend on supported compilers, while at the same time legacy code maintained on older compilers could still rely on Boost.MPL's impressive ability to run virtually anywhere. On the other hand, newer projects interested on pure type computations would have the newer API entirely available to them. This proposal also overcomes the problem of dealing with the maintainability of Boost.MPL, since it provides a way for smooth transition from legacy hacks required by ancient compilers into a cleaner and easier to maintain C++11 codebase, besides avoiding any breaking changes within existing code in the process. Furthermore, should this proposal make it into Boost, I would be naturally willing to take responsibility for the maintenance of Boost.MPL, which AFAIK has been maintained by the CMT for quite some time now, often with limited resources. Comparing Metal and Boost.MPL there are a few noteworthy differences. Metafunction Classes have proven themselves entirely unnecessary and have thus been removed altogether in favour of pure Lambdas (in the Boost.MPL sense). Moreover, iterators make little sense in a functional world, so these too have been removed despite the fact they may easily be emulated in the new design. Moreover Metal develops the concept of optionals, that is, its metafunctions only have a nested ::type defined when they may be successfully computed, what may be safely tested using metal::is_just and may also be used to SFINAE out of miscomputations. Finally I'd like to point out that Metal was designed to be portable across as many compilers as possible and three of the most popular ones are continuously tested using Travis and Appveyor: Clang 3.5+, GCC 4.8+ and MSVC 14 (2015). I hope this is a reasonable proposal and I look forward into your opinions about it. ** Even though I haven't published any benchmarks yet, an example follows just to back my claims regarding performance (just tested on my personal laptop running linux): //Generate a list containing 10 thousand instances of std::integral_constant, from 0 to 9999 using l = metal::enumerate_t<metal::integer<10000>>; // GCC 5.3 ~0.4 s // Clang 3.7 ~0.5 s //Transform a list containing 5 thousand numbers by squaring each element using l1 = metal::enumerate_t<metal::number<long long, 5000>>; using l2 = metal::transform_t<metal::pow<metal::_1, metal::integer<2>>, l1>; // GCC 5.3 ~5.6 s // Clang 3.7 ~3.0 s [1]: http://thread.gmane.org/gmane.comp.lib.boost.devel/257680 [2]: http://thread.gmane.org/gmane.comp.lib.boost.devel/257983 [3]: http://thread.gmane.org/gmane.comp.lib.boost.devel/258843 [4]: http://pdimov.com/cpp2/simple_cxx11_metaprogramming.html [5]: http://rrsd.com/blincubator.com/bi_suggestion/mpl-lite-or-mpl2/ [6]: http://brunocodutra.github.io/metal/ Regards, Bruno Dutra

12 48

[graph] Sync develop with master?
by Murray Cumming 12 Aug '16

12 Aug '16

Now that Boost 1.61 is out, it would be great if the various fixes in boost graph's develop branch could be merged/cherry-picked/whatever to master, please. There seem to be a couple of years of fixes that have not appeared in a release. -- Murray Cumming murrayc(a)murrayc.com www.murrayc.com

5 21

[config] RFC PR 82
by Domagoj Saric 01 Aug '16

01 Aug '16

Hi everyone, I am finally getting back to (trying to) contributing some of my personal projects to Boost. For two of those, Err (https://github.com/psiha/err) and especially Functonoid (a C++11 generalization and rewrite of my previous Boost.Function related work) I need some lower level codegen and/or optimiser control functionality (i.e. portable macros wrapping toolset specific attributes and pragmas) that I've added to my personal fork of Boost.Config and which I've now submitted in the subject PR (https://github.com/boostorg/config/pull/82) I don't expect this PR to be accepted as is/'just like that' so I'm opening this thread where we can discuss which of those changes/macros are welcome, which need more work and which, for some reason, should not be part of Boost.Config (and which, in turn then, I have to move to some 'internal implementation headers' in libraries that will need them). To avoid 'spamming' (and save time;) I'll skip the explanation of the individual macros as I expect them to mostly be self-explanatory (if not from their name then from the minimal Boost.Config documentation additions that are part of th PR). ps. I'll be on the (off) road for the next three weeks so I don't know when I'll be able to respond until I get back... -- "What Huxley teaches is that in the age of advanced technology, spiritual devastation is more likely to come from an enemy with a smiling face than from one whose countenance exudes suspicion and hate." Neil Postman

8 31

[graph] Compilation error with adjacency_list and C++11
by Sebastien Loriot (GeometryFactory) 18 Jul '16

18 Jul '16

Hello, the program below does not compile at least with g++ 5.3.1 and clang++ 3.5.2-1 when using c++11 standard. If I comment line #1 it compiles. If I change #2 to undirectedS it compiles. Is there anything wrong in my code or is it a problem in boost's? Thanks, Sebastien. #include <boost/graph/adjacency_list.hpp> struct A { A(){} A(const A& ){} // #1 A& operator=(const A&){return *this;} }; typedef boost::adjacency_list<boost::listS, boost::vecS, boost::directedS, //#2 A > Graph; int main() { Graph g; boost::add_vertex(g); return 0; }

2 2

smartptr maintained
by Karolin Varner 15 Jul '16

15 Jul '16

Hi, is smartptr still being maintained? There are four pull requests, one more than a year old. Best, Karolin Varner

2 3

New library? CallableTraits
by Barrett Adair 01 Jul '16

01 Jul '16

I posted about this a month ago, but I did not receive much response. Since then, I added an extended example use case, and I added a documentation section [1] that compares CallableTraits and Boost.FunctionTypes. I received some positive feedback this week in Aspen, and r/cpp also seemed to respond well [2], so I thought I'd give this another shot. Here are my questions for you: 1. Is there any interest in reviewing a future version of this for inclusion in Boost? 2. If so, does this belong in its own library, or should it be incorporated into Boost.TypeTraits or something similar? 3. What you like to see added, removed, renamed, or redesigned? I'd say CallableTraits is about 85% finished. Here's what's left: * Add INVOKE semantics to a couple of things for consistency (arity, etc) * Remove unused/undocumented code * Account for transaction_safe and C++17 noexcept * Finish/test the calling convention features * Finish/update the reference documentation * Write even more tests Cheers, Barrett [1] http://badair.github.io/callable_traits/doc/html/index.html#callable_traits… [2] https://www.reddit.com/r/cpp/comments/4ffmfs/callabletraits_never_write_ano… GitHub: https://github.com/badair/callable_traits Documentation from the top: http://badair.github.io/callable_traits/doc/html/index.html (reference section under construction)

5 11

Pimpl Again?
by Vladimir Batov 10 Jun '16

10 Jun '16

Don't laugh but it is only fairly recently at work that I managed to move all our supported platforms to C++11. So, then, I started moving our code to C++11 (what a delight!) and stumbled upon my old pimpl which is used quite a bit around my workplace for all its good properties... :-) Now C++11-ed piml turned out to be very small and very basic. So basic it felt it did not have the right to exist. Still, it encapsulates and enforces the "proper" pimpl properties and behavior, reduces implementation minutia and offers a recognizable deployment pattern (helps other people reading the code). Over the years IMO the technique has been proven as legitimate and useful, a basic but important building block... rather than a curiosity item. Unfortunately, despite many articles and a few Sutter's GotWs about it there is nothing ready-to-go like std::unique_ptr. I feel that pimpl and its deployment pattern need to be codified, described, "standardized" and in our toolboxes to stop/avoid everyone re-inventing the pimpl and making the same mistakes. IMO Boost is best positioned for that. Do you think we might review what I've got and/or maybe collectively come up with something better... It's no MPL or Hana but as std::unique_ptr it's one of the first "little things" I personally reach out for in my everyday work. IMO having pimpl in Boost would save quite a few hours of frustration for many. Thoughts? No pressure. I am easy either way. :-) https://github.com/yet-another-user/pimpl Docs are freshened up but still somewhat out of date. Apologies.

15 84

[announcement] GitHub permission changes
by Daniel Pfeifer 03 Jun '16

03 Jun '16

Hi all, GitHub finally allows us to set permissions on the level of granularity that we always wanted. When we moved to GitHub, we received many request like "can I please get admin rights to my repository?" We wanted to do that, but it just was not possible. As a workaround, we have created a team per repository and many of those teams had just one member. That way, we could at least give you write access to individual repositories. Not quite what you requested, but at least something. Anyway, it is now possible to set permissions on a per repository level. I have started to delete the teams with a single member and added the member as the owner of the repository. How do those changes affect you? As the owner of a repository you have write access as before, but you can also add collaborators, modify the repository descriptions, enable/disable issue tracking and wiki, and so forth. I will continue this cleanup soon, but I need your input. For teams with multiple members, I don't know whether you want to share ownership or whether you prefer to have a single owner and additional contributors. Please create new issues for that matter: https://github.com/boostorg/admin/issues Cheers, Daniel

3 2

Boost.Fiber mini-review May 23 - June 1
by Nat Goodspeed 02 Jun '16

02 Jun '16

Hi all, The Boost.Fiber candidate library by Oliver Kowalke begins a mini-review today, Monday May 23, which will close Wednesday June 1. It was last reviewed in September 2015; the verdict at that time was "not yet." Oliver has been working steadily to address review comments and to improve the library in other ways, and has brought the library back for mini-review. The updated documentation is here: http://olk.github.io/libs/fiber/doc/html/index.html The code is on the master branch of this repository: https://github.com/olk/boost-fiber/tree/master I believe it is Oliver's intention to respond to review feedback on the develop branch, leaving the master branch stable during the review. I will monitor reviews and discussion on both the boost-users@ list and the boost@ developers' list. Please include at least "fiber" and "review" in the subject line of your mail, e.g. by replying to this message. (Please reply to only ONE list, however.) I will also check the Boost Library Incubator for Fiber reviews: http://rrsd.com/blincubator.com/bi_library/fiber/?gform_post_id=859 though I check that less frequently than email. Please do remember to state in your review whether you think the library should be accepted as a Boost library. Thank you for your interest and your feedback! ----------------------------------------------------- Here follows a synopsis of issues raised during the September 2015 review: Cross-thread fiber migration: Evidently the community strongly desires the ability to transfer a suspended fiber from one thread to another. Now supported, with documentation. Cross-thread migration support implies a requirement to document the thread safety requirements of the customization API. Addressed. Standard required timing specifications: meet (30.2.4 Timing specifications [thread.req.timing]). Addressed. Adapt one or more existing test suites for thread facilities to validate the correctness of the Fiber library's synchronization constructs. The requester clarified in private mail that I misstated his suggestion: he wanted Oliver to review one or more such test suites to discover the kinds of issues that can arise with thread synchronization constructs. He has professed himself satisfied with the current state of the Fiber library's synchronization constructs. std::chrono support: ensure that wait_until() can accept any supported time_point specialization. Addressed. C++11 compatibility. Addressed. Document that this_fiber::yield() (et al.) are valid from main(), or in general from a thread function, as well as from explicitly-launched fibers. Addressed. Make shared_state lock requirements explicit: for example, make mark_ready_and_notify_() accept a std::unique_lock<>& (or &&) to force its caller to provide one. Addressed. Avoid holding mutex during condition_variable::notify_*() calls. Addressed. packaged_task must not decay-copy its task arguments. Addressed. Align fibers::async() signature, result description and invoke_helper implementation with std::async(). Avoid returning std::move(...). Addressed. Wait list implementation: try an intrusive linked list of fiber_context objects. Addressed. Avoid sleeping thread when no fibers are ready -- block on external event. Better handling of waiting tasks (decentralized wait queues?). Addressed. Optimization to resume awakened fiber on the thread that awakens it. Hooks provided. Template redundancy: eliminate duplication between specializations for T, T& and void. The future, shared_future, shared_state, promise and task_object templates were specifically cited. Addressed. Leverage predicate-based condition::wait() overload internally. Addressed. Nested schedulers: make schedulers be schedulable entities themselves. Not implemented. Improve robustness of `promise' handling in Asynchronous Callbacks documentation. Avoid overconfident remarks about it. Addressed. Fix Note overstating the requirements on condition_variable::wait(). Addressed.

2 3

[optional] using name boost::in_place -- need your opinion/advice
by Andrzej Krzemienski 30 May '16

30 May '16

Hi Everyone, I have stumbled upon a problem that I do not know how to address. I would like to seek an advice from the people in this list. I am trying to make boost::optional resemble std::optional (where it is reasonably easy to achieve). std::optional has this nice and useful "placement" constructor: std::optional<std::mutex> m {std::in_place}; std::in_place is a tag type, that instructs std::optional to create an object using placement-new syntax, from the provided arguments (zero in the example), without incurring any move construction. I cannot easily copy 1-to-1 this solution, because in namespace boost name in_place is reserved for the in-place factories: http://www.boost.org/doc/libs/1_61_0/libs/utility/in_place_factories.html I could simply go with a different name for a tag, but something tells me it would introduce an unnecessary complications for users that want to migrate from one optional to another. I could hack in-place factories so that they can also be used as a tag, although, I am not sure it is doable in a type-safe manner, and if it would not confuse people to have this boost::in_place do a number of different things. I could use a different namespace, but again, this might look surprising.I am a bit torn. I wonder if anyone here needed to face a similar problem, and if you can think of an elegant solution. Thanks, &rzej

4 12

[Boost.Test][Boot.Timer v2] header only boost.test conflicts with Boot.Timer V2
by Tan, Tom (Shanghai) 30 May '16

30 May '16

This following simple snippet would yield an error with visual studio 2015 for both boost1.60.61: boost/timer/timer.hpp(32): error C2757: 'timer': a symbol with this name already exists and therefore this name cannot be used as a namespace name // compiled with cl.exe /EHsc #define BOOST_TEST_MODULE test #include <boost/test/included/unit_test.hpp> #include <boost/timer/timer.hpp> The following variants are ok // compiled with cl.exe /EHsc #define BOOST_TEST_MODULE test #include <boost/test/unit_test.hpp> #include <boost/timer/timer.hpp> Or // compiled with cl.exe /EHsc #define BOOST_TEST_MODULE test #include <boost/test/included/unit_test.hpp> #include <boost/timer.hpp> It looks like Boost.Test is relying on boost.timer v1, which is deprecated in documentation and conflict with V2.

3 2

[boost.timer v2] auto_cpu_timer does not compile
by Tan, Tom (Shanghai) 29 May '16

29 May '16

This following snippet generates an error with VS2015 both fo 1.60&1.61: libboost_timer-vc140-mt-s-1_61.lib(cpu_timer.obj) : error LNK2019: unresolved external symbol "public: static class boost::chrono::time_point<class boost::chrono::steady_clock,class boost::chrono::duration<__int64,class boost::ratio<1,1000000000> > > __cdecl boost::chrono::steady_clock::now(void)" (?now@steady_clock@chrono@boost@@SA?AV?$time_point@Vsteady_clock@chrono@boost@@V?$duration@_JV?$ratio@$00$0DLJKMKAA@@boost@@@23@@23@XZ) referenced in function "public: struct boost::timer::cpu_times __cdecl boost::timer::cpu_timer::elapsed(void)const " (?elapsed@cpu_timer@timer@boost@@QEBA?AUcpu_times@23@XZ) // compile with cl.exe /EHSc #include <boost/timer/timer.hpp> int main() { boost::timer::auto_cpu_timer t; } What's interesting is that uncommenting line #14 in file boost/timer/timer.hpp would get rid of this error. - Why is there such a line but commented out there? - Is there a better way to get it through without modifying this file - the binary is downloaded from sourceforge, not a custom build. - Thanks.

1 0

Re: [boost] Boost.Fiber mini-review May 23 - June 1
by Bjorn Reese 28 May '16

28 May '16

On 05/23/2016 06:20 PM, Nat Goodspeed wrote: > Please do remember to state in your review whether you think the > library should be accepted as a Boost library. Yes, I vote for unconditional acceptance of Boost.Fiber. I did not participate in the formal review (due to time constraints), so I am not going to address the individual issues. I happened to have studied Boost.Fiber recently because I came across limitations of the inter-coroutine interaction in Boost.Coroutine, and Boost.Fiber addresses these limitations rather nicely. I especially like the message passing channels, which makes Boost.Fiber an obvious choice for building a coroutine-based actor framework. The only finding I have is that several Boost.Fiber headers include detail headers from Boost.Context. While this is not a problem per se (because Oliver is the maintainer of both libraries), it may be an idea to consider if these detail headers should be made public.

1 0

[iterator] strided, recursive variants
by Jeremy Murphy 28 May '16

28 May '16

Dear Boosters, I was wondering why a strided iterator has not made it into the Boost.Iterator library? There is a strided range in Boost.Range based on a private implementation of such an iterator, and Boost.Compute has their own implementation too. Just an untied loose end? On a related note, what about variants of such iterators that work in recursive algorithms? That is, if you stride a strided iterator, existing implementations will keep nesting the stride type, which the compiler fails to do recursively because there is no stopping criterion. So I wrote a variant of strided iterator that when you stride a strided iterator, it just multiplies the two strides together and takes the base pointer type from the original strided iterator. I assume some of the other iterator adaptors are limited in the same way. Anyway, it's no big deal to me, but I just thought I'd canvas whether that's something people (especially the maintainers) are interested in? Cheers. Jeremy

1 0

compiling mysql-5.7.12, cannot use DTRACE
by Mariano Apilado 26 May '16

26 May '16

Hi, I get the following error when compiling mysql-5.7.12 on Nexenta 4.0.4 OS ( Formerly known as Open Solaris / Illumos ). To temporarily bypass this problem, I chose not to use DTRACE with the compiler options. However, it should be fixed to use DTRACE. # cmake -DENABLE_DTRACE=0 Thanks and Regards,Mariano [ 15%] Linking CXX static library libmysys_ssl.a cd /usr/local/mysql-5.7.12/mysys_ssl && /usr/local/bin/cmake -P CMakeFiles/mysys_ssl.dir/cmake_clean_target.cmake cd /usr/local/mysql-5.7.12/mysys_ssl/CMakeFiles/mysys_ssl.dir && /usr/local/bin/cmake -DDTRACE=/usr/sbin/dtrace -DOUTFILE=/usr/local/mysql-5.7.12/mysys_ssl/CMakeFiles/mysys_ssl.dir/mysys_ssl_dtrace.o -DDFILE=/usr/local/mysql-5.7.12/include/probes_mysql.d -DDTRACE_FLAGS=-64 -DDIRS=. -DTYPE=STATIC_LIBRARY -P /usr/local/mysql-5.7.12/cmake/dtrace_prelink.cmake dtrace: failed to link script /usr/local/mysql-5.7.12/include/probes_mysql.d: No probe sites found for declared provider cd /usr/local/mysql-5.7.12/mysys_ssl && /usr/local/bin/cmake -E cmake_link_script CMakeFiles/mysys_ssl.dir/link.txt --verbose=1 /usr/bin/ar qc libmysys_ssl.a CMakeFiles/mysys_ssl.dir/crypt_genhash_impl.cc.o CMakeFiles/mysys_ssl.dir/mf_tempdir.cc.o CMakeFiles/mysys_ssl.dir/my_default.cc.o CMakeFiles/mysys_ssl.dir/my_getopt.cc.o CMakeFiles/mysys_ssl.dir/my_aes.cc.o CMakeFiles/mysys_ssl.dir/my_sha1.cc.o CMakeFiles/mysys_ssl.dir/my_sha2.cc.o CMakeFiles/mysys_ssl.dir/my_md5.cc.o CMakeFiles/mysys_ssl.dir/my_rnd.cc.o CMakeFiles/mysys_ssl.dir/my_murmur3.cc.o CMakeFiles/mysys_ssl.dir/my_aes_yassl.cc.o /usr/bin/ranlib libmysys_ssl.a cd /usr/local/mysql-5.7.12/mysys_ssl && /usr/bin/ar r /usr/local/mysql-5.7.12/mysys_ssl/libmysys_ssl.a /usr/local/mysql-5.7.12/mysys_ssl/CMakeFiles/mysys_ssl.dir/mysys_ssl_dtrace.o ar: cannot open /usr/local/mysql-5.7.12/mysys_ssl/CMakeFiles/mysys_ssl.dir/mysys_ssl_dtrace.o: No such file or directory ar: /usr/local/mysql-5.7.12/mysys_ssl/CMakeFiles/mysys_ssl.dir/mysys_ssl_dtrace.o not found gmake[2]: *** [mysys_ssl/libmysys_ssl.a] Error 1 gmake[2]: *** Deleting file `mysys_ssl/libmysys_ssl.a' gmake[2]: Leaving directory `/usr/local/mysql-5.7.12' gmake[1]: *** [mysys_ssl/CMakeFiles/mysys_ssl.dir/all] Error 2 gmake[1]: Leaving directory `/usr/local/mysql-5.7.12’ gmake: *** [all] Error 2

2 1

Call for Papers for Meeting C++ 2016 ends on Friday night!
by Jens Weller 25 May '16

25 May '16

Hello Boost Community! a short reminder, that the deadline is coming up for submitting your talk to this years Meeting C++ conference! Meeting C++ 2016 Page: http://meetingcpp.com/index.php/mcpp2016.html Talk submission page: https://meetingcpp.com/mcpp/submittalk/ thanks, Jens Weller

1 0

Error while compiling mysql-5.7.12 /usr/xpg4/include/term.h:596: error: conflicting types for ‘tgoto’
by Mariano Apilado 25 May '16

25 May '16

Hi, I get the following error when compiling mysql-5.7.12 on Nexenta 4.0.4 OS ( Formerly known as Open Solaris / Illumos ). In order to temporarily bypass this problem, I commented out. However, this is not the solution. /usr/local/mysql-5.7.12/cmd-line-utils/libedit/terminal.c:60: /* *#ifdef HAVE_CURSES_H *#include <curses.h> *#elif HAVE_NCURSES_H *#include <ncurses.h> *#endif */ Thanks and Regards,Mariano Error: [ 4%] Building C object cmd-line-utils/libedit/CMakeFiles/edit.dir/terminal.c.o cd /usr/local/mysql-5.7.12/cmd-line-utils/libedit && /usr/bin/gcc -DHAVE_CONFIG_H -D_FILE_OFFSET_BITS=64 -D_POSIX_PTHREAD_SEMANTICS -D_PTHREADS -D_REENTRANT -D__EXTENSIONS__ -I/usr/local/mysql-5.7.12/cmd-line-utils/libedit -I/usr/local/mysql-5.7.12/include -I/usr/local/mysql-5.7.12/extra/rapidjson/include -I/usr/local/mysql-5.7.12/libbinlogevents/include -I/usr/local/mysql-5.7.12/libbinlogevents/export -I/usr/xpg4/include -m64 -O3 -g -fabi-version=2 -fno-omit-frame-pointer -fno-strict-aliasing -DDBUG_OFF -fPIC -m64 -lstdc++ -R'RIGIN/../lib' -R/usr/lib/amd64 -o CMakeFiles/edit.dir/terminal.c.o -c /usr/local/mysql-5.7.12/cmd-line-utils/libedit/terminal.c In file included from /usr/xpg4/include/curses.h:43, from /usr/local/mysql-5.7.12/cmd-line-utils/libedit/terminal.c:60: /usr/xpg4/include/term.h:596: error: conflicting types for ‘tgoto’ /usr/local/mysql-5.7.12/cmd-line-utils/libedit/sys.h:137: note: previous declaration of ‘tgoto’ was here gmake[2]: *** [cmd-line-utils/libedit/CMakeFiles/edit.dir/terminal.c.o] Error 1 gmake[2]: Leaving directory `/usr/local/mysql-5.7.12' gmake[1]: *** [cmd-line-utils/libedit/CMakeFiles/edit.dir/all] Error 2 gmake[1]: Leaving directory `/usr/local/mysql-5.7.12’ gmake: *** [all] Error 2

1 0

Having problems installing mysql 5.7.12 with boost ELF 32 bit, wrong ELF Class
by Mariano Apilado 25 May '16

25 May '16

Hi, I get the following error when compiling mysql-5.7.12 on Nexenta 4.0.4 OS ( Formerly known as Open Solaris / Illumos ). How do I fix the compile options or get the necessary files required to make the compile successful? Thanks and Regards, Mariano The files libboost_system.so and libboost_chrono.so are the wrong ELF class: ELFCLASS32. root@nex-01-test:/volumes# file /root/boost_1_59_0/stage/lib/libboost_system.so /root/boost_1_59_0/stage/lib/libboost_system.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available root@nex-01-test:/volumes# file /root/boost_1_59_0/stage/lib/libboost_system.so /root/boost_1_59_0/stage/lib/libboost_system.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available Error Message: [ 95%] Linking CXX executable ../mysqlpump cd /root/mysql-5.7.12/client/dump && /usr/local/bin/cmake -E cmake_link_script CMakeFiles/mysqlpump.dir/link.txt --verbose=1 /usr/bin/g++ -w -fpermissive -m64 -Wall -Wextra -Wformat-security -Wvla -Woverloaded-virtual -Wno-unused-parameter -O3 -g -fabi-version=2 -fno-omit-frame-pointer -fno-strict-aliasing -DDBUG_OFF -R'$ORIGIN/../lib' -R/usr/lib/amd64 CMakeFiles/mysqlpump.dir/program.cc.o -o ../mysqlpump libmysqlpump_lib.a -lboost_system -lboost_chrono ../base/libclient_base.a ../../libmysql/libmysqlclient.a -lsocket -lnsl -lm ../../extra/liblz4_lib.a ld: fatal: file /root/boost_1_59_0/stage/lib/libboost_system.so: wrong ELF class: ELFCLASS32 ld: fatal: file /root/boost_1_59_0/stage/lib/libboost_chrono.so: wrong ELF class: ELFCLASS32 ld: fatal: file processing errors. No output written to ../mysqlpump collect2: ld returned 1 exit status gmake[2]: *** [client/mysqlpump] Error 1 gmake[2]: Leaving directory `/root/mysql-5.7.12' gmake[1]: *** [client/dump/CMakeFiles/mysqlpump.dir/all] Error 2 gmake[1]: Leaving directory `/root/mysql-5.7.12’ gmake: *** [all] Error 2

2 1

[compute] [OS X 10.11.5] [GeForce GT 750M] Segmentation fault
by Prashant 25 May '16

25 May '16

Hi, Am trying to sort a vector on GPU (GeForce GT 750M) using example code which generates SEGV. However, it runs fine on Iris Pro (Intel(R) Core(TM) i7-4850HQ CPU). We observe SEGV when size is 10 million. When the size is 5 million, following exception is thrown: boost/1_61_0/include/boost/compute/command_queue.hpp(453): Throw in function boost::compute::event boost::compute::command_queue::enqueue_write_buffer(const boost::compute::buffer &, size_t, size_t, const void *, const boost::compute::wait_list &) Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector< boost::compute::opencl_error> > std::exception::what: Invalid Value Another observation: if the size of vector is 50 million the sorting works fine, though the timings are worse than Iris Pro. Also, when is size is 100 million, the binary causes the OS to crash. Compiler details: clang++ --version Apple LLVM version 7.3.0 (clang-703.0.31) Target: x86_64-apple-darwin15.5.0 Thread model: posix OS: System Version: OS X 10.11.5 (15F34) Kernel Version: Darwin 15.5.0 Regards, Prashant ----------------------------Cut here------------------------------------- #include <iostream> #include <vector> #include <algorithm> #include <boost/foreach.hpp> #include <boost/compute/core.hpp> #include <boost/compute/platform.hpp> #include <boost/compute/algorithm.hpp> #include <boost/compute/container/vector.hpp> #include <boost/compute/functional/math.hpp> #include <boost/compute/types/builtin.hpp> #include <boost/compute/function.hpp> #include <boost/chrono/include.hpp> #include <boost/exception/all.hpp> namespace compute = boost::compute; int main(int argc, char* argv[]) { if (argc != 2) { std::cout << "Usage: " << argv[0] << " <size> " << std::endl; return 0; } // generate random data on the host std::vector<float> host_vector(atoi(argv[1])); std::generate(host_vector.begin(), host_vector.end(), rand); std::cout << "===============CPU==================\n"; for (size_t k=0; k<5; k++) { std::vector<float> host_copy_vector(host_vector); auto start = std::chrono::high_resolution_clock::now(); std::sort(host_copy_vector.begin(), host_copy_vector.end()); auto duration = std::chrono::duration_cast<std::chrono::milliseconds> (std::chrono::high_resolution_clock::now() - start); std::cout << "time: iteration ("<< k << ") : " << duration.count() << " ms" << std::endl; } std::vector<compute::platform> platforms = compute::system::platforms(); for(size_t i = 0; i < platforms.size(); i++){ const compute::platform &platform = platforms[i]; std::cout << "Platform '" << platform.name() << "'" << std::endl; std::vector<compute::device> devices = platform.devices(); for(size_t j = 0; j < devices.size(); j++){ const compute::device &device = devices[j]; std::string type; if(device.type() & compute::device::gpu) type = "GPU Device"; else if(device.type() & compute::device::cpu) type = "CPU Device"; else if(device.type() & compute::device::accelerator) type = "Accelerator Device"; else type = "Unknown Device"; if (type != "GPU Device") { std::cout << "Ignoring non GPU devices.\n"; continue; } std::cout << "====\n"; std::cout << " " << type << ": " << device.name() << std::endl; std::cout << "====\n"; compute::context context(device); compute::command_queue queue(context, device); for (size_t k=0; k<5; k++) { compute::vector<float> device_vector(host_vector.size(), context); // copy data from the host to the device compute::copy( host_vector.begin(), host_vector.end(), device_vector.begin(), queue ); auto start = std::chrono::high_resolution_clock::now(); try { compute::sort(device_vector.begin(), device_vector.end(), queue); } catch (boost::exception & e) { std::cerr << diagnostic_information(e); break; } auto duration = std::chrono::duration_cast<std::chrono::milliseconds> (std::chrono::high_resolution_clock::now() - start); std::cout << "time: iteration ("<< k << ") : " << duration.count() << " ms" << std::endl; } std::cout << "====\n"; } } return 0; }

2 1

[multiprecision] compilation failure
by Raffi Enficiaud 24 May '16

24 May '16

Hi, I have the following failure on develop from multiprecision (unit tests of boost.test): In file included from writing-test-ts/fp-multiprecision-comparison-test.cpp:23:0: ../../../boost/multiprecision/cpp_dec_float.hpp: In member function ?std::size_t boost::multiprecision::backends::cpp_dec_float<Digits10, ExponentType, Allocator>::hash() const?: ../../../boost/multiprecision/cpp_dec_float.hpp:264:10: error: ?hash_combine? is not a member of ?boost? boost::hash_combine(result, data[i]); Thanks, Raffi

3 2

Request for a "Policy Review" regarding 'CMakeLists.txt'
by David Sankel 24 May '16

24 May '16

A question has been brought up regarding whether or not a Boost library author is permitted to include a 'CMakeLists.txt' file in the root of the directory. This stemmed from a discussion at C++Now 2016 which included several members of the Boost Steering Committee and a sampling of the Boost community. We recommend and propose that the Boost Guidelines are modified to allow library authors, at their own discretion, to include a 'CMakeLists.txt' file in their library's top-level directory. * Several libraries, such as Boost.Hana and Boost.Spirit, have two distribution mechanisms: one as distributed with Boost and the other as an independent package. The requirement that these libraries not include a 'CMakeLists.txt' as part of their Boost distribution creates a maintenance burden for authors or otherwise hurts usability of the independent distribution. * Several companies have revealed that they are building Boost with their own custom CMake scripts. The suggested policy change would enable authors to relieve the infrastructure cost of their CMake users and unify how their library is built. * CMake is, by far, the most popular build system for C++. Allowing authors to support CMake users in addition to BJam will help the Boost ecosystem to grow and thrive by lowering the barriers to access. -- David Sankel

51 224

Boost.Fit review Mars 3-20 result
by Vicente J. Botet Escriba 24 May '16

24 May '16

Hi, I will be out for two weeks and I wanted to at least give the result of the Boost.Fit library review even if I would need more time to have a complete report. Summary ======= The review of the proposed Boost.Fit library ended on Mars 20, 2016. The verdict is: Conditional acceptance (a new review is needed) There were too much concerns about the documentation and what exactly this library is proposing and not enough reviews commenting the design, code and test for each one of the proposed functions. From the review discussion I deduce that there is some interest in the library, and that some people don't understand yet what the library is proposing. Paul has started already to take in account some if the issues raised during the review and a lot of them must be resolved before we re-try a new review. There were some discussion about the name of the library, but there were no consensus. Paul is free to change the name of his library and see how people react. On behalf of the Boost community, I would like to thank Paul Fultz for the work he has put into the Fit library so far. I encourage him to continue to evolve this library and to bring it back for a new review. We had seven 6 formal votes, and 2 more votes without a complete review abbreviated here: Steaven Watanabe: No in his current state Zach Laine : Conditinal acceptance Krzysztof Jusiak: Accepted Artyom Beilis : Rejected Peter Dimov : Accepted (no review) Manuel Sancher : Accepted (no review) Rob Stewart : Conditinal acceptance ??? Louis Dionne : Conditinal acceptance There were other people that participated on the review giving their advice respect to a specific issue. I thank each of these reviewers, and indeed everyone who invested some time participating in the discussions. If you feel that I have misrepresented your position, or have omitted or garbled an important point, please respond: the archived mail thread should accurately reflect the will of the community, even if this message does not. Detailed Report =============== You will need to wait yet for a month before I will be able to do it. On the mean time there are a lot of issues that must be addressed and that are part of the github issues. For more information see: Github:https://github.com/pfultz2/Fit/tree/boost Issues:https://github.com/pfultz2/Fit/issues Documentation:http://pfultz2.github.io/Fit/doc/html/ Hopping this helps, Vicente Botet Escriba

11 26

b2 looks for tools/inspect/build/Jamfile
by Peter Dimov 23 May '16

23 May '16

I'm experimenting with a partial Boost clone, the superproject, tools/build, libs/bind, libs/config and few others, and when trying to build the tests, I'm getting the following error: D:\tmp\boost\libs\bind\test>..\..\..\b2 toolset=msvc-10.0 D:/tmp/boost/tools/build/src/build\project.jam:262: in find-jamfile from module project error: Unable to load Jamfile. error: Could not find a Jamfile in directory '../../../tools/inspect/build'. error: Attempted to find it with pattern '[Bb]uild.jam [Jj]amfile.v2 [Jj]amfile [Jj]amfile. [Jj]amfile.jam'. error: Please consult the documentation at 'http://www.boost.org'. D:/tmp/boost/tools/build/src/build\project.jam:280: in load-jamfile from module project D:/tmp/boost/tools/build/src/build\project.jam:64: in load from module project D:/tmp/boost/tools/build/src/build\project.jam:89: in load-used-projects from mo dule project D:/tmp/boost/tools/build/src/build\project.jam:75: in load from module project D:/tmp/boost/tools/build/src/build\project.jam:113: in load-parent from module p roject D:/tmp/boost/tools/build/src/build\project.jam:464: in initialize from module pr oject D:/tmp/boost/tools/build/src/build\project.jam:306: in load-jamfile from module project D:/tmp/boost/tools/build/src/build\project.jam:64: in load from module project D:/tmp/boost/tools/build/src/build\project.jam:113: in load-parent from module p roject D:/tmp/boost/tools/build/src/build\project.jam:464: in initialize from module pr oject D:/tmp/boost/tools/build/src/build\project.jam:306: in load-jamfile from module project D:/tmp/boost/tools/build/src/build\project.jam:64: in load from module project D:/tmp/boost/tools/build/src/build\project.jam:145: in project.find from module project D:/tmp/boost/tools/build/src\build-system.jam:535: in load from module build-sys tem D:\tmp\boost\tools\build\src/kernel\modules.jam:295: in import from module modul es D:\tmp\boost\tools\build\src/kernel/bootstrap.jam:139: in boost-build from modul e D:\tmp\boost\boost-build.jam:17: in module scope from module Does anyone have an idea why b2 looks for the tools/inspect Jamfile? I don't remember this being a problem before when I tried a stripped-down installation.

6 14

doctest - the lightest feature rich C++ single header testing framework - if it can enter boost and if it/boost will benefit from that
by Viktor Kirilov 23 May '16

23 May '16

Hello! I just released doctest - https://github.com/onqtam/doctest All the info about it can be found on github. So do you think it can enter the boost project? How much work will it take to get it into boost except for adding boost in the title? Will it or boost benefit from that addition? Also I've sort-of followed the Best Practice Handbook (I consider it very valuable) as much as possible - https://svn.boost.org/trac/boost/wiki/BestPracticeHandbook Any feedback will be greatly appreciated. Thanks!

10 19

Rebooting Boost: Call for Lightning Talks @ CppCon
by Niall Douglas 23 May '16

23 May '16

At C++ Now a number of informal meetings showed there to be frustrations with the current ecosystem around the Boost C++ Libraries (to paraphrase a founder of Boost, "Boost is supposed to serve *the entire C++ community; it isn't Boost's goal to serve Boost's community*". Recent and recurrent boost-dev discussions have raised the lack of cmake based tooling; lack of ABI management and the consequent ODR violation when mixing Boost versions in the same process; the anti-social behaviour of Boost towards library end users, new ideas, new blood and the wider C++ community; and the chronic lack of maintenance of up to half the Boost libraries. One question which needs to be answered is whether a clean reboot of Boost from the first principles of proving high quality C++ libraries well suited for use with the latest C++ standard is viable. This new collection of C++ libraries would be started completely from scratch (even if some existing libraries were ported into the new organisation), so ANYTHING is possible. All we need is a critical mass of library developers willing to collaborate on developing a shared infrastructure mutually beneficial to all participants, whether library developer or library end user. To that end of discovering if this critical mass is there, five minute lightning talk topics are requested for CppCon this September on this topic: "What design pattern, practice or idiom should a standards aspiring collection of C++ 14/17 libraries share?" Please keep each talk topic focused on a single design pattern, practice or idiom (see suggested talk format below). Each speaker may submit up to THREE talk topics (not all may be accepted if there are a lack of slots, so please rank them in order of preference). Please send your talk topics to me privately by email, only if sufficient numbers present to fill a session will your name and your talk topic be shared with the CppCon Programme Committee. We'll try to arrange a short panel session at the end so attendees can ask questions of the speakers. After the lightning talk we'll arrange a restaurant so all the speakers and any interested attendees can dine together, followed by a night in a Bellevue bar. If after the dust has settled it is felt there is a critical mass sufficient to reboot a brand shiny new edition of Boost, we'll start development! I should *stress* that it is up to the CppCon Programme Committee whether these lightning talks are approved or not. I'll just copy and paste your proposed talk to the CppCon PC as-is. If insufficient lightning talk topics are received by me to fill a 60 minute session, I'll withdraw this talk proposal from CppCon. Suggested talk format ================ Five minutes is not much time, so here is a suggested lightning talk outline: 1. A current widely practiced library design pattern (show example). 2. The problems it generates for library users or maintainers. 3. Your proposed alternative design pattern (show example). 4. The problems the alternative design pattern fixes. 5. Any mockup, prototype or even live demo (!) of the alternative design pattern in action. Suggested talk themes might be documentation, packaging, distribution, testing, tooling, quality assessment, barriers to entry, governance, strategy, important gaps in the standard libraries, automation and deprecation/removal policies. Here is an example of such a lightning talk: 1. Current design pattern: Library v1.00: namespace boost { namespace lib { void foo(size_t, char); } } User code: boost::lib::foo(100, 'n'); 2. Problem: Library v1.01: namespace boost { namespace lib { void foo(char, size_t); } } User code: boost::lib::foo(100, 'n'); // oh oh! 3. Alternative: Library v1.00: namespace boost { namespace lib { inline namespace v100 { void foo(size_t, char); } } } #define BOOST_LIB_NAMESPACE_V100 boost::lib::v100 Library v1.01: namespace boost { namespace lib { inline namespace v101 { void foo(char, size_t); } } } #define BOOST_LIB_NAMESPACE_V101 boost::lib::v101 User code: // Mount v100 of Boost.Lib into "lib" namespace lib=BOOST_LIB_NAMESPACE_V100; lib::foo(100, 'n'); // ABI stable! No ODR violation possible! 4. Problems fixed: a) Mixing incompatible versions of individual Boost libraries in the same process (or even translation unit) is now safe. b) Libraries can now depend on other libraries without worrying about breaking code which depends on them which uses a different version of the same dependency. This greatly helps reduce change ripple effects. c) Forward compatibility or alternative implementation shims are now very easy to implement e.g. library users can externally configure either Boost.Filesystem or std::experimental::filesystem for your library to use, your code simply refers to _some_ Filesystem TS implementation e.g. namespace filesystem = FILESYSTEM_TS_IMPLEMENTATION; filesystem::path mypath; -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

8 10

@boost-admins: permission to git-repo removed?!
by Oliver Kowalke 23 May '16

23 May '16

Hi, I can't push commits to git-repo boost.coroutine2: remote: Invalid username or password. fatal: Authentication failed for 'https://github.com/boostorg/coroutine2/' Could you please re-add user 'olk', please. thx, Oliver

3 3

What C++14/1z standard or TS libraries would you like to have available on a C++11 compiler?
by Vicente J. Botet Escriba 23 May '16

23 May '16

Hi, I would like to have your feedback on C++ standard library features you would like to have available for a C++11 compiler. The idea would be to present a Boost.StdExtensions library that would provide some of these features for review with some of these features. Please , let me know if you are interested in participating in this project and working on some specific parts. This library should avoid as much Boost dependencies as possible. How the library could be structured? I believe that it should follow the C++ standard files. Which folder should be used? boost/stdext? boost/stdext11? Which namespace? boost::stdext? I have prefixed with a * the lines that interest myself and with VBE* those that I could work on. The features that need compiler help or that need C++14/17 language features are excluded and prefixed by N/A. Please be free to add a * if you are interested and your name as well if you want to participate. Best, Vicente P.S. The project could be as well extended to C++98 compilers with C++11 standard libraries (But I would not have time to invest in). P.S.S. I would also be interested in extend the project to extended to C++14 compilers. C++14 standard libraries ================ VBE* N3658 - Compile-time integer sequences * N3654 - Quoted Strings N3656 - make_unique VBE* N3462 - std::result_of and SFINAE * N3668 std::exchange() N3469 Constexpr Library Additions: chrono N3470 Constexpr Library Additions: containers N3471 Constexpr Library Additions: utilities N3302 Constexpr Library Additions: complex VBE* N3545 An Incremental Improvement to integral_constant N3644 Null Forward Iterators N3670 Addressing Tuples by Type N3671 Making non-modifying sequence operations more robust N3642 User-defined Literals VBE* N3655 TransformationTraits Redux (excluding part 4) N3657 Adding heterogeneous comparison lookup to associative containers N3669 Fixing constexpr member functions without const N3659 Shared Locking in C++ N3779 User-defined Literals for std::complex N3789 Constexpr Library Additions: functional N3887 Consistent Metafunction Aliases N3891 A proposal to rename shared_mutex to shared_timed_mutex C++1z standard libraries ================ VBE* N3911 TransformationTrait Alias void_t N4089 Safe conversions in unique_ptr<T[]> VBE* N4169 A proposal to add invoke function template N4258 Cleaning-up noexcept in the Library. N4277 TriviallyCopyable reference_wrapper. N4279 Improved insertion interface for unique-key maps. VBE* N4280 Non-member size() and more N4284 Contiguous Iterators. N4387 improving pair and tuple VBE* N4389 bool_constant N4508 shared_mutex for C++17 N4366 LWG 2228 missing SFINAE rule N4510 Minimal incomplete type support for standard containers N/A* P0006R0 Adopt Type Traits Variable Templates for C++17. VBE* P0092R1 Polishing <chrono> VBE* P0007R1 Constant View: A proposal for a std::as_const helper function template. VBE* P0156R0 Variadic lock_guard(rev 3). P0074R0 Making std::owner_less more flexible VBE* P0013R1 Logical type traits rev 2 P0024R2 The Parallelism TS Should be Standardized P0226R1 Mathematical Special Functions for C++17 VBE* P0220R1 Adopt Library Fundamentals V1 TS Components for C++17 P0218R1 Adopt the File System TS for C++17 P0033R1 Re-enabling shared_from_this VBE* P0005R4 Adopt not_fn from Library Fundamentals 2 for C++17 P0152R1 constexpr atomic::is_always_lock_free N/A* P0185R1 Adding [nothrow-]swappable traits P0253R1 Fixing a design mistake in the searchers interface P0025R0 An algorithm to "clamp" a value between a pair of boundary values P0154R1 constexpr std::hardware_{constructive,destructive}_interference_size P0030R1 Proposal to Introduce a 3-Argument Overload to std::hypot P0031R0 A Proposal to Add Constexpr Modifiers to reverse_iterator, move_iterator, array and Range Access P0272R1 Give std::string a non-const .data() member function VBE* P0077R2 is_callable, the missing INVOKE related trait Fundamental V1 TS ============ Uses-allocator construction Changes to std::shared_ptr and weak_ptr Additions to std::function Additions to std::promise Additions to std::packaged_task Class erased_type VBE* Calling a function with a tuple of arguments N/A Type traits (_v) Other type transformations Compile-time Rational Arithmetic Time Utilities System Error Support Class memory_resource Class template polymorphic_allocator Template alias resource_adaptor Global memory resources Pool resource classes Class monotonic_buffer_resource Alias templates using polymorphic memory resource Searchers * Optional Objects Initial implementation * class any * string_view memory Algorithms library

6 8

Boost 1.61.0 has been released
by Rene Rivera 22 May '16

22 May '16

Release 1.61.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains four new libraries and numerous enhancements and bug fixes for existing libraries. New Libraries * Compute: Parallel/GPU-computing library, from Kyle Lutz. * DLL: Library for comfortable work with DLL and DSO, from Renato Tegon Forti and Antony Polukhin * Hana: A modern C++ metaprogramming library, from Louis Dionne. * Metaparse: A library for generating compile time parsers parsing embedded DSL code as part of the C++ compilation process, from Abel Sinkovics. For details, including download links, see http://www.boost.org/users/news/version_1.61.0 You can also download directly from SourceForge: http://sourceforge.net/projects/boost/files/boost/1.61.0/ Tom Kent has made pre-built windows binaries, and they are available at: https://sourceforge.net/projects/boost/files/boost-binaries/1.61.0/ To install this release on your system, see http://www.boost.org/doc/libs/release/more/getting_started/index.html Thanks, --The Boost release team Vladimir Prus Rene Rivera Marshall Clow Eric Niebler Daniel James Beman Dawes

11 18

Boost Evolution
by Robert Ramey 21 May '16

21 May '16

What I would like to see is more encouragement for the idea of boost evolution. But I have well defined ideas about how that should occur. I articulated these ideas is quite a bit of detail at C++Now in 2015 to a packed house. It wasn't recorded so you'll have to take my word for it. All is not lost though. For those who might be interested I kept my practice recordings for the narrative on the slides and attached them to each slide. So you can get a good feeling for the presentation by checking out http://www.blincubator.com/C++Now2015/index.html If you do this don't forget to checkout the last two slides (including the audio)! in real life it was much better!!! When I articulated my particular suggestions at the conference there was a lot of push back and I sort of lost control of things. On the other hand, there was a lot of enthusiasm for my "call to action". I didn't expect any drastic changes. But as I look back a year I do see some real progress. I see: a) more and better reviews b) more interest, discussion and criticism of documentation c) 30 libraries in the incubator. Some have already been added to boost. d) Now movement on opening up the build/test system to evolution. e) A program in place to make more resources available for maintaining existing libraries. The complains of unmaintained libraries have diminished by quite a bit - I don't know for a fact that this is related to this program - maybe it's just a happy coincidence. A couple of things have made much progress. a) modular deployment and dependency management. No surprise here as this is a job of major, major difficulty. b) policy for library deprecation - not really hard but really very low priority. c) improvements in incubator - no real progress - but it's probably as good as it needs to be. d) boost website improvement - no discernible progress. There is one big lesson from all this: a) Boost is not a company - we don't take direction from the top. b) Boost is not a government - we actually do something. c) Boost is a religion - want something changed, start preaching. Get other people on board. Convince people people to start doing something. Take a look at the CMake history. There was a huge effort undertaken from the top to switch to CMake for build / test. It was a failure because it tried to do it from the top down. I'm thinking that the promoters of this idea concluded that the problem wasn't ambitious enough and added deployment to the task and built rypll. This had as key collaborators our most capable and hard core developers - including David Abrahams and Eric Neibler. Huge amount of expended effort but not much came out of it. I think if you want to help boost evolve - remember Boost is a religion. We are the jesuits of C++. Bjarn's marines - the tip of the spear. We ambush the world with a new idea which builds or replaces something else. We do it in an insidious manner. The opening up to CMake has proceeded steadily over years until it's a the cusp of victory. No one saw it coming and here it is. The world doesn't change from great initiatives, it changes when the old order collapses while espending it's existence to deny change. I've been told on this is a right wing world view - and so it is - oh well. So I encourage those who want to contribute to Boost and by extension C++ to consider using this approach. I think you'll be more successful. Robert Ramey

19 47

A comment on cmake and subprojects
by Biddiscombe, John A. 20 May '16

20 May '16

In our task of the HBP (Human Brain Project), we have a lot of libraries with interdependencies and have standardised on a reasonably simple system that works well enough – it can/could be improved significantly, but in case it’s of interest to boost, here’s a brief description (which I’m writing from memory and all the actual names of commands etc are wrong, but I only aim to describe the process) A top level cmakelists file would contain something like project(my_big_project) add_subproject(subprojectX ${CMAKE_CURRENT_SOURCE_DIR}/x) add_subproject(subprojectY ${CMAKE_CURRENT_SOURCE_DIR}/y) etc subprojects X,Y,….. Are defined by either including the source for those projects in the relevant subdirs, or by providing an additional command along the lines of git_external_project(name URL branchname/SHA/etc) Or by supplying a .gitprojects file in the root of the master subproject (subproject can if they wish do this recursively) which may contain a list of desirable projects + urls that we know will be needed if enabled When the user runs cmake on the top-level source project (my_big_project) it provides OPTIONS of the form SUBPROJECT X ON/OFF SUBPROJECT Y ON/OFF Which the user can enable via the GUI or by cmake –DSUBPROJECT_X=ON …. The macros defined will decide that if project X is not present to do a git clone (--shallow, --branch, --anything you want to add in the config) of project X,Y,… from the git URL supplied and checkout the repo into the correct location, add_subproject then enters the subproject and cmake progresses as usual. Inside the subproject, another macro can defined DEPENDENCIES of the project via more instantiations of the same kind which will also be cloned as git subprojects if they are not already present (currently if X depends on A branch1 and Y depends on A branch2 we throw an error, but it would be possible to support this tight control of include_directories). Seeing the ongoing discussion of cmake in boost (I am one of the many it seems who cmakeified the parts of boost I needed years ago and then gave up around the time rypll came into being – hoping that the job would be done properly). So the top level boost cmakelists would simple contain a list of all the libraries and their git locations and release branches, each sub project (library) can say dependencies(atomic, filesystem, threads, context) and let the cmake scripts do the rest. A user checking out the “top” level boost would get only a single cmakelists file with a bunch of helper scripts containing the macros needed for install, versions, git cloning etc etc and would then run cmake –DSUBPROJECT_ATOMIC=ON –DSUBPROJECT_THREADS=ON –DSUBPROJECT_CONTEXT=ON ~/path/to/top/level/boost-cmakelists (you could change the SUBPROJECT to BOOSTMODULE or something like that if you preferred) If one of the libs the user ‘wants’ uses another library, it gets enabled by the dependencies declared in the lib and everything just builds and works. A make install will install all the libs that got built including those dependencies that were pulled in (some public/private options could no doubt be added to make that better if necessary). To give you an idea of what I’m referring to, https://github.com/Eyescale/CMake/blob/master/GitExternal.cmake<https://github.com/Eyescale/CMake/blob/master/SubProject.cmake> https://github.com/Eyescale/CMake/blob/master/SubProject.cmake Are a couple of scripts that do some of the work. The process has helped us to simplify somewhat our build and dependency process and it might be a useful mechanism for boost to use cmake. It isn’t perfect, isn’t pretty in some places and has been heavily tweaked beyond its original purpose so the scripts would not be considered usable in their current state – but with some cleaning up … One very nice feature is the one can create a simple script project(mystuff) #set some options we might beed set(boost_optionX,y,x…) add_subproject(boost) # and some more set(hpx_optionX,y,z…) add_subproject(hpx) set(my_optionX,y,z…) add_subproject(stuff_that_needs_them) And the user does not need to worry about cloning the projects as the gitproject refs will do it for them and take what’s needed on a per repo basis. (I use this for HPX extensively - the individual libs/projects must be careful with relative path names and using per project prefixes for options, tests etc etc) I would be happy to volunteer as a helper should you wish for help cmakeifying boost regardless of the method by which you proceed. JB -- John Biddiscombe, email:biddisco @.at.@ cscs.ch http://www.cscs.ch/ CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82

1 0

Files in individual libraries
by Edward Diener 20 May '16

20 May '16

As long as library authors follow the normal Boost guidelines for placing the necessary files for using, building ( for non-header only libraries ), testing, and documenting their library I really don't see why an author cannot add to their library whatever other files they want in whatever place in their library structure they want to put it. Can it really be such a big issue that this should not be allowed ? And, if so, why ? If the real issue being objected to is that the placement of additional files gives the end-user an impression that Boost libraries generally support additional things which an individual library supports with the additional files, wouldn't it just be better to encourage and/or require that an individual library developer document the additional files as personal extensions to what Boost requires.

2 2

Re: [boost] [Boost-users] Boost 1.61.0 has been released
by Daniel James 19 May '16

19 May '16

On 18 May 2016 at 08:05, Vladimir Prus <vladimir.prus(a)gmail.com> wrote: > > Tom has pointed a typo in file names in the file. Correct one is now > attached, and instructions > for validating are the same: I added the to the website, it's currently linked from the release notes, and if it's okay, I'll add a link to the download page at some point. Although it can't be underestimated just how little I care or understand about any of this stuff, so I'm sure I've done it all wrong. If line endings make a difference then it might not work since git converted the file to unix style automatically, so let me know. I also don't really want to add all the instructions to the release notes, so if someone wants to write generic instructions for another page, I could put that up and link to it.

1 0

DMARC and mailman
by James Sharpe 19 May '16

19 May '16

In June 2016 gmail is going to be changing its DMARC policy to reject any unaligned mail. This means that we will be seeing any mailing list responses from a gmail.com address to be considered spam by any mail server that enforces DMARC. For a while now yahoo.com has had this policy turned on which has meant that yahoo.com addresses have been considered spam. Mailman has released a workaround in version 2.1.18: https://www.mail-archive.com/mailman-users@python.org/msg64098.html The boost mailing list is currently on mailman 2.1.15. I'd strongly suggest that this should be updated as a matter of urgency else we'll find a lot of the conversations on this list will end up in the spam folder... Regards, James

1 0

Link problem
by Adolfo 19 May '16

19 May '16

Hi everyone, I am quite newbie on this and perhaps this is quite simple, sorry for the trouble. I am using VSC++ 2012, I have the boost version boost_1_60_0 and I have built it following the description in http://www.boost.org/doc/libs/1_60_0/more/getting_started/windows.html. No problem with batch files (bootstrap and b2). When I try to test the example code from section 6, I have the following linking error: Error 1 error LNK1104: no se puede abrir el archivo 'libboost_regex-vc110-mt-gd-1_60.lib' I have realised that in my ...\boost_1_60_0\stage\lib directory, all the .lib files have names like libboost_*-vc140-*-1_60.lib. Can anybody be so kind of telling me what I did wrong or where I have to change this?? Best wishes, Adolfo.

3 2

Re: [boost] [Boost-users] Boost 1.61.0 has been released
by Tom Kent 18 May '16

18 May '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > On Wed, May 18, 2016 at 2:05 AM, Vladimir Prus <vladimir.prus(a)gmail.com> wrote: > > On 17/05/2016 13:16, Vladimir Prus wrote: > > > On 13/05/2016 15:07, Rene Rivera wrote: > > > Release 1.61.0 of the Boost C++ Libraries is now available. > > > > > > For details, including download links, see http://www.boost.org/users/news/version_1.61.0 > > > > > > You can also download directly from SourceForge: http://sourceforge.net/projects/boost/files/boost/1.61.0/ > > > > You can optionally verify integrity of the source downloads using the attached signed checksums file. > > Tom has pointed a typo in file names in the file. Correct one is now attached, and instructions > for validating are the same: I now get good hashes and a good signature verification. I'm signing this email with my private key "Thomas Kent <teeks99(a)yahoo.com>" for the record. Tom Original Attachment: - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 a547bd06c2fd9a71ba1d169d9cf0339da7ebf4753849a8f7d6fdb8feee99b640 boost_1_61_0.tar.bz2 a77c7cc660ec02704c6884fbb20c552d52d60a18f26573c9cee0788bf00ed7e6 boost_1_61_0.tar.gz fa1c34862b7ba8674ed6e064a14667a11830c6252f702d9458451834b74f7815 boost_1_61_0.7z 02d420e6908016d4ac74dfc712eec7d9616a7fc0da78b0a1b5b937536b2e01e8 boost_1_61_0.zip - -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXPBG3AAoJEA8aPs1OrCMWL1QQAJCsQbr4rxpQMDssW5O0Fupg aw8Us0CnfPLSPW5gMdQoIQxu/n1SNobn4Vg1/hyTfweufqFwHFRxJnHiWtlbI/GB q1TueLPCxcJUi6lT7ZOVcpKb6AS6vOnSJRODQ0zk62phKBmLDUxiBI46FlCkzHbz uWVG+wttzk2Skeb3400xWEMtM0fgX3oJenh5Ye//oD7biJC0aIVPrnkauQ2Nze0l 2nG8e7w7ZzlXEx0Ei8KHiyBsFMj0/O5JIJKbxWorBAeELSgWun0YqB9EnrbADGDp XCEUUg1FB2llTmpG3a/dyv8fMlAS/ENka7e4aGuIHAlyfmTKGx+9Zd813XLiSjvw CHCyp+b7v0dGn2RFrVhgl9qRyFKgcvYjhhsA42iO0eFt7rgkoXV72qQzjSClzjkS jJrcj8dxJkZVMJ9tWKCmzGoPYRj4z8Nt8dw7HDqFGb7/2Rw6FZ18N9SsqHD+y9G3 TZhPPYQJVqckM9qo0CFzYwZpjiBgLhhQI6iEUh8UB8xXB09cJfgHGvyszXsvR+3l xQvKq19BYWHlPoi4Ie+YUzxF81Pgj98mbnwXLcgUoLBZWueXGfFdf+nBvyDoQyli LbHEpt0cGwWyfk+HXt+Qa5dmSRMr7zZpmWseBr9/6J1gCoNxAEOqHZ1hCrpFIHWt pM+LHXktogy3CpBV2IXH =6T/2 - -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJXPIMxAAoJEO5CwwL7YZSoqjQQAME+iTB9MhE3Jz2AAl7+tohB +v8U25f1C2X6qbVTKCynG+FzdfthIOwdLeReIcY8fUD7O30LqhYpfjPgDJvRqvDT pjU/jxD4ORLn9aEtNGcEX+EtSuO9dV2eZP3cDcyNnTRUu26O6LkJN2wRb2BFa1kN coVuhNSD7I8BBpiNgWo/J09Ajv3GRags8y6WHjC6IUD5isGUGMGD7udhjD6qcX/q hiyTfdzkqMo5lDmGj20JCsuXg1Iqku5JKydeDH4vunpZokbDmtSja992kzMSRFGK CemHapPcml5ei8ubvEnROYLPcIpcrL9zpO6vTpKRQs5dzfJDkeiCeS9Zgvm/fb7h G4yoUD08ccU0HHwRVCNdpHXPRgSSh3JJp94XuWO/sFgNg0q+5pGeGoqnveBaroqu zAgdcteBmw+YoU39bWt+kPu5zVbVygHZNXpC0BOKc8+IP86wwOvEHDEUm1o5UQma QPWQrZuoMcGNE9SZn1K1Zg+oJ6KG5Ykp5SOhhb3SrV7Oqb3SN3lg9lbEyGBHa/lY SUSLdMlkcEtUITRu6KcYJAVw9Pbq2O8AZWYPZSjToZxpEFv4+53VOSr3mkpFQxMc dzral/n0Yyw+XsqIke1kdzWpbCGrPAy0Pm5BGB7Fsi9iq1JbVjVi47ZIk4L16L0H gmgII1jsJy8+R3XXpGRZ =x/tu -----END PGP SIGNATURE-----

1 0

Re: [boost] [Boost-users] Boost 1.61.0 has been released
by Daniel James 18 May '16

18 May '16

On 17 May 2016 at 21:42, Raffi Enficiaud <raffi.enficiaud(a)mines-paris.org> wrote: > > Thanks! > The boost.test documentation has the banner "click here to view the latest > version on this page" on the top: > http://www.boost.org/doc/libs/1_61_0/libs/test/doc/html/index.html > > Sorry for the late mention, I thought it was because 1.61 was not released > yet. > Anything I did wrong? Anything I can do? Sorry about that, it was a bug. It should be fixed now, you might have to shift-refresh to see the fixed page.

1 0

Review Wizard Report for May 2016
by Ronald Garcia 18 May '16

18 May '16

============================================== Review Wizard Status Report for May 2016 ============================================== News ==== 1. Boost 1.58 Released April 2015. New Libraries: Endian, Sort 2. Metaparse Library Accepted 3. Hana Library Accepted 4. DLL Library Accepted 5. Http Library Rejected 6. Boost 1.59 Released August 2015. New Libraries: Coroutine2, Convert 7. AFIO Library Reviewed 8. Fiber Library Conditionally Accepted 9. Boost 1.60 Released December 2015. New Libraries: Variadic Macro Data 10. Quaternions, Vectors, Matrices Accepted 11. Fit Library Rejected 11. Boost 1.61 Released May 2016. New Libraries: Compute, DLL, Metaparse, Hana Open Issues =========== The following libraries have review managers, but have not yet been scheduled for review: * Range Extensions - added May 2012; review manager: Neil Groves. The following libraries have been reviewed and await reports from their review managers: * AFIO - reviewed August 2015; review manager: Ahmed Charles. The following libraries have been accepted to Boost, but have not yet been integrated into Boost Git: * Contract - accepted September 2012; author: Lorenzo Caminiti. * Quaternions,Vectors,Matrices - accepted December 2015; author: Emil Dotchevski The following libraries have been accepted and submitted to Boost Git, but have not yet appeared in a release: * none The following libraries have been accepted provisionally to Boost, but have not been submitted for mini-review and full acceptance: * none General Announcements ===================== As always, we need experienced review managers. Please take a look at the list of libraries in need of managers and check out their descriptions. In general review managers are active boost participants, including library contributors, infrastructure contributors, and other mailing list participants with a substantial track record of constructive participation. If you can serve as review manager for any of them, email Ron Garcia or John Phillips, "rxg at cs dot ubc dot ca" and "johnphillipsithica at gmail dot com" respectively. We are also suffering from a lack of reviewers. While we all understand time pressures and the need to complete paying work, the strength of Boost is based on the detailed and informed reviews submitted by you. If you are interested in reviewing a library but won't have time during the review period, you can always prepare your review ahead of time. No rule says you can only work on a review during the review period. A link to this report will be posted to www.boost.org. If you would like us to make any modifications or additions to this report, please email Ron or John. The review schedule is an unordered list of the libraries awaiting review. As such, any library on the schedule can be reviewed once the developer is ready, a review manager has been secured, and the manager, developer, and wizards agree on a date to schedule the review. Review Schedule =============== * Join (M) * Block Pointer (M) * Singularity (M) * Extended Complex Numbers (M) * Boost.Range Extensions * Nowide (M) * Array (M) * STL Extensions (M) * Countertree (M) * Process (M) * Application (M) * Edit Distance (M) * Mixin (M) * Dependency Injection (M) * Segmented Tree * Fiber ``(M)`` marks libraries that need review managers. -------------------- Join ---- :Author: Yigong Liu :Review Manager: Needed :Download: http://channel.sourceforge.net/ :Description: Join is an asynchronous, message based C++ concurrency library based on join calculus. It is applicable both to multi-threaded applications and to the orchestration of asynchronous, event-based applications. It follows Comega's design and implementation and builds with Boost facilities. It provides a high level concurrency API with asynchronous methods, synchronous methods, and chords which are "join-patterns" defining the synchronization, asynchrony, and concurrency. Block Pointer ------------- :Author: Phil Bouchard :Review Manager: Needed :Download: https://svn.boost.org/svn/boost/sandbox/block_ptr/ :Description: Deterministic memory manager of constant complexity capable of handling cyclic collections. Singularity ----------- :Author: Ben Robinson :Review Manager: Needed :Download: https://github.com/cppmaven/Singularity :Description: The Singularity Design Pattern allows you to restrict any class to a single instance. Unlike the infamous Singleton, Singularity gives you direct control over the lifetime of the object, does not require you to grant global access to the object, nor does it limit you to the default constructor for that object. Extended Complex Numbers ------------------------ :Author: Matthieu Schaller :Review Manager: Needed :Download: http://code.google.com/p/cpp-imaginary-numbers/ :Description: The library is an extension of the std::complex class addressing two issues: 1. The standard does not guaranty the behaviour of the complex class if instantiated with types other than float/double/long double. 2. Some calculation where pure imaginary numbers (i.e. multiples of sqrt(-1)) appear are unnecessarily slowed down due to the lack of support for these numbers. The code I submit contains two interleaved classes boost::complex and boost::imaginary which can be instantiated with any type T provided T overloads the usual arithmetic operators and some basic (real) mathematical functions depending on which complex function will be used. It is thus an extended version of Thorsten Ottosen's n1869 proposal (http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2005/n1869.html) Range Extensions ---------------- :Author: Akira Takahashi :Review Manager: Neil Groves :Download: https://github.com/faithandbrave/OvenToBoost :Description: This project adds some features of the Oven Range Library to Boost.Range. Features: - Additional Range Adaptors (taken, taken_while, dropped, dropped_while, elements, elements_key, memoized, outdirected) - Extensions for using Lambda (regular function, regular operator) - Infinite Range (iteration function) - and additional range utilities. Nowide ------ :Author: Artyom Beilis :Review Manager: Needed :Download: http://cppcms.com/files/nowide/ :Description: This library makes cross platform Unicode aware programming easier. It provides an implementation of standard C and C++ library functions, such that their inputs are UTF-8 aware on Windows without requiring to use Wide API. Array ----- :Author: Brian Smith :Review Manager: Needed :Download: https://github.com/BrianJSmith/Array :Description: The array class is a C++11 compatible implementation of static multidimensional arrays. STL Extensions -------------- :Author: Vadim Stadnik :Review Manager: Needed :Download: https://github.com/vstadnik/stl_ext_adv_review :Description: The proposed library [stl_ext_adv] offers augmented array based B+ trees and STL containers that support the interfaces of the C++03 sequences and associative containers. The library offers a number of extensions and performance improvements that are not available in C++03 and C++11 standard containers. Countertree ----------- :Author: Francisco Jose Tapia :Review Manager: Needed :Download: https://dl.dropbox.com/u/8437476/works/countertree_code_doc.zip :Description: This library is an implementation of a binary red-black counter tree. This tree have an additional counter in each leaf. This permit the access to the elements by the position, like in a vector. It is a random access container with random access iterators. COUNTERTREE This kind of trees have an additional counter in each leaf. This permit the access to the elements by the position, like in a vector. It is a random access container with random access iterators. With unordered information we have a vector with the same speed inserting and deleting in any position (O(log N)). With ordered information, we have the classes set, multiset, map and multimap, with identical interface than the STL classes, with the plus of access to the elements by position, like in a vector. The iterators are random access , and you can subtract them. SUBALLOCATOR The suballocator is a layer between the allocator and the data structures, compatible with any allocator with the STL definition. The suballocator replace to the allocator in the allocation of equal size elements. It provides speed, return the unused memory and decrease the memory used by the program and improve the cache performance due to the data locality improvement ( 30% of improvement of speed respect the std::allocator with GCC 4.7) Process ------- :Author: Boris Schaeling :Review Manager: Needed :Download: http://www.highscore.de/boost/process0.5/process.zip :Description: Boost.Process is a library to manage system processes. It can be used to: * create child processes * setup streams for child processes * communicate with child processes through streams (synchronously or asynchronously) * wait for processes to exit (synchronously or asynchronously) * terminate processes Application ----------- :Author: Renato Tegon Forti :Review Manager: Needed :Download: https://github.com/retf/Boost.Application :Documentation: http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/index.html :Description: Application provides an application environment, or start point to any people that want a basic infrastructure to build an system application on Windows or Unix Variants (e.g. Linux, MacOS). Application uses behaviours modeled using 'aspects' concept proposed by 'Vicente J. Botet Escriba', that allow easy extension and customization of library components. The application modes uses these components internally to achieve the user desirable behaviours. Application provide many useful ready-to-use features, e.g: * Run application as Windows Service; * Run application as UNIX/POSIX Daemon; * Plugin extension system; * Process(executable) Single instance Instantiation support; * Application SIGNAL/Callbacks customization; * Windows Service Setup feature; * And many others. Edit Distance ------------- :Author: Erik Erlandson :Review Manager: Needed :Download: https://github.com/erikerlandson/algorithm/tree/edit_distance/sequence :Description: The edit distance is the length of the shortest (or least-cost) edit script from one sequence to another, where an edit script is defined as a sequence of insertion, deletion and (optionally) substitution operations. The function implementing the edit distance is named edit_distance. This function will return the edit distance between two sequences, where sequences may be any valid range object supporting forward iteration. The edit_distance function will also, if requested, return the edit script. Mixin ----- :Author: Borislav Stanimirov :Download: https://github.com/iboB/boost.mixin :Documentation: http://ibob.github.io/boost.mixin/ :Review Manager: Needed :Description: Boost.Mixin is a library that allows the composition and modifications of polymorphic types at run time. Types and objects are constructed out of building blocks called mixins. The library uses the type boost::mixin::object as a placeholder, whose instances can be extended with existing classes (mixins), thus providing a particular instance with the functionality of all those types. Accessing the newly formed type's interface is made through messages: stand-alone functions generated by the library, which can be thought of as methods. This is given while also having full abstraction between the interface and the definition of types. An existing feature in another language similar to Boost.Mixin and also an inspiration for the library are the mixins in Ruby. The library also has similarities with the pattern entity-component-system. Dependency Injection -------------------- :Author: :Download: https://github.com/krzysztof-jusiak/di :Documentation: http://krzysztof-jusiak.github.io/di/boost/libs/di/doc/html :Incubator: http://rrsd.com/blincubator.com/bi_library/di-dependency-injection/?gform_p… :Review Manager: Needed :Description: Boost.DI is a dependency injection library improving manual dependency injection by simplifying object instantiation with automatic dependencies injection. Using Boost.DI has many advantages over manual dependency injection. * Reduce boilerplate code (No factories, no objects creation in specific order) * Reduce cost of maintenance effort (Constructor signature change won't affect di configuration) * Reduce testing effort * Give better control of what and how is created (Policies, Providers) * Give better understanding about objects hierarchy (UML Dumper) Segmented Tree -------------- :Author: Chris Clearwater :Download: http://rrsd.com/blincubator.com/bi_library/segmentedtreeseq-2/?gform_post_i… :Repository: http://github.com/det/segmented_tree :Documentation: https://det.github.io/segmented_tree :Review Manager: Glen Fernandes :Description: SegmentedTreeSeq is a sequence data structure like vector and deque that supports efficient random access insert and erase. It is implemented using B+Trees and has an emphasis on speed and a low memory overhead. Fiber ----- :Author: Oliver Kowalke :Download: https://github.com/olk/boost-fiber :Documentation: http://olk.github.io/libs/fiber/doc/html/ :Review Manager: Nat Goodspeed :Description: Boost.Fit is a header-only C++11/C++14 library that provides utilities for functions and function objects. Libraries under development =========================== See The Boost Library Incubator Project at http://blincubator.com for discussion of libraries currently under development.

2 1

Re: [boost] [proto][variant] variant crashes proto expression
by Igor R. 17 May '16

17 May '16

> // The values bound to the placeholders > Value *d[2]; <...> > // The result of evaluating arithmetic expressions > typedef Value& result_type; So, you store pointers to the variants and return references, thus preventing copying. But why does the copying cause the aforementioned crash? Does it look like a bug in Proto? That's quite weird, because I never encountered any issue with variant copying... -- View this message in context: http://boost.2283326.n4.nabble.com/proto-variant-variant-crashes-proto-expr… Sent from the Boost - Dev mailing list archive at Nabble.com.

1 0

Boost Build and Test
by Robert Ramey 17 May '16

17 May '16

I started a new thread to accommodate the widening discussion on CMake. Build and Test systems: I've always been a big complainer about Boost Build. Now I'm a big complainer about CMake as well. Just so you know. I always found it weird that the buiding of libraries jam file was stashed in it's own directory - build while jam files for other components like test and building docs was found inside their respective directories. I also added to the serialization library some other jam files in subdirectories example and in performance. So to me by far the most natural place to find the library jam file would be in the directory we've agreed to name src. I never made any issue of this as my whole progress through life is about moving on to get my own projects done. Largely motivated by the desire to do cutting edge C++ development I replaced my old windows system with a mac mini. Soon I wanted to build and test my projects in XCode IDE. I like to use an IDE, but setting it and maintaining it for a project like the serialization library is an incredible amount of work. So I resolved to setup CMake to do the job. I had exposure to CMake before and found it no better than all the other build systems. But it needed to do what I wanted it to do - create the IDE project and it was very popular. So I managed to make it work in this context and the result has been quite satisfactory. But making it run all the tests I want to run - different compilers, libraries, etc. etc. integrating with my own library_status dashboard builder looked like a serious pain and I already had an elaborate Jamfile set for doing all of that. So upshot is I use them both for different purposes. I don't see anything wrong with that. In order not to upset the established structure I put my CMakeLists.txt file inside it's own directory. If it was totally up to me, what I'd like to see is: a) jam files in the build directory moved to src b) thereby acknowledging the practice of having jam files in the same directories which contain the build sources. c) which is pretty much the same as the CMake approach. c) official tolerance for including other build systems at the same level such as CMakeLists.txt and maybe MS projects and solutions. d) official tolerence for including a top level CMakeLists.txt. Personally I don't think this is necessary or even a good idea - but I want to leave that as a separate discussion. Robert Ramey

1 0

Final benchmark graphs for Colony vs std:: containers now available
by Soul Studios 17 May '16

17 May '16

Re-wrote my benchmark code from scratch a month or two ago with some help from Baptiste Wiche, have run over std::list, std::map, std::multiset, std::deque, std::vector, and for GCC, Chris's segmented_tree implementation. To be honest there's not much point comparing against segmented_tree, as the goals are totally different (efficient random access insertion for segtree, vs efficient unordered erasure/insertion/iteration without pointer invalidation colony), but there was some interest last time I wrote here. In addition I compared against other methods for ensuring pointer/index validity using deques and vectors, to see how those things pan out. Graphs are available here: http://www.plflib.org/colony.htm#benchmarks and here: http://www.plflib.org/stack.htm There are also MSVC 2013 results linked to in the first paragraph of the benchmarks. Comments are welcome, but please read the page first. Stack performs particularly well, outperforming all alternatives in both GCC/MSVC.

3 16

Boost ICL tests attempting to pass non-bidirectional iterator to std::reverse_copy
by Billy O'Neal (VC LIBS) 16 May '16

16 May '16

Hi folks. I'm not a Boost.ICL expert, but we detected this one failure with our in-development STL and this test case: template <ICL_IntervalSet_TEMPLATE(_T) IntervalSet, class T> void interval_set_element_iter_4_discrete_types() { typedef IntervalSet<T> IntervalSetT; typedef typename IntervalSetT::interval_type IntervalT; typedef std::vector<T> VectorT; IntervalSetT set_a; set_a.add(I_I(1,3)).add(I_I(6,7)); VectorT vec(5), cev(5); vec[0]=MK_v(1);vec[1]=MK_v(2);vec[2]=MK_v(3);vec[3]=MK_v(6);vec[4]=MK_v(7); cev[0]=MK_v(7);cev[1]=MK_v(6);cev[2]=MK_v(3);cev[3]=MK_v(2);cev[4]=MK_v(1); VectorT dest; std::copy(elements_begin(set_a), elements_end(set_a), std::back_inserter(dest)); BOOST_CHECK_EQUAL( vec == dest, true ); dest.clear(); std::copy(elements_rbegin(set_a), elements_rend(set_a), std::back_inserter(dest)); BOOST_CHECK_EQUAL( cev == dest, true ); dest.clear(); std::reverse_copy(elements_begin(set_a), elements_end(set_a), std::back_inserter(dest)); BOOST_CHECK_EQUAL( cev == dest, true ); dest.clear(); std::reverse_copy(elements_rbegin(set_a), elements_rend(set_a), std::back_inserter(dest)); BOOST_CHECK_EQUAL( vec == dest, true ); } which produces this failure: C:\Dev\WCFB01_01\binaries\x86ret\inc\algorithm(1672): error C2665: 'std::_Reverse_copy1': none of the 2 overloads could convert all the argument types C:\Dev\WCFB01_01\binaries\x86ret\inc\algorithm(1655): note: could be '_OutIt std::_Reverse_copy1<_Iter,_OutIt>(_BidIt,_BidIt,_OutIt,std::random_access_iterator_tag,std::random_access_iterator_tag)' with [ _OutIt=std::back_insert_iterator<VectorT>, _Iter=boost::icl::element_iterator<std::_Tree_const_iterator<std::_Tree_val<std::_Tree_simple_types<boost::icl::discrete_interval<bicremental_type_5,std::less>>>>>, _BidIt=boost::icl::element_iterator<std::_Tree_const_iterator<std::_Tree_val<std::_Tree_simple_types<boost::icl::discrete_interval<bicremental_type_5,std::less>>>>> ] C:\Dev\WCFB01_01\binaries\x86ret\inc\algorithm(1645): note: or '_OutIt std::_Reverse_copy1<_Iter,_OutIt>(_BidIt,_BidIt,_OutIt,std::bidirectional_iterator_tag,std::_Any_tag)' with [ _OutIt=std::back_insert_iterator<VectorT>, _Iter=boost::icl::element_iterator<std::_Tree_const_iterator<std::_Tree_val<std::_Tree_simple_types<boost::icl::discrete_interval<bicremental_type_5,std::less>>>>>, _BidIt=boost::icl::element_iterator<std::_Tree_const_iterator<std::_Tree_val<std::_Tree_simple_types<boost::icl::discrete_interval<bicremental_type_5,std::less>>>>> ] C:\Dev\WCFB01_01\binaries\x86ret\inc\algorithm(1672): note: while trying to match the argument list '(boost::icl::element_iterator<std::_Tree_const_iterator<std::_Tree_val<std::_Tree_simple_types<boost::icl::discrete_interval<DomainT,Compare>>>>>, boost::icl::element_iterator<std::_Tree_const_iterator<std::_Tree_val<std::_Tree_simple_types<boost::icl::discrete_interval<DomainT,Compare>>>>>, std::back_insert_iterator<VectorT>, boost::iterators::detail::iterator_category_with_traversal<std::input_iterator_tag,Traversal>, std::output_iterator_tag)' with [ DomainT=bicremental_type_5, Compare=std::less ] and [ DomainT=bicremental_type_5, Compare=std::less ] and [ Traversal=boost::iterators::bidirectional_traversal_tag ] c:\dev\wcfb01_01\src\qa\vc\fe\3rdpartycomp\boost_1_60_0\libs\icl\test\fastest_interval_set_\../test_interval_set_shared.hpp(810): note: see reference to function template instantiation '_OutIt std::reverse_copy<boost::icl::element_iterator<std::_Tree_const_iterator<std::_Tree_val<std::_Tree_simple_types<boost::icl::discrete_interval<DomainT,Compare>>>>>,std::back_insert_iterator<VectorT>>(_BidIt,_BidIt,_OutIt)' being compiled with [ _OutIt=std::back_insert_iterator<VectorT>, DomainT=bicremental_type_5, Compare=std::less, _BidIt=boost::icl::element_iterator<std::_Tree_const_iterator<std::_Tree_val<std::_Tree_simple_types<boost::icl::discrete_interval<bicremental_type_5,std::less>>>>> ] c:\dev\wcfb01_01\src\qa\vc\fe\3rdpartycomp\boost_1_60_0\libs\icl\test\fastest_interval_set_\../fastest_interval_set_cases.hpp(61): note: see reference to function template instantiation 'void interval_set_element_iter_4_discrete_types<boost::icl::interval_set,discrete_type_2>(void)' being compiled We are considering reverting this enforcement of iterator category tag in our STL, but technically a standard library appears within its rights to reject this. Billy Robert O'Neal III SDE II - Visual C++ Libraries bion(a)microsoft.com

1 0

media file errors
by Rainer Deyke 15 May '16

15 May '16

"CDs/Reverend Bizarre - III - So Long Suckers (disc 1)" is redundant and should be deleted. In "CDs/Shadow Gallery - Room V": "Shadow Gallery - Seven Seas.mp3" -> "Shadow Gallery - Seven Years.mp3" -- Rainer Deyke (rainerd(a)eldwood.com)

1 0

Call for Submissions: International Conference on Information Society (i-Society 2016), Technical Co-Sponsored by IEEE UK/RI Chapter!
by Faye Bewsy 13 May '16

13 May '16

1 0

[proto][variant] variant crashes proto expression
by Igor R 13 May '16

13 May '16

The following code is a slightly modified Proto calc2 example. Instead of doubles I use variant<int, double>, and the expression is just _1 = _2. This code triggers assertion in variant/detail/forced_return.hpp, so it looks like some variant instance gets messed up. It happens when the value returned from proto::eval(*this, ctx) is being copied. It can be reproduced both with MSVC and gcc, with Boost 1.60. Is there any workaround for this issue? Thanks. ////////////// #include <iostream> #include <boost/proto/proto_typeof.hpp> #include <boost/proto/core.hpp> #include <boost/proto/context.hpp> #include <boost/variant.hpp> namespace proto = boost::proto; using proto::_; typedef boost::variant<int, double> var_t; template<typename Expr> struct calculator_expression; // Tell proto how to generate expressions in the calculator_domain struct calculator_domain : proto::domain<proto::generator<calculator_expression> > {}; // Will be used to define the placeholders _1 and _2 template<int I> struct placeholder {}; // Define a calculator context, for evaluating arithmetic expressions // (This is as before, in calc1.cpp) struct calculator_context : proto::callable_context< calculator_context const > { // The values bound to the placeholders var_t d[2]; // The result of evaluating arithmetic expressions typedef var_t result_type; explicit calculator_context(const var_t &d1 = var_t(), const var_t &d2 = var_t()) { d[0] = d1; d[1] = d2; } // Handle the evaluation of the placeholder terminals template<int I> result_type operator ()(proto::tag::terminal, placeholder<I>) const { return d[ I - 1 ]; } }; // Wrap all calculator expressions in this type, which defines // operator () to evaluate the expression. template<typename Expr> struct calculator_expression : proto::extends<Expr, calculator_expression<Expr>, calculator_domain> { explicit calculator_expression(Expr const &expr = Expr()) : calculator_expression::proto_extends(expr) {} BOOST_PROTO_EXTENDS_USING_ASSIGN(calculator_expression<Expr>) // Override operator () to evaluate the expression var_t operator ()() const { calculator_context const ctx; return proto::eval(*this, ctx); } var_t operator ()(const var_t &d1) const { calculator_context const ctx(d1); return proto::eval(*this, ctx); } var_t operator ()(const var_t &d1, const var_t &d2) const { calculator_context const ctx(d1, d2); return proto::eval(*this, ctx); } }; // Define some placeholders (notice they're wrapped in calculator_expression<>) calculator_expression<proto::terminal< placeholder< 1 > >::type> const _1; calculator_expression<proto::terminal< placeholder< 2 > >::type> const _2; // Now, our arithmetic expressions are immediately executable function objects: int main() { BOOST_PROTO_AUTO(expr, _1 = _2); var_t a1(1), a2(2.5); expr(a1, a2); return 0; }

3 2

[intrusive] crash with slist push_back
by Arpan Sen 12 May '16

12 May '16

Hi Boost Dev, Please consider the following code, this crashes with slist but works just fine if I replace slist with list. Also flat_map crashes but std::map works fine. Am I doing something gross or is there a bug here? #include <iostream> #include <boost/container/flat_map.hpp> #include <map> //#include <boost/intrusive/list.hpp> #include <boost/intrusive/slist.hpp> using namespace boost::intrusive; struct m : public slist_base_hook<> { int n; public: m(int k) : n(k) { } }; int main() { boost::container::flat_map<int, slist<m, cache_last<true> > > c1; std::map<int, slist<m, cache_last<true> > > c2; m* m1 = new m(22); c1[1].push_back(*m1); m* tt = new m(99); c2[1].push_back(*tt); } Regards Arpan

2 1

Using thread_local with Boost.Thread
by Ruediger Berlich 11 May '16

11 May '16

Hi there, I am curious whether it would be possible to use C++11 thread_local instead of Boost's own TLS, while continuing to use Boost.Thread ? I assume that there will be problems if Boost falls back to native pthread ? Kind Regards, Beet

1 0

Boost 1.61.0 Release Candidate 2
by Vladimir Prus 11 May '16

11 May '16

The second release candidates for the 1.61.0 release are now available at: http://boost.cowic.de/rc/boost_1_61_0_rc2.zip http://boost.cowic.de/rc/boost_1_61_0_rc2.7z http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.bz2 http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.gz The SHA256 checksums are as follows: fa1c34862b7ba8674ed6e064a14667a11830c6252f702d9458451834b74f7815 boost_1_61_0_rc2.7z a547bd06c2fd9a71ba1d169d9cf0339da7ebf4753849a8f7d6fdb8feee99b640 boost_1_61_0_rc2.tar.bz2 a77c7cc660ec02704c6884fbb20c552d52d60a18f26573c9cee0788bf00ed7e6 boost_1_61_0_rc2.tar.gz 02d420e6908016d4ac74dfc712eec7d9616a7fc0da78b0a1b5b937536b2e01e8 boost_1_61_0_rc2.zip The changes relative to RC1 are MSVC fixes for signals2 and graph libraries. 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 signed list of checksums is also attached, signed with the following key: https://pgp.mit.edu/pks/lookup?op=get&search=0xDA472E8659753BA4 Key fingerprint C5F0 F367 AA66 616F B839 806E DA47 2E86 5975 3BA4 Thanks! -- The release managers

9 14

[lockfree] _ENABLE_ATOMIC_ALIGNMENT_FIX for VS 2015 Update 2
by Stephan T. Lavavej 11 May '16

11 May '16

Hi, While running Boost.Lockfree's tests, one of our compiler devs encountered the following failure: freelist_test.cpp c:\wcfb01\binaries\x86chk\inc\atomic(659): error C2338: You've instantiated std::atomic<T> with sizeof(T) equal to 2/4/8 and alignof(T) < sizeof(T). Before VS 2015 Update 2, this would have misbehaved at runtime. VS 2015 Update 2 was fixed to handle this correctly, but the fix inherently changes layout and breaks binary compatibility. Please define _ENABLE_ATOMIC_ALIGNMENT_FIX to acknowledge that you understand this, and that everything you're linking has been compiled with VS 2015 Update 2 (or later). c:\wcfb01\binaries\x86chk\inc\atomic(669): note: see reference to class template instantiation 'std::_Atomic_base<_Ty,4>' being compiled with [ _Ty=boost::lockfree::detail::tagged_index ] e:\boost\boost\boost\lockfree\detail\freelist.hpp(608): note: see reference to class template instantiation 'std::atomic<boost::lockfree::detail::tagged_index>' being compiled e:\boost\boost\boost\lockfree\detail\freelist.hpp(609): note: see reference to class template instantiation 'boost::lockfree::detail::fixed_size_freelist<T,NodeStorage>' being compiled call "C:\WCFB01\binaries\x86chk\bin\i386\vcvarsall.bat" x86 >nul cl /Zm800 -nologo @"..\bin.v2\libs\lockfree\test\freelist_test.test\msvc-latest\debug\threading-multi\freelist_test.obj.rsp" ...failed compile-c-c++ ..\bin.v2\libs\lockfree\test\freelist_test.test\msvc-latest\debug\threading-multi\freelist_test.obj... with the following type: class tagged_index { public: typedef boost::uint16_t tag_t; typedef boost::uint16_t index_t; protected: index_t index; tag_t tag; }; This is by design - your tagged_index has align 2, size 4, triggering the need for my atomic alignment fix. As the static_assert advises, your code needs to define _ENABLE_ATOMIC_ALIGNMENT_FIX in order to pass. If this has already been fixed in 1.61.0, then that's great (I haven't checked). Thanks, STL

5 14

Getting started with boost in Codeblocks
by Karan Kapoor 11 May '16

11 May '16

Hi, This is Karan Kapoor,a 3rd year UG student at NSIT. Can somebody guide me how to get started with boost libraries while i am using codeblocks. Karan Kapoor

2 1

Boost.Random subtract_with_carry doesn't like m == numeric_limits<result_type>::digits
by Billy O'Neal (VC LIBS) 10 May '16

10 May '16

Hello, Boost folks. I found a bug in subtract_with_carry_engine while fixing a bug in MSVC++'s implementation of the same, where m == numeric_limits<result_type>::digits. Consider the following: #include <stdlib.h> #include <stdio.h> #ifdef USE_BOOST #include <boost/random/subtract_with_carry.hpp> using namespace boost::random; #else #include <random> using namespace std; #endif template <typename Engine> typename Engine::result_type run_10k(Engine engine) { for (int i = 0; i < 9999; ++i) { engine(); } return engine(); } int main() { subtract_with_carry_engine<unsigned long long, 64, 10, 24> ull_swc; ull_swc.seed(0x12341234'00000000); printf("0x%016llX\n", run_10k(ull_swc)); } MSVC++ said: 0xFCF0A4776BA0A6A8 Libstdc++ says: 0x01316AEA3646F686 Libc++ says: 0x01316AEA3646F686 Boost 1.60.0/libc++ + Clang says: 0x69E18848FE1BD36D Boost 1.60.0/libstdc++ + g++ says: 0x1DD6C263C41EEED0 MSVC++'s bug was that we did the underflow check incorrectly resulting in the carry bit always being set if m == numeric_limits<result_type>::digits. I fixed that and MSVC++ will agree with libstdc++ and libc++ in the next update; but boost's behavior here is still strange. Hope that helps, Billy Robert O'Neal III SDE II - Visual C++ Libraries bion(a)microsoft.com

2 1

[thread] API for getting/setting thread name in Boost?
by Bob Summerwill 10 May '16

10 May '16

I've also been working with an external developer which is getting Ethereum C++ working on Alpine Linux, as a statically linked executable using musl, rather than glibc. One rather confusing element was related to setting and getting thread names, which is the process of working through this issue, I find appears not to have made its way into either Boost or the C++11 standard library, though it must be a very common cross-platform use-case. https://github.com/ethereum/libweb3core/pull/73 https://github.com/ethereum/libweb3core/pull/73/files I've just added this comment-block, while fixing the issue: /// Set the current thread's log name. /// /// It appears that there is not currently any cross-platform way of setting /// thread names either in Boost or in the C++11 runtime libraries. What is /// more, the API for 'pthread_setname_np' is not even consistent across /// platforms which implement it. /// /// A proposal to add such functionality on the Boost mailing list, which /// I assume never happened, but which I should follow-up and ask about. /// http://boost.2283326.n4.nabble.com/Adding-an-option-to-set-the-name-of-a-bo… /// /// man page for 'pthread_setname_np', including this crucial snippet of /// information ... "These functions are nonstandard GNU extensions." /// http://man7.org/linux/man-pages/man3/pthread_setname_np.3.html /// /// Stack Overflow "Can I set the name of a thread in pthreads / linux?" /// which includes useful information on the minor API differences between /// Linux, BSD and OS X. /// http://stackoverflow.com/questions/2369738/can-i-set-the-name-of-a-thread-i… /// /// musl mailng list posting "pthread set name on MIPs" which includes the /// information that musl doesn't currently implement 'pthread_setname_np' /// https://marc.info/?l=musl&m=146171729013062&w=1 void setThreadName(std::string const& _n); Would I be right in assuming that this never happened? http://boost.2283326.n4.nabble.com/Adding-an-option-to-set-the-name-of-a-bo… If not, where can I log an issue to request that we revisit that? From what I can see, everybody is likely just cut-and-pasting much the same code for this functionality. http://stackoverflow.com/questions/10121560/stdthread-naming-your-thread Cheers, Bob Summerwill -- bob(a)summerwill.net

2 7

[config] Boost and the Intel (Linux) compiler
by Bob Summerwill 10 May '16

10 May '16

I am a developer on the Ethereum C++ client ( https://github.com/ethereum/webthree-umbrella) and have been working with an external developer on adding support to the codebase for building with the Intel Compiler on Ubuntu. Here is the full log of pain :-) https://github.com/ethereum/webthree-umbrella/issues/396 We've already merged various changes, and we appear to be getting down to the real hard ones, which are now mainly clustered around build issues with boost::multiprecision and seeming limitations with the Intel compiler and Like so: /home/libweb3core/libdevcore/Base64.h(48): error: no suitable conversion function from "boost::multiprecision::number<boost::multiprecision::backends::cpp_int_backend<160U, 160U, boost::multiprecision::unsigned_magnitude, boost::multiprecision::unchecked, void>, boost::multiprecision::et_off>" to "unsigned int" exists unsigned r = (unsigned)(a - a / 36 * 36); // boost's % is broken ^ detected during instantiation of "std::string dev::toBase36(const dev::FixedHash<N> &) [with N=20UL]" at line 114 of "/home/libethereum/libethcore/ICAP.cpp" This appears to be the key observation: https://github.com/ethereum/webthree-umbrella/issues/396#issuecomment-20659… "In summary, the intel platform supports this "convert_to" member function, but does not support implicit conversion of boost multiprecision types" Has anybody worked with Boost and the Intel compiler who might have some further insight into whether there is some way in which the Intel compiler "warts" can be handed within Boost? Or are we stuck with these nasty diffs/workarounds? https://github.com/ethereum/libethereum/pull/224/files https://github.com/ethereum/libweb3core/pull/68/files Cheers, Bob Summerwill Developer, Ethereum Foundation -- bob(a)summerwill.net

3 4

github issues tracking listing
by Vicente J. Botet Escriba 09 May '16

09 May '16

Hi, I would like to have the possibility to have github issues in my boost modules (thread/chrono/ratio). I see that Boost.Hana has its own issue list. What I need to do to add the possibility to add issues? Best, Vicente

3 3

Boost 1.61.0 Release Candidate 1
by Vladimir Prus 09 May '16

09 May '16

The release candidates for the 1.61.0 release are now available at: http://boost.cowic.de/rc/boost_1_61_0_rc1.zip http://boost.cowic.de/rc/boost_1_61_0_rc1.7z http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.bz2 http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.gz The SHA256 checksums are as follows: dcd11a91a412b2e8a78678b38cb2a74857e61f9bfe2577de9fd70be770100d54 boost_1_61_0_rc1.7z 476937369c7a82103b734ccae85d35a523cdb7f8462c5f2fe1217ff0c8e2a7df boost_1_61_0_rc1.tar.bz2 e60dee39ebb29d24bf8a4ef9aec34dbb8c1b9b219d4737ea4b358f38b1aab2b7 boost_1_61_0_rc1.tar.gz e5f662f44a65c5c19450b8a1c07f75c7d5f16e58667871e856ba3984ec082006 boost_1_61_0_rc1.zip 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 signed list of checksums is also attached, signed with the following key: https://pgp.mit.edu/pks/lookup?op=get&search=0xDA472E8659753BA4 Key fingerprint C5F0 F367 AA66 616F B839 806E DA47 2E86 5975 3BA4 Thanks! -- The release managers

14 38

[Style] Import a C function with wrong signature on purpose
by Klemens Morgenstern 08 May '16

08 May '16

Hi, for the boost.process library I need WinAPI functions which take an enumerator. Problem is: the forward-declaration doesn't work here, even with C++11. I.e. this code is still illegal, because X has a non-fixed type: enum X {}; enum X : typename std::underlying_type<X>::type ; I do however know which values the enum has take, thus I can redeclare it and have the reasonable expectation, that it will use the same underlying type. So theoretically, I could import the function into a seperate namespace (using extern "C") and use it, while having it declared with another enum type. I.e. you have in some C code the declaration: enum X { a,b,c}; void f(X); And I'll write in my code without including the other header: namespace import_thingy { extern "C" { enum X { a,b,c}; void f(X); } To be absolutely sure, I'd add an test, which asserts that the underlying types are equal. Now of course, that would never be accepted into the boost/winapi module, but I could just add this in my library. Would this be a dealbreaker for a library attempting to become a boost-library? If so, I'd need to put it into a source file and include windows.h there, but I'd really like the library to be header-only and under no circumstances include windows.h there. Thanks, Klemens

2 6

What to do about std::binary_function and std::unary_function?
by Nick Matteo 07 May '16

07 May '16

std::binary_function and std::unary_function are deprecated, and scheduled to be removed from the standard in C++17. That means it's possible that code using these might soon fail to compile when targeting this standard. These are still used throughout Boost, including by the libraries Accumulators, Algorithm, Bimap, Function, Functional, GIL, Graph, ICL, MPI, Polygon, and Xpressive. You can see all the uses I found in the 1.61 beta boost/ directory at http://kundor.github.io/ubinary_function_list.html . All that these classes do are provide the typedefs result_type, and argument_type (for unary_function) or first_argument_type and second_argument_type (for binary_function). In particular, they do not include a virtual operator(), so that one cannot accept a function object polymorphically as a std::binary_function&, for example. So, although it is conceivable that C++98-era user code might check for inheritance from std::binary_function, it seems rather unlikely: practically all uses should just depend on the typedefs being present (which is what the standard library has always done). With modern C++ standards, the availability of std::result_of, decltype, and std::function make these typedefs redundant, and references to them are being phased out of the standard library (starting with deprecation.) It seems to me that there are four main possibilities for removing these classes from Boost. (I'll talk about binary_function in the following, but it all applies equally to unary_function.) 1) Add some sort of compatibility macro to Boost.Config, to enable classes to inherit from std::binary_function if it is available, or add the appropriate typedefs if it is not. I don't think this is necessary. 2) Remove the inheritance from std::binary_function, and add the typedefs. This seems to be the default approach: it is used by the C++11 standard itself, and has also already been done by some Boost libraries, e.g. in container/string.hpp and in intrusive/priority_compare.hpp. The drawback here is increased verbosity. Instead of writing template <class T> struct functor : std::binary_function<T, T, bool> {...}; We must write template <class T> struct functor { typedef T first_argument_type; typedef T second_argument_type; typedef bool result_type; ... }; 3) A modification of approach 2: instead of manually adding the typedefs everywhere, make a base class to provide the typedefs somewhere in Boost. Then replace inheritance from std::binary_function<Arg1, Arg2, Result> with inheritance from boost::binary_function<Arg1, Arg2, Result>. 4) Just remove inheritance from std::binary_function (and don't provide typedefs.) This is the bold approach. The typedefs are redundant now: I think the only use in the standard library is by the deprecated std::not1/std:not2 and the deprecated binders std::bind1st/std::bind2nd (which are to be removed in C++17). This is the direction that the standard library is starting to head, with all uses of the typedefs deprecated and probably eventually removed, and even the provision of the typedefs optional in C++17 standard library function objects. This has already been done at least by Boost Interprocess in detail/mpl.hpp. Probably the best options are either (2) or (4). Should there be a default policy on what authors should do? Nick Matteo

5 6

Regression testing Clang/LLVM with VC14.
by degski 07 May '16

07 May '16

I have started a new thread as the other one "Testing of clang emualting the VC++ preprocessor on Windows" has become rather long and interlaced with less relevant musings. Here I would like to concentrate on the subject in the title. Sergey suggested I'd run regression tests, in the "other thread". I was hesitant at first, mostly due to the luke warm reception. Thanks to Google's simple coding of their spam filter, I actually missed the post by Niall Douglas of 4th of April. When it was referenced later and after I dug it from the archives, I became encouraged by the fact that maybe I wasn't all wrong and somebody within the community was actually thinking along similar lines as me. Following this I'd decided to take on regression testing. I chose to first simply test boost-develop against VC14, just to see how it goes. Some good, some bad. Was easy to set up (git already included with VC14, all what I needed to do was install python, which I normally have, but I'm having a new laptop). The bad, space required 44GB (advertised as 5GB). Possibly .pdb files (debugger symbols) are filling up disk-space uselessly. Next bad, the process finished with the following lines: # Done writing "C:\boost_develop\results\degski.xml". # Compressing "C:\boost_develop\results\degski.xml"... # Done writing "C:\boost_develop\results\degski.zip". # Uploading log archive "C:\boost_develop\results\degski.zip" to develop # <lambda> failed with message "[Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions" # Retrying (5 more attempts). # Uploading log archive "C:\boost_develop\results\degski.zip" to develop # <lambda> failed with message "[Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions" # Retrying (4 more attempts). # Uploading log archive "C:\boost_develop\results\degski.zip" to develop # <lambda> failed with message "[Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions" # Retrying (3 more attempts). # Uploading log archive "C:\boost_develop\results\degski.zip" to develop # <lambda> failed with message "[Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions" # Retrying (2 more attempts). # Uploading log archive "C:\boost_develop\results\degski.zip" to develop # <lambda> failed with message "[Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions" # Retrying (1 more attempts). # Uploading log archive "C:\boost_develop\results\degski.zip" to develop # <lambda> failed with message "[Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions" # Giving up. Traceback (most recent call last): File "run.py", line 71, in <module> runner(root) File "C:\boost_develop\boost_regression_src\regression.py", line 287, in __init__ self.main() File "C:\boost_develop\boost_regression_src\regression.py", line 624, in main getattr(self,action_m)() File "C:\boost_develop\boost_regression_src\regression.py", line 591, in command_regression self.command_upload_logs() File "C:\boost_develop\boost_regression_src\regression.py", line 538, in command_upload_logs lambda: File "C:\boost_develop\boost_regression_src\regression.py", line 663, in retry return f() File "C:\boost_develop\boost_regression_src\regression.py", line 546, in <lambda> self.dart_server ) File "C:\boost_develop\boost_regression_src\collect_and_upload_logs.py", line 430, in upload_logs upload_to_ftp( tag, logs_archive, ftp_proxy, debug_level, ftp_url ) File "C:\boost_develop\boost_regression_src\collect_and_upload_logs.py", line 256, in upload_to_ftp ftp = ftplib.FTP( ftp_site ) File "C:\Python27\lib\ftplib.py", line 120, in __init__ self.connect(host) File "C:\Python27\lib\ftplib.py", line 135, in connect self.sock = socket.create_connection((self.host, self.port), self.timeout) File "C:\Python27\lib\socket.py", line 575, in create_connection raise err socket.error: [Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions I've re-checked this page <http://www.boost.org/development/running_regression_tests.html>again, there's no mention of "registering" or something similar. Some tests must have failed, got prompted for starting the debugger twice (is the latter normal). This was a test-run (testing the testing), with VC14U2. Assuming the above can get sorted, I would in reality like to test Clang/LLVM (with VC14U2). I would like to ask (Niall Douglas in particular, I guess) what the suggested parameters to run.py should be for this combo. Should I target clang.exe or clang-cl.exe, develop or master. What about Clang/C2? How to reduce disk-space usage? degski

5 7

proposed new library "histogram"
by Hans Dembinski 06 May '16

06 May '16

Hi everybody, I recently added a new library called "histogram" to the Boost Incubator. I would like to advertise it a little here in the hope to find a person interested in reviewing it. I hope that shameless self-advertisement is not going against some rule of this list, but I am sure you will let me know. My background is in analysis of big data in the fields of particle physics and astroparticle physics. Boost is very popular among my peers, since it is a free, high-quality, rich, and very well maintained collection of libraries. There is a growing number of tools to do statistical analysis in Boost and I think this project would fit in nicely, and fill a gap. We work with histograms a lot, so that's why my interest came from. I am a senior programmer in C++ and Python with 10 years of experience. Guiding development through code reviews and tickets, as well as taking on responsibility for continuous maintenance, are natural for me. Naturally, I am willing to commit free time to maintain the project should it be accepted, and do my share of the work in this community. I put a lot of thought and effort into this project, the rationale and my design choices are explained in the documentation, which I wrote according to the advice given at the Boost Incubator website. The project is feature complete from my side. What it needs now is the input from the Boost community to round off possible edges and to make the interface rich enough for everybody. I am good at considering the user perspective, but I cannot anticipate everyone's needs. In case you got interested, here are the links: Incubator link: http://rrsd.com/blincubator.com/bi_library/histogram-2/?gform_post_id=1582 github link: https://github.com/HDembinski/histogram Best regards, Hans

6 15

1.61 release notes
by John Maddock 06 May '16

06 May '16

Is it too late to add release notes? Forgetfully yours, John.

2 1

Boost.Proto: specializing context::eval classes
by Brook Milligan 06 May '16

06 May '16

I am trying to use Boost.Proto with some user-defined function terminals. Following the documentation, this requires specialization of context::eval classes to handle new terminals. (Using the callable_context<> mechanism is too simplistic because that seems to require a uniform result_type.) However, doing as suggested (see the "Defining an Evaluation Context" section) does not compile when function terminals are involved. My solution is a new traits class that deduces the type of a terminal. This does allow successful specialization of context::eval on the type of terminal, even with functions. To illustrate this, I have attached a set of three files, one implementing an example proto function, one implementing the relevant metafunction, and one demonstrating both use cases: the one corresponding to the Boost.Proto documentation and the one corresponding to my alternative. I would appreciate comments on the following: - Is this a valid problem and a valid solution or have I missed a standard method using Boost.Proto that works to solve this pattern? - Is this the standard way of creating function terminals in Boost.Proto or have I done something there to trigger the problem? - If the answer to these questions indicates a missing feature within Boost.Proto, what is the process for fixing that? Thanks for any help you can offer. Cheers, Brook

1 0

[random] Using random_device needs to link to built library
by Edward Diener 06 May '16

06 May '16

Evidently if I use boost::random::random_device class in code I need to link to the built random library. Otherwise the random library is header only. Shouldn't this be mentioned somewhere in the Boost random documentation ?

1 0

[generic programming] header file for general "default" operations for C++ classes
by Walt Karas 05 May '16

05 May '16

In C++, a default assignment operator is generated for a class if all of its components (data members and base classes) have an assignment operator. There are plans in C++17 to do something similar for comparison operators. This header, in https://github.com/wkaras/C-plus-plus-library-default-operators , facilitates that, more generally, if there is an operation on all the components of a class, a single macro invocation can provide this operation on the class as well. A big drawback is that it's very intrusive into the class definition. Each class component must be defined using a macro, COMPOSITE_OP_MBR_T(int) i; for examle. The class will in truth be a template, with the template parameter being defaulted for normal usage. I don't know which, if any, existing Boot library this header would belong in.

3 4

[Promotional] ghournal - a commandline based blog engine for gh-pages
by Ganesh Prasad 05 May '16

05 May '16

***DISCLAIMER*** *This is a self promotional message and quite unrelated to Boost and C++. But I believe, it's something that makes lives of developers easier, in fact I built it to make my life easier. Now, as an OpenSource activity it needs some promotion to attract users and contributors alike. * *Also, I am not good at writing promotional messages, so this mail might look really messy. Hence, apologies in advance.* *********************************************************************************************** git is the lifeline of most of the OpenSource activities around the globe. We all write code, create projects on github and push our changes to the repo and blah blah blah... That's what we all do, git add | commit | merge | push are probably the most used commands on a developer's console, the command pattern is muscle memory. Now with the introduction of github-pages it has been possible to host static websites for your projects on github, most of the serious projects on github already have their static websites there. Sometimes we want to maintain blogs for our projects on the project website. But github-pages being a static platform does not provide backend scripting or database capabilities. So, conventional blogging (like on blogger/wordpress) is not natively possible on github-pages. Sometimes we wish that blogging was possible and conveniently easy to use on github-pages. Also, some of us (like me for instance) sometimes think like, "life would have been easier if blogging was as simple as git init..git commit...git push, maybe something like blog init... blog new... blog publish". *ghournal <https://www.npmjs.com/package/ghournal>* as a tool designed for users of git, makes these above wishes come true. It is a command line based blog management tool for static web hosts, targeted primarily towards the github-pages platform. *ghournal <https://www.npmjs.com/package/ghournal> *exposes a git like command structure for blogging from the terminal. Creating a blog is as easy as 'ghournal init', adding a new post is as simple as 'ghournal new <postID>' etc. The complete command structure is documented in the project README. *ghournal <https://www.npmjs.com/package/ghournal>* is written in javascript and is available on npm. Hence installing and using it can not me easier. In short, it is designed to make the lives of developers who want to blog about their projects easier. So, if this sounds cool, please have a look at https://www.npmjs.com/package/ghournal and thanks :) sincerely Ganesh Prasad

1 0

[config] Checking if put_time is in iomanip
by Edward Diener 04 May '16

04 May '16

Does anybody know of a way to check if the std::put_time functionality is part of iomanip ? It is supposed to be a part of C++11, but Boost.Config does not have any general way to check for C++11 that I know about. Nor do I find anything in SD-6 which would tell me if std::put_time is supported.

1 0

[chrono] Header only library build and boost::system dependency
by Edward Diener 04 May '16

04 May '16

The documentation for chrono says: "How to Build Boost.Chrono as a Header Only Library? When BOOST_CHRONO_HEADER_ONLY is defined the lib is header-only. If in addition BOOST_USE_WINDOWS_H is defined <windows.h> is included, otherwise files in boost/detail/win are used to reduce the impact of including <windows.h>. However, you will either need to define BOOST_CHRONO_DONT_PROVIDE_HYBRID_ERROR_HANDLING or link with Boost.System. " So I have: #define BOOST_CHRONO_HEADER_ONLY #define BOOST_CHRONO_DONT_PROVIDE_HYBRID_ERROR_HANDLING #include <boost/chrono.hpp> followed by some code using chrono, and I still get when linking my exe: gcc.link C:\Programming\VersionControl\modular-boost\build\boost\bin.v2\libs\cxx_dual\test\test_chrono.test\gcc-mingw-5.3\debug\test_chrono.exe C:\Programming\VersionControl\modular-boost\build\boost\bin.v2\libs\cxx_dual\test\test_chrono.test\gcc-mingw-5.3\debug\test_chrono.o: In function `_static_initialization_and_destruction_0': E:\Programming\VersionControl\modular-boost\libs\cxx_dual\test/../../../boost/system/error_code.hpp:221: undefined reference to `boost::system::generic_category()' E:\Programming\VersionControl\modular-boost\libs\cxx_dual\test/../../../boost/system/error_code.hpp:222: undefined reference to `boost::system::generic_category()' E:\Programming\VersionControl\modular-boost\libs\cxx_dual\test/../../../boost/system/error_code.hpp:223: undefined reference to `boost::system::system_category()' collect2.exe: error: ld returned 1 exit status Is there a way to use chrono without having to link boost::system ?

3 5

Naming convention of iterated binary operation
by Jeremy Murphy 03 May '16

03 May '16

Dear list entities, is there such a convention or precedent for naming an iterated binary operation? For example, Boost.Functional/Hash has an iterated hash() called hash_range(). I don't mind the "_range" suffix but I prefer the "iterated_" prefix based on the mathematical definition: https://en.wikipedia.org/wiki/Iterated_binary_operation The case in point is gcd() in Boost.Math: we want to provide an iterated gcd but we can't quite decide how to name it. I like the "iterated_" prefix but I would rather go with whatever might be the convention. Thanks, cheers. Jeremy

3 6

[predef] check and require logical operators and multiple expression questions
by Edward Diener 01 May '16

01 May '16

Is there any difference in the result when you use the 'and' logical operator or simplty specify more than one expression: lib my_special_lib : source.cpp : [ predef-require "BOOST_OS_WINDOWS" and "BOOST_COMP_CLANG"] ; lib my_special_lib : source.cpp : [ predef-require "BOOST_OS_WINDOWS" "BOOST_COMP_CLANG"] ; Are both the above equivalent ? Can I use both 'and' and 'or' in an expression ? If so does 'and' bind before 'or' does, so that 'expression1 and expression2 or expression3' is conceptually '(expression1 and expression2) or expression3' ? Can I use parentheses to bind an expression with 'and' and 'or' ?

1 0

boost chrono bad_cast (gcc > 4.9 on Mac)
by Min Yang Jung 01 May '16

01 May '16

Hi All, I was wondering if Boost.Chrono works with gcc > 4.9 on Mac. When system_clock::now() is called, it throws an std::bad_cast exception. The binary from the same code doesn’t have the issue if compiled with clang on Mac and gcc > 4.9 on Linux. The gcc compilers that I use are macport-installed gcc 4.9 and 5.0 (g++-mp-4.9 and g++-mp-5.0) on Mac. Any help would be appreciated. Thanks. Regards, Min Yang Jung

3 2