January 2014 - Boost - lists.boost.org

[git] boost + git flow
by Oliver Kowalke 22 Jan '14

22 Jan '14

does boost follows the git-flow schema, e.g. merging the changes from branch develop into master is not required by the library developer (this is done by the release manager)?! Oliver

5 4

[testing] Reports that lead nowhere?
by John Maddock 22 Jan '14

22 Jan '14

While we're updating and fixing testing issues, I notice the report generator is still creating content-free failures, for example this one: http://www.boost.org/development/tests/develop/developer/marshall-mac-regex… Ultimately leads nowhere :-( Thanks, John.

4 4

[regex] Need some help with msvc-11/12
by John Maddock 22 Jan '14

22 Jan '14

Can anyone with access to msvc-11 or 12 tell me what's causing this failure: http://www.boost.org/development/tests/develop/developer/output/DrWeb_vc12_… You will probably need to build and run under the debugger to find out I suspect... Many thanks in advance, John.

3 4

Support for Android
by Vicente J. Botet Escriba 22 Jan '14

22 Jan '14

Hi, I see that there are some trouble with Boost and Android: https://svn.boost.org/trac/boost/ticket/9082 http://www.boost.org/development/tests/develop/developer/output/apolukhin-A… Could someone state what is the Boost approach to support Android? Should the user build with NDK r8e? Does bjam supports a specific android platform? Best, Vicente

4 11

[wave] preprocessor directives in output
by Eric Niebler 22 Jan '14

22 Jan '14

I'm looking at automating the regeneration of Fusion's preprocess headers with the wave tool. Currently, it's impossible because of stuff like this (from container\vector\vector.hpp): #if !defined(BOOST_NO_CXX11_RVALUE_REFERENCES) vector(vector&& rhs) : vec(std::forward<vector_n>(rhs.vec)) {} #endif When the wave driver is run, either BOOST_NO_CXX11_RVALUE_REFERENCES is defined, in which case the block of code gets left out, or else it isn't, in which case the block of code is left in. Both are wrong. What should happen is that the #if and #else directives should be present in wave's output. I can keep wave from expanding certain named macros with the -N switch, but there doesn't seem to be a way to selectively keep wave from evaluating #if/#else directives. Or is there? Any help appreciated. Eric

8 18

[variant] Breaking change introduced by variadic support
by Agustín K-ballo Bergé 22 Jan '14

22 Jan '14

