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

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

[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

[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

[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

[1.61] Two weeks remaining for new libraries and breaking changes
by Vladimir Prus 19 Mar '16

19 Mar '16

I wanted to remind that the master branch is closing for new libraries and breaking changes on Feb 24, about two weeks from now. We'll be closed for major changes on March 2. That's not a lot of time, please make sure any big work is completed. Thanks, -- Vladimir Prus http://vladimirprus.com

10 38

[Fit] pipable order of the arguments
by Vicente J. Botet Escriba 05 Mar '16

05 Mar '16

Hi, I would like to know what other think about the order of the pipe (See this issue https://github.com/pfultz2/Fit/issues/5) What would be the expected meaning of auto r1 =1 | pipable(f)(2); f(1,2) or f(2,1)? What would be the expected meaning of auto f2 = partial(f)(2); auto r1 =1 | pipable(f2); f(1,2) or f(2,1)? As the operator| has left-to-right associativity, we can not do auto x = 1 | 2 | pipable(f); We would need a way to pack the parameters auto x = forward_as_tuple(1, 2) | pipable(f); but this wouldn't compile as f has two parameters. or use parenthesis auto x = 1 | (2 | pipable(f)); and the result will be f(2, 1). Any ideas? Best, Vicente Vicente

1 1

[gsoc16] Boost rejected as GSoC 2016 org
by Niall Douglas 02 Mar '16

02 Mar '16

Dear Boost, It is with a heavy heart I write to say that Boost was rejected as an org for Google Summer of Code 2016 by Google. We had our application submitted in time, it was reviewed by three members of the Boost leadership, our ideas list had six solid ideas with an especially solid seventh on the way, we were in very good standing with Google and there was no reason to expect rejection. We have asked for clarification as to why we were rejected, and we shall try to improve our application next year to improve our chances. We recognise that many students and mentors will be extremely disappointed by this news. We share in that disappointment, and all we can say is please try again next year. For those students and mentors who are continuing a previous GSoC on an existing Boost library, there may be a possibility that Boost may be able to fund those continuations this year. Each case will be approached by the steering committee on a case by case basis, and be aware that the standard required for funding by Boost is considerably above that of Google's with an accompanying high and detailed standard of funding application to the steering committee. Contact us privately if you want to know more. On other news we had been expecting to announce today that Bryce Adelstein Lelbach has generously agreed to take over as secondary GSoC admin from Boris Schäling who has served Boost GSoC for something like four years now, so he has definitely earned himself a rest! Our thanks to Boris for his service, and welcome Bryce to the team! Finally, I'd like to thank Jon Kalb who moved heaven and earth as he always does to get the GSoC application submitted in time. Yours, Niall Douglas -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

18 24

[doc] Liven up Boost Documentation with Java Script?
by Krzysztof Jusiak 01 Mar '16

01 Mar '16

Dear Boosters, I'm writing to ask about your opinion regarding more interactive documentation for Boost. I know already that some of you would like to see online documentation without Java Script and that's absolutely fine and I agree that documentation should be available for anyone and any configuration. Nevertheless, I would like to know what the Boost community thinks about having following features in the documentation... * Run the code online (allows to check library with one click) * Comments (allows commenting on the documentation) * Chats (allows discussing issues and solutions) Personally, I have found above features extremely useful when checking out other languages/libraries and therefore I have implemented solutions for C++ too. Please, check it out (JS is required)... http://boost-experimental.github.io/msm-lite http://boost-experimental.github.io/di If there is an interest I can provide generic solution to allow developers to write documentation using markdown (mkdocs) and simply integrate it with their libraries. Currently, theme is just slightly modified version of readthedocs, however Paul Fultz II has prepared a boost theme for Fit library ( https://github.com/pfultz2/mkdocs-boost) already and it might be easily integration with the JS facilities provided. Cheers, Kris

8 26

Re: [boost] [Boost-users] [Fit] upcoming formal review for Boost.Fit
by paul Fultz 29 Feb '16

29 Feb '16

On Sunday, February 28, 2016 12:23 PM, Edward Diener <eldiener(a)tropicsoft.com> wrote: > > >On 2/27/2016 11:16 AM, Vicente J. Botet Escriba wrote: >> Dear Boost community, >> >> The formal review of Paul Fultz II's Fit library starts on Wednesday, 2nd March and ends on 13th March. > >How do I generate the docs or run the tests for my local copy of Fit ? > You can build and run the tests by building the check target. For those unfamiliar with cmake, first configure the build directory with cmake: mkdir build cd build cmake .. cd .. Next build the check target using the native build system(such as make or msbuild). CMake can call the native build system to build the target 'check', like so: cmake --build build --config Release --target check Also, the library can be installed by invoking the 'install' target. The documentation needs to be built using mkdocs. You can install mkdocs and the boost theme with pip like this: pip install mkdocs mkdocs-boost Then to build the documentation, first `setup.py` must be run to extract the documentation and examples from the source code, then `mkdocs` can be invoked, like this: python setup.py mkdocs build -t boost And the documentation will be in the 'doc/html' directory. Paul

4 6

C++Now Student/Volunteers Call for Applications
by Jon Kalb 29 Feb '16

29 Feb '16

The Call for Applications for Student/Volunteers for C++Now 2016 (AKA BoostCon X) has been released: http://cppnow.org/2016-conference/announcements/2016/02/23/student-volunteer -program-accepting-applications.html The application submission deadline is March 16th. We are looking for students with a strong interest in C++. The opportunity is open to student of any level or any field of study. Jon Kalb Chair, C++Now 2016

1 0

[filesystem] cygwin paths
by Steven Watanabe 29 Feb '16

29 Feb '16

AMDG Does Boost.Filesystem have any support at all for cygwin paths? I know that you want to use Windows paths internally, but this creates problems for programs that get paths from an external source. In particular, it causes the regression tests to fail when running from cygwin. See https://github.com/boostorg/regression/issues/37. else if ( !locate_root.is_complete() ) { locate_root = ( fs::initial_path() / locate_root ).normalize(); } locate_root is created by locate_root = fs::path( *args_i ); i.e. it's taken directly from the command line. In Christ, Steven Watanabe

1 0

Version mismatch
by Neil Gatenby 29 Feb '16

29 Feb '16

As per http://lists.boost.org/Archives/boost/2015/05/222520.php, I'm seeing (on master) Jamroot version set to 1.60 and version.hpp calling the release 1.61.0 I can work around the problems it's causing, but I note it, FYI Cheers Neil

1 0

[Fit] upcoming formal review for Boost.Fit
by Vicente J. Botet Escriba 29 Feb '16

29 Feb '16

Dear Boost community, The formal review of Paul Fultz II's Fit library starts on Wednesday, 2nd March and ends on 13th March. Fit is a header-only C++11/C++14 library that provides utilities for functions and function objects. Fit is: - Modern: Fit takes advantages of modern C++11/C++14 features. It support both `constexpr` initialization and `constexpr` evaluation of functions. It takes advantage of type deduction, variadic templates, and perfect forwarding to provide a simple and modern interface. - Relevant: Fit provides utilities for functions and does not try to implement a functional language in C++. As such, Fit solves many problems relevant to C++ programmers, including initialization of function objects and lambdas, overloading with ordering, improved return type deduction, and much more. - Lightweight: Fit builds simple lightweight abstraction on top of function objects. It does not require subscribing to an entire framework. Just use the parts you need. Fit is divided into three components: * Function Adaptors and Decorators: These enhance functions with additional capability. * Functions: These return functions that achieve a specific purpose. * Utilities: These are general utilities that are useful when defining or using functions Fit has been tested on gcc 4.6-4.9, clang 3.4-3.7, and Visual Studio 2015. For more information see: Github:https://github.com/pfultz2/Fit/tree/boost Documentation:http://pfultz2.github.io/Fit/doc/html/ Note that, as Fit is a functional library, the semantic of the functions is given in the form of `equations` instead of the classic effects, returns schema. This is because most of the functions have no side effects. E.g. the semantic of the function flip is defined as |assert(flip(f)(x, y, xs...) == f(y, x, xs...));| and the semantic of compose as |assert(compose(f, g)(xs...) == f(g(xs...)));| We await your feedback! Best regards, Vicente J. Botet Escriba P.S. Paul, now it is time to freeze the version that will be reviewed. I suggest you to create a branch on which you could fix the review issues.

3 2

[gsoc16] Static Map Competency test
by Karim Tarabishy 28 Feb '16

28 Feb '16

Hello, I have some questions regarding the test: 1) You have asked why did I chose this constexpr hashing function, do you mean this for the hashing algorithm it self like its collision rate and speed relative to other hashing algorithms? 2) I wanted to check about the elegant and useful error for the case of using an array of different size or using non string literals, does the error message appearing here http://melpon.org/wandbox/permlink/TFEP1yUc7pjukowH suffice? 3) Can I have feedback on the code and the simple tests? http://melpon.org/wandbox/permlink/HiFu9KXClEWDS1Of Thanks in advance. Karim Amr, Seniors Class, Software Engineer -- View this message in context: http://boost.2283326.n4.nabble.com/gsoc16-Static-Map-Competency-test-tp4683… Sent from the Boost - Dev mailing list archive at Nabble.com.

2 3

[test-matrx] problem with testing expected compile-time failures.
by Andrzej Krzemienski 28 Feb '16

28 Feb '16

Hi Everyone, I need help trying to understand how the testing of desired compile-time failures work. I know the concept in general, but I observe something strange in test results for Optional in Master: http://www.boost.org/development/tests/master/developer/optional.html I have a test called optional_test_ref_convert_assign_const_int_prevented <https://github.com/boostorg/optional/blob/master/test/optional_test_ref_con…> It is marked (intentionally) "cf": "only try to compile and expect a failure".But on tester sun- 12.4_stlport4 the test results are marked as "comp" which indicates an *unexpected* compile-time failure. This confuses me: * I marked the test "expect compile-time failure". * Test results are marked as "unexpected compile-time failure". Am I missing something? Not to mention that there is no compiler output included: http://www.boost.org/development/tests/master/developer/output/oracle-intel… Thanks, &rzej

2 2

Test results marked as failure without errors
by Abel Sinkovics 28 Feb '16

28 Feb '16

Hi, Some of the Metaparse tests are marked as failures, however I see no errors in the output. Here are two examples (one for gcc and one for msvc) http://www.boost.org/development/tests/develop/developer/output/igaztanaga-… http://www.boost.org/development/tests/develop/developer/output/igaztanaga-… Both the compile and link steps succeed and there is nothing about the execution of the compiled code. Does someone know why these are marked as failures? Thanks, Ábel

4 5

[Container] Inner Smart Pointers
by Phil Bouchard 28 Feb '16

28 Feb '16

I have to admit MSVC 2015 got a clean STL... block_ptr_test2.cpp doesn't crash but some assertions are wrong (in my block_ptr tests). Is there any plans from Boost to make the Boost.Container work with inner smart pointers? I don't think there is any other alternative if people want to plugin memory management. Thanks, -Phil

4 16

Re: [boost] [Boost-users] [Fit] upcoming formal review for Boost.Fit
by Vicente J. Botet Escriba 27 Feb '16

27 Feb '16

Le 27/02/2016 20:18, Edward Diener a écrit : > On 2/27/2016 11:16 AM, Vicente J. Botet Escriba wrote: >> Dear Boost community, >> >> The formal review of Paul Fultz II's Fit library starts on Wednesday, >> 2nd March and ends on 13th March. > > What is the branch of Fit we are going to be reviewing ? The boost branch. The link https://github.com/pfultz2/Fit/tree/boost points directly to the repository that will be reviewed. Vicente

1 0

Maintainer of bimap
by Sebastien Loriot 27 Feb '16

27 Feb '16

Hi, Is there still somebody in charge of the bimap package? There are 2 trivial pull requests lying around since last summer. It would be nice to see them integrated. Thanks, Sebastien.

2 1

[config] config.requires and simple_run
by Steven Watanabe 27 Feb '16

27 Feb '16

AMDG I've just been trying to get MinGW working without requiring the compiler's bin directory to be in the PATH. It mostly works now, but unfortunately I ran into problems with simple_run_action. The problem essentially is that this rule ignores RUN_PATH, which may be set by some toolsets (a quick grep shows borland, cw, gcc, and intel) to indicate additional paths that must be added to PATH when running the executable. In addition, I'm wondering how this is supposed to work with a cross-compiler. We really shouldn't be requiring cross-compilers to have access to the target system for ordinary builds. In Christ, Steven Watanabe

2 4

Can't build in status?
by John Maddock 27 Feb '16

27 Feb '16

I can't seem to get building anything in the status directory working, I'm using: bjam --dump-tests msvc-14.0 -n But any combination of arguments seems to fail, the failures are: M:/data/boost/boost/tools/build/src/build\property.jam:743: in class(a)property-map.find from module object(property-map)@236 error: Ambiguous key M:/data/boost/boost/tools/build/src/build\type.jam:333: in generated-target-ps from module type M:/data/boost/boost/tools/build/src/build\type.jam:270: in type.generated-target-suffix from module type M:/data/boost/boost/tools/build/src/build\virtual-target.jam:509: in virtual-target.add-prefix-and-suffix from module virtual-target M:/data/boost/boost/tools/build/src/build\virtual-target.jam:468: in _adjust-name from module object(file-target)@149078 M:/data/boost/boost/tools/build/src/build\virtual-target.jam:253: in abstract-file-target.__init__ from module object(file-target)@149078 M:/data/boost/boost/tools/build/src/build\virtual-target.jam:561: in class(a)file-target.__init__ from module object(file-target)@149078 M:/data/boost/boost/tools/build/src/kernel\class.jam:90: in class.new from module class M:/data/boost/boost/tools/build/src/build\generators.jam:558: in generator.generated-targets from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/tools\builtin.jam:886: in linking-generator.generated-targets from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/tools\unix.jam:67: in generated-targets from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/build\generators.jam:459: in construct-result from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/build\generators.jam:412: in run-really from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/build\generators.jam:386: in generator.run from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/tools\builtin.jam:801: in linking-generator.run from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/tools\unix.jam:41: in unix-linking-generator.run from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/tools\gcc.jam:692: in class(a)gcc-linking-generator.run from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/build\generators.jam:994: in try-one-generator-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1056: in try-one-generator from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1294: in construct-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1378: in generators.construct from module generators M:/data/boost/boost/tools/build/src/tools\python.jam:1160: in class(a)python-test-generator.run from module object(python-test-generator)@244 M:/data/boost/boost/tools/build/src/build\generators.jam:994: in try-one-generator-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1056: in try-one-generator from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1294: in construct-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1378: in construct from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1069: in generators.construct-types from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:609: in convert-to-consumable-types from module object(generator)@245 M:/data/boost/boost/tools/build/src/build\generators.jam:405: in run-really from module object(generator)@245 M:/data/boost/boost/tools/build/src/build\generators.jam:386: in class(a)generator.run from module object(generator)@245 M:/data/boost/boost/tools/build/src/build\generators.jam:994: in try-one-generator-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1056: in try-one-generator from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1294: in construct-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1378: in generators.construct from module generators M:/data/boost/boost/tools/build/src/build\targets.jam:1553: in construct from module object(typed-target)@19839 M:/data/boost/boost/tools/build/src/build\targets.jam:1353: in class(a)basic-target.generate from module object(typed-target)@19839 M:/data/boost/boost/tools/build/src/build\targets.jam:774: in generate-really from module object(main-target)@148055 M:/data/boost/boost/tools/build/src/build\targets.jam:746: in class(a)main-target.generate from module object(main-target)@148055 M:/data/boost/boost/tools/build/src/build\targets.jam:895: in targets.generate-from-reference from module targets M:/data/boost/boost/tools/build/src/build\targets.jam:1266: in generate-dependencies from module object(alias-target-class)@19840 M:/data/boost/boost/tools/build/src/build\targets.jam:1323: in class(a)basic-target.generate from module object(alias-target-class)@19840 M:/data/boost/boost/tools/build/src/build\targets.jam:774: in generate-really from module object(main-target)@148056 M:/data/boost/boost/tools/build/src/build\targets.jam:746: in class(a)main-target.generate from module object(main-target)@148056 M:/data/boost/boost/tools/build/src/build\targets.jam:272: in class(a)project-target.generate from module object(project-target)@19754 M:/data/boost/boost/tools/build/src/build\targets.jam:272: in class(a)project-target.generate from module object(project-target)@2060 M:/data/boost/boost/tools/build/src\build-system.jam:710: in load from module build-system M:\data\boost\boost\tools\build\src/kernel\modules.jam:295: in import from module modules M:\data\boost\boost\tools\build\src/kernel/bootstrap.jam:139: in boost-build from module M:\data\boost\boost\boost-build.jam:17: in module scope from module Anyone any ideas? Thanks, John.

2 11

[Experimental Boost.DI] [v1.0.0 released] [Looking for a Review Manager] Your C+14 Dependency Injection library with no overhead and compile time creation guarantee!
by Krzysztof Jusiak 27 Feb '16

27 Feb '16

Dear Boosters, I have just released version 1.0.0 of experimental Boost.DI library. Your C++14 header only Dependency Injection library with no dependencies. Library entered Boost Formal Review Queue some time ago and right now, IMHO, is ready to be reviewed. http://www.boost.org/community/review_schedule.html Therefore, I'm looking for a Review Manager, so if you think that Boost.DI is good enough to be reviewed and you would like to help with it, please let me know. Thank you! In the mean time check out the library yourself online! http://boost-experimental.github.io/di/examples/index.html Or read the interactive documentation... http://boost-experimental.github.io/di Or check out the source code... https://github.com/boost-experimental/di Why Boost.DI? * Boost.DI has none or minimal run-time overhead * Boost.DI compiles fast / Faster than Java-Dagger2! * Boost.DI gives short diagnostic messages * Boost.DI is non-intrusive * Boost.DI reduces boilerplate code * Boost.DI reduces testing effort * Boost.DI gives better control of what and how is created * Boost.DI gives better understanding about objects hierarchy Read more why here -> http://boost-experimental.github.io/di/index.html Any feedback is more than welcome! Cheers, Kris

9 34

GSOC-2016
by Abhimanyu Shekhawat 27 Feb '16

27 Feb '16

Hi there ! I am Abhimanyu Shekhawat, a sophomore perusing B.E(Hons)Computer Science, Birla Institute of Technology & Science, Pilani - Goa,India. I would like to take part in GSOC Programme 2016 with Boost Community. Actually I am very excited about contributing to open source projects and I already have experiences with some of the college based projects till now.I feel that being able to work in open source community will not only expose me to new learning avenues but will also give me a chance to contribute to the a much larger community. As far as my background is concerned,I have taken a course on Discreet Mathematics and currently perusing a rigorous Algorithm and Data structure course. Also I have got an intermediate level of skill set in C++,C,Java,Android and Mysql while a basic understanding of python. I hope that my skills and enthusiasm will prove an asset to the community.So I will be grateful if you can get me started Thank you :D

3 2

[hana] missing .gitattributes
by Steven Watanabe 26 Feb '16

26 Feb '16

AMDG I just noticed that all the files for hana had \n line endings in my working copy. To fix this I had to copy .gitattributes from the superproject. (Or am I just using git wrong) In Christ, Steven Watanabe

3 5