The recent changes to introduce variadic support to `variant` introduce breaking changes in the documented macros. When variadic support is detected, `BOOST_VARIANT_LIMIT_TYPES` is not defined and `BOOST_VARIANT_ENUM_[SHIFTED_]PARAMS` uses variadic templates instead of enumerating parameters. This is a breaking change in the documented interface, and one that requires all but the simplest use cases to be rewritten. For instance, this breaks _Boost.Spirit_ support of `variant` (https://svn.boost.org/trac/boost/ticket/9238) requiring two different implementations to be provided. Is this the preferred path to take? I would suggest instead to keep the macros as documented at all times, and let the user handle the variadic case manually. This would allow users to support both variadic and non-variadic `variant`s up to a certain limit with a single code case (without breaking the documented interface), and result in cleaner code for those cases that only target compilers with variadic support. There's no point in using a macro if it won't work for both cases. Regards, -- Agustín K-ballo Bergé.- http://talesofcpp.fusionfenix.com

3 8

[phoenix] New maintainer
by Fletcher, John P 21 Jan '14

21 Jan '14

I have just agreed to play a part in the maintenance of Boost Phoenix. I am working with a lot of help from Joel, Thomas and Eric. I have been looking at the bugs logged on the system and it seems as though there are a number of reported problems which need to be tackled, in particular 9362 and 9363. Please bear with me as I learn the modular-boost system and look for fixes for the problems. If you have any information on your problems with Phoenix, in particular any not already on the bug system, please let me know. Best wishes John

3 3

Reboot the CREST server machines
by DongInn Kim 21 Jan '14

21 Jan '14

Dear All, The current CREST servers need to reboot to kick in a new kernel and to mount a NFS server with a new IP address. If things are not too critical nowadays, I would like to reboot the following server machines next Tuesday (Jan 21st). - lion.crest.iu.edu - tiger.crest.iu.edu - wowbagger.crest.iu.edu - leopard.crest.iu.edu - jaguar.crest.iu.edu Date: Jan 21st, Tuesday Time: 6:00am-6:30am Pacific US time 7:00am-7:30am Mountain US time 8:00am-8:30am Central US time 9:00am-9:30am Eastern US time 12:00pm-12:30pm GMT The list of services that may not be available: - NFS - Web services www.crest.iu.edu www.open-mpi.org www.boost.org svn.crest.iu.edu/svnmanager ... - Mailing lists - Subversion - LDAP authentication (login to the Linux workstations and cutter cluster) Please let me know if you have any questions or concerns about this booting schedule. Regards, -- - DongInn

1 1

bjamming that used to work before modular-boost
by Paul A. Bristow 20 Jan '14

20 Jan '14

I have a jamfile.v2 in a sandbox project that used to work before. I have started using modular-boost, and after some fumbling, I'm using that OK-ish. The message is: Unable to find the Boost source tree in the locations searched. Try setting the environment variable BOOST to point to your Boost tree, or else invoke bjam with the --boost=path option. The Boost include path will not be automatically set. The paths searched were I:\boost-sandbox\guild/../boost I:\boost-sandbox\guild/../Trunk But the file LICENSE_1_0.txt was not found in any of them Unable to find the Boost.Build source tree in the locations searched. Try setting the environment variable BOOST_BUILD to point to your Boost.Build tree, or else invoke bjam with the --boost-build=path option. The paths searched were i:\modular-boost\tools\build\v2 But bootstrap.jam was not found in any of these More failures will very likely follow... (And they did ;-( ) I've tried some guesses at parameters including b2 --boost=i:\modular-boost --boost-build=i:\modular-boost\tools\build -a html without success. I have boost-build.jam at I:\modular-boost Suggestions please. Paul PS I'd like to change environment variables if possible to avoid changing lots of .bat files that call b2. --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow(a)hetp.u-net.com

4 8

Forthcoming Boost.Fiber review
by Nat Goodspeed 20 Jan '14

20 Jan '14

Hi all, The review of Boost.Fiber by Oliver Kowalke is scheduled from Monday, January 6th to January 12th. ----------------------------------------------------- About the library: Boost.Fiber provides a framework for micro-/userland-threads (fibers) scheduled cooperatively. The API contains classes and functions to manage and synchronize fibers similar to Boost.Thread. Each fiber has its own stack. A fiber can save the current execution state, including all registers and CPU flags, the instruction pointer, and the stack pointer and later restore this state. The idea is to have multiple execution paths running on a single thread using a sort of cooperative scheduling (versus threads, which are preemptively scheduled). The running fiber decides explicitly when it should yield to allow another fiber to run (context switching). Boost.Fiberinternally uses coroutines from Boost.Coroutine <http://ok73.funpic.de/boost/libs/coroutine/index.html>; the classes in this library manage, schedule and, when needed, synchronize those coroutines. A context switch between threads usually costs thousands of CPU cycles on x86, compared to a fiber switch with a few hundred cycles. A fiber can only run on a single thread at any point in time. docs: http://ok73.funpic.de/boost/libs/fiber/doc/html/index.html<http://ok73.ok.funpic.de/boost/libs/coroutine/doc/html/> git: https://github.com/olk/boost-fiber src: http://ok73.ok.funpic.de/boost.fiber.zip<http://ok73.ok.funpic.de/boost.coroutine.zip> --------------------------------------------------- Naturally, you need not wait until the review formally opens to start reviewing the Fiber library. Please always state in your review whether you think the library should be accepted as a Boost library! Additionally please consider giving feedback on the following general topics: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? Nat Goodspeed Boost.Fiber Review Manager ------------------------------

6 8