- Boost - lists.preview.boost.org

[thread 1.48] Multiple interrupt/timed_join leads to deadlock
by Gaetano Mendola 12 Dec '12

12 Dec '12

Hi all, I was investigating a rare deadlock when issuing an interrupt and a timed_join in parallel. I come out with the the following code showing the behavior. This is the backtrace of it: http://pastebin.com/xArHgHXf The deadlock is rare so sometime you need to wait a bit. I couldn't try it with boost 1.52 because the code is invalid due the precondition of "thread joinable" when issuing the timed_join. Is the code not valid or a real bug? Regards Gaetano Mendola ////////////////////// CODE ////////////////////// #include <iostream> #include <boost/thread.hpp> struct Runner { void operator()() { const boost::posix_time::time_duration mySeconds = boost::posix_time::seconds(100); boost::this_thread::sleep(mySeconds); } }; struct Interrupter { Interrupter(boost::thread& aThread, boost::barrier& aBarrier) : theThread(aThread), theSeconds(boost::posix_time::seconds(1)), theBarrier(aBarrier) { } void operator()() { theBarrier.wait(); for (int i=0; i<1000;++i) { theThread.interrupt(); theThread.timed_join(theSeconds); } } boost::thread& theThread; boost::posix_time::time_duration theSeconds; boost::barrier& theBarrier; }; int main() { for (size_t i = 0; i < 1000000; ++i) { Runner myRunner; boost::thread myRunnerThread(myRunner); boost::barrier myBarrier(2); Interrupter myInterrupter1(myRunnerThread, myBarrier); Interrupter myInterrupter2(myRunnerThread, myBarrier); boost::thread myInterrupterThread1(myInterrupter1); boost::thread myInterrupterThread2(myInterrupter2); myInterrupterThread1.join(); myInterrupterThread2.join(); myRunnerThread.join(); std::cout << "."; std::cout.flush(); } }

5 34

[thread] [Boost-testing] Trunk regression failed on missing 'virtual_noexcept.cpp'
by Rene Rivera 11 Dec '12

11 Dec '12

Seems the thread lib has some missing test files? ---------- Forwarded message ---------- From: Jim Bell <Jim(a)jc-bell.com> Date: Tue, Dec 11, 2012 at 10:37 AM Subject: [Boost-testing] Trunk regression failed on missing 'virtual_noexcept.cpp' To: Running Boost regression tests <boost-testing(a)lists.boost.org> error: at G:/boost/GCC/trunk/tools_bb/**kernel\modules.jam:107 error: Unable to find file or target named error: 'virtual_noexcept.cpp' error: referred to from project at error: '../libs/thread/test' ______________________________**_________________ Boost-Testing mailing list Boost-Testing(a)lists.boost.org http://lists.boost.org/**mailman/listinfo.cgi/boost-**testing<http://lists.boost.org/mailman/listinfo.cgi/boost-testing> -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

2 1

Request for interest in a library to ease double dispatching
by Per Karlström 11 Dec '12

11 Dec '12

Hi, I have been tinkering on a template library to ease the use of double dispatching. Now I know there are other techniques such as visitor patterns that might solve this problem in a more general way. However I believe that there are occasions when using double dispatch is a good way forward. I have some excerpts of example code at the end of this mail. Of course if I somehow have missed a boost library that already handles this I would be happy to know about it. So if there is even any interest for this I would be happy if someone would like to cooperate with me to make this library better and in the end so good so that it can be part of boost. I feel I do not have the time to spare to finalize this on my own, plus I feel I still have things to learn and would be happy to cooperate with someone more experienced in template programming. What I in that case need help with is: *How (or is it) possible to make the library more transparent to the number of types that should be in the double dispatch hierarchy. Right now, as I have shown in the code at the end of this mail, you have to put a post-fix number telling how many types to use. *How (if possible) can a class be double dispatchable with different return types. The way I solved it was with a union. But would it somehow be possible to do like this struct Val : public DoubleDispatchable<bool,A,B>, public DoubleDispatchable<int,A,B> *What else would be needed to start the journey to make this a library fit for boost (is it even good enough to ever make into boost?) If anyone is interested in a cooperation I am happy to provide my working draft of this library and to have a more private talk about how we could move forward. Best Regards Per Karlström For now a union is used to hold the return value to make this simmilar for all types of returns. union ReturnVal { float float_type_m; bool bool_type_m; ReturnVal(const bool& bool_type_):bool_type_m(bool_type_){} ReturnVal(const float& float_type_):float_type_m(float_type_){} ReturnVal():bool_type_m(false){} }; In essence a library user can define handler classes akin to this: struct less : public DoubleDispatchHandler_3<ReturnVal,A,B,C> { return_type handle_alpha_alpha(const alpha_type& arg1, const alpha_type& arg2) const {return arg1 < arg2} return_type handle_alpha_beta (const alpha_type& arg1, const beta_type& arg2) const {return true;} return_type handle_alpha_gamma (const alpha_type& arg1, const gamma_type& arg2) const {return true;} //And all other combinations }; Or with a default function struct equal : public DoubleDispatchHandler_3<ReturnVal,A,B,C> { return_type handle_default() const {return false;} return_type handle_alpha_alpha(const alpha_type& arg1, const alpha_type& arg2) const; return_type handle_beta_beta (const beta_type& arg1, const beta_type& arg2) const; return_type handle_gamma_gamma (const gamma_type& arg1, const gamma_type& arg2) const; }; Then the base class is derived from DoubleDispatchable class Val : public DoubleDispatchable_3<ReturnVal,A,B,C> { public: virtual ~Val(){} virtual std::ostream& print(std::ostream& ost) const=0; virtual bool operator<(const Val& other) const =0; virtual bool operator==(const Val& other) const =0; virtual float combine(const Val& other) const =0; }; While Child classes had to define the member function dispatch_<type> struct A : public Val { int val_m; private: //Handles the first double dispatch call return_type dispatch_alpha(const alpha_type& alpha, const handler_type& handler) const { return double_dispatch(alpha,*this,handler); } return_type dispatch_beta(const beta_type& beta, const handler_type& handler) const { return double_dispatch(beta,*this,handler); } return_type dispatch_gamma(const gamma_type& gamma, const handler_type& handler) const { return double_dispatch(gamma,*this,handler); } public: A(const int& val_=0):val_m(val_){} //Normal calls to the operators via a template function bool operator<(const Val& other) const { return double_dispatch(*this,other,less()).bool_type_m; } bool operator==(const Val& other) const { return double_dispatch(*this,other,equal()).bool_type_m; } float combine(const Val& other) const { return double_dispatch(*this,other,add()).float_type_m; } std::ostream& print(std::ostream& ost) const { ost<<"A("<<val_m<<")"; return ost; } }; class B{...}; class C{...};

3 5

Registration for C++Now 2013 is now open
by Boris Kolpackov 11 Dec '12

11 Dec '12

The seventh annual C++Now Conference (formerly BoostCon) will be held at the Aspen Center for Physics in Aspen, Colorado, May 12th to 17th, 2013. "We are thrilled to announce the second annual C++Now conference, the whole-language edition of BoostCon covering all the coolest topics in C++," said Dave Abrahams, Conference Co-Chair. "In 2012, we broadened the conference scope by adding a third track and offering more C++11 coverage than any other event, and the community responded with an unprecedented number of registrations. In 2013, we are going to build on that success with foundational sessions integrating what we've all learned about using C++11 during the past year, while continuing the exploration of cutting-edge topics that BoostCon attendees have come to expect." Early Bird Savings Deadlines! Early Bird conference registration, which ends April 14th, 2013, costs $599. After that date, the registration fee is $699. Register now at our registration page <http://www.eventbrite.com/event/2717332615>. Early Bird hotel registration ends December 31st, 2012 and saves $20 per night. Please reserve your room using the Aspen Meadows online reservation system <https://resweb.passkey.com/go/cplusplusnow2013> Speakers If you are interested in presenting, we are currently accepting proposals <http://cppnow.org/2013-call-for-submissions/>. Registration fee is waived for one speaker of every standard session presentation. Shorter sessions are prorated. Student/Volunteers Registration fees will be waived for a limited number of individuals that wish to attend as volunteers. Volunteer work consists of helping to run the conference and will not prevent volunteers from attending sessions. This is the first year this opportunity is being offered. If you are interested in applying to attend as a volunteer, contact us at <organizers(a)cppnow.org>. Sponsors For a copy of the conference Sponsorship Prospectus contact sponsorship(a)cppnow.org. C++Now is presented by Boost in-cooperation with ACM. Permanent link for this announcement is: http://cppnow.org/2013-registration-announcement/

1 0

Using c++11 features in clang
by Marshall Clow 10 Dec '12

10 Dec '12

In response to a some questions on the boost-users list (and boost bug reports), I wrote up this: http://marshall.calepin.co/llvmclang-and-standard-libraries-on-mac-os-x.html I don't know if this should be a FAQ entry for Boost, or for clang. Suggestions/comments/edits welcome. -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki

3 3

[hash] Tests fail on Intel compiler
by Andrey Semashev 10 Dec '12

10 Dec '12

Hi, I've been looking through Boost.Atomic and Boost.Thread tests on the "lazy piranha fedora 17 64" tester, intel-linux-13.0.1 compiler. The tests fail because Boost.Thread does not compile because of Boost.Hash. Here's an example of build log: http://www.boost.org/development/tests/trunk/developer/output/lazy%20piranh… The problem is that apparently BOOST_HASH_CONFORMANT_FLOATS is not defined on this compiler while there are both ::fpclassify and std::fpclassify functions. Are there valid reasons for not defining the macro on this compiler?

2 1

[trac] Add new components
by Michel Morin 10 Dec '12

10 Dec '12

The following four libraries do not have "components" in trac (lockfree already has the component in trac): - atomic - coroutine - multiprecision - odeint (numeric/odeint) Regards, Michel

4 4

[algorithm][hex] function hex_char_to_int in unnamed namespace in header file
by Felipe Magno de Almeida 10 Dec '12

10 Dec '12

Hello, AFAIK, unnamed namespaces are dangerous in headers. There is a commentary just above the function definition: // this needs to be in an un-named namespace because it is not a template // and might get included in several compilation units. This could cause // multiple definition errors at link time. But it seems the better thing would be to define it inline. It is exactly because it can be used in several translation units that it can cause an ODR violation if defined in a unnamed namespace AFAIK. Regards, -- Felipe Magno de Almeida

3 8

Boost new library policy
by islam y. yasar 10 Dec '12

10 Dec '12

Hi Boost Developers; i and my friend want to develope a library for boost. Is there any policy document for that ? i want to learn this process step by step. thank you.

6 9

[boost::asio] SCTP support with boost::asio
by Ajay Yadav 10 Dec '12

10 Dec '12

Hi, I am newbie to the boost library. I would like to develop the SCTP client-server application. Is boost::asio supported SCTP. Please guide me how I can make the application using SCTP. Regards, Ajay Yadav DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . -----------------------------------------------------------------------------------------------------------------------

2 1

[quickbook] template vs block vs phrase issues
by Andreas Pokorny 09 Dec '12

09 Dec '12

Hi, I use quickbook to write software design documentation targeting pdf. We now introduce a requirements tracking system that includes both source code and design documents. To describe or refer to requirements in docbook docments special xml markup is needed. I.e. something like <reqfooo><status>approved</status><version>1</version><id>DoOnlyNeededStuff</id><description></description></regfoo>. Since I do not want to write XML I added quickbook templates: [template reqfoo[id contents]'''<reqcfoo><id>'''[id]'''</id>'''[contents]'''</reqfoo>'''] [template sdesc[contents]'''<shortdesc>'''[contents]'''</shortdesc>'''] [template verification[contents]'''<verifycrit>'''[contents]'''</verifycrit>'''] [template source[contents]'''<source>'''[contents]'''</source>'''] [template usecase[contents]'''<usecase>'''[contents]'''</usecase>'''] [template status[contents]'''<status>'''[contents]'''</status>'''] [template version[contents]'''<version>'''[contents]'''</version>'''] and finally: [template desc[contents]'''<description>'''[contents] '''</description>'''] Now I want to use block elements inside the contents parameter of desc. Is there any way to achieve that? The only thing I can think of is: [template desc[]'''<description>'''] [template enddesc[]'''</description>'''] But then quickbook is just as good as xml! I tried to make desc a block level template by adding a line break at different positions, but then I get broken xml code, since para tags are spread around <description> regards Andreas

2 5

[Git] Modularizing Boost libraries with sublibs
by Daniel Pfeifer 09 Dec '12

09 Dec '12

While adding Boost.ODEint to the modularization manifest, I realized some inconsistencies about sublibs. The directories in "libs" usually contain one library each. In this case, we move the content to a dedicated Git repository. Some directories however (algorithm, numeric) host multiple libraries. How should we treat them? Move each one to a dedicated Git repository, or leave them grouped together? What's currently inconsistent, is that "numeric" is split into individual repositories, while "algorithm" is not. Further, I saw that the Git submodules of numeric's sublibraries are generated in "libs" rather than "libs/numeric", which is wrong. However, before I fix it, we need to decide whether these individual submodules should be individual or not. Opinions? Cheers, Daniel

4 5

Re: [boost] [Git] tools/wave missing (was: Documentation for Git and Modular Boost conversion)
by Hartmut Kaiser 09 Dec '12

09 Dec '12

> On Fri, Dec 7, 2012 at 3:42 PM, Eric Niebler <eric(a)boostpro.com> wrote: > > On 12/7/2012 11:44 AM, Oliver Kowalke wrote: > > >> Do I have to clone an additional submodule (which is not mentioned in > >> the docu)? > > > > Beman's docs appear to lack instructions for how to clone the > > super-project and initialize the sub-modules. That would be a nice > > addition. I don't know the steps and can't find them ATM, but I know > > it's documented *somewhere*. Beman? > > Just added: https://svn.boost.org/trac/boost/wiki/TryModBoost > > The original instructions were buried in a C++Now presentation slide. When I follow those steps as far as I can see everything looks fine except for tools/wave, which is missing. Is that intentional? Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu > > Thanks, > > --Beman > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

2 2

[Smart Pointers]
by Rahul Sr 09 Dec '12

09 Dec '12

Hi All, This is my first post though so please bear with my sentences. I have used scoped_ptr but this is too tied with new/delete semantics i.e. can't use it with pointers which gets allocated from specialized memory area. class AManager { public: A * allocate(); void deallocate(A * p); }; class A { ..... }; This specially happens when I use scoped pointer for C like pointers/allocator: Can I modify scoped pointer to have release semantics which is user defined: template<typename T> class DefaultReleasePolicy { static void releaseA(T * p) { delete p; } }; class ReleaseAPolicy { static void releaseA(A * p) { AManager::getInstance()->deallocate(p); } }; template<typename T,typemame ReleasePolicy = DefaultReleasePolicy<T> > class ScopedPtrModified { ~ScopedPtrModified() { ReleasePolicy::release(m_ptr); } }; Is this fine? Let me know your thoughts. Regards, Rahul

3 3

[odeint] Request to merge odeint into release branch
by Karsten Ahnert 09 Dec '12

09 Dec '12

I would like to ask for permission to merge odeint into the release branch. There are currently four failures in the regression tests. Two have already been fixed. The other two originate from the build time out of 180 seconds. These two tests will often require longer build times, since they heavily use Boost.Fusion, Boost.Units and Boost.MPL.

2 5

[multiprecision] Request permision to merge to release.
by John Maddock 09 Dec '12

09 Dec '12

I'd like to ask permission to merge the multiprecision lib to release. Note that as things stand I'm still chasing down test failures, but these are now mostly down to: * Things that work locally, but the testers haven't cycled yet. * 300s timeouts - mostly from the intel compiler :-( Aside: in an effort to reduce the number of timeouts, I've basically gutted some of the tests when the compiler is Intel, and I think I have all the build times under 20s on my Linux box, yet I'm still getting 300s timeouts on some tester machines, either those machines are seriously underpowered or I'm missing something here :-( Cheers, John.

3 5

[smart ptr] [shared] suggestion: single pointer in object returned from make_shared
by Julian Gonggrijp 09 Dec '12

09 Dec '12

Dear Smart Ptr maintainer(s), I recently learned that boost::make_shared allocates the space for the pointee and the reference counter in one go. It makes a lot of sense, and I might have suggested it if it wasn't already the case. Now I'm assuming that a shared_ptr stores two raw pointers internally, one to the pointee and one to the counter. I guess that would be necessary in the "normal" case where the pointee and the counter are allocated separately. Now in the case where the shared_ptr is created by make_shared, ideally you'd need to store only one raw pointer because pointee and counter reside in the same memory object. That would be the finishing touch to a nonintrusive smart pointer that really performs like an intrusive one. To me such a thing seems highly desirable. I realise this would require a new implementation of the shared pointer. Could this somehow be made to cooperate or at least coexist with the old shared_pointer? Would it perhaps even be an option to deprecate the old shared_pointer in order to entirely replace it by the new version in the future? I'll be most interested to read your comments on this idea. -Julian

1 0

Boost.Test updates in trunk: need for (mini) review?
by Gennadiy Rozenal 09 Dec '12

09 Dec '12

Hi, It's been a long while since I merged any changes into boost release and by now there are whole bunch of new features there. Some are small, but some others are big ones such that they can change the way people use the library. I'd like to list them here (excluding bug fixes and removal of deprecated interfaces) and ask what should we do with these. Specifically let me know if you think these require some kind of (mini) review from community, but any other comments are welcome as well. So here we go: I. New testing tool BOOST_CHECKA This tool is based on excellent idea from Kevlin Henney. I chose the name CHECKA for this tool due to the lack of better name, but I am open to suggestions. This testing tool capable of replacing whole bunch of existing other tools like BOOST_CHECK_EQUAL, BOOST_CHECK_GT etc. Usage is the most natural you can wish for: BOOST_CHECKA( var1 - var2 >= 12 ); And the output will include as much information as we can get: error: in "foo": check var1 - var2 >= 12 failed [23-15<12] II. New "data driven test case" subsystem New data driven test case subsystem represent a generalization of parameterized test case and test case template and eventually will replace both. The idea is to allow user to specify an arbitrary (monomorphic or polymorphic) set of samples and run a test case on each of the samples. Samples can have different arity, thus you can have test cases with multiple parameters of different types. For now we support following dataset kinds (aside of generators none of dataset constructions routines performs *any* copying): a) singleton - dataset constructed out of single sample data::make(10) - singleton dataset with integer sample data::make("qwerty") - singleton dataset with string sample b) array - dataset constructed out of C array int a[] = {1,2,3,4,5,6}; data::make(a) - dataset with 6 integer values c) collection - dataset constructed out of C++ forward iterable collection std::vector<double> v{1.2, 2.3, 3.4, 5.6 }; data::make(v) - dataset with 6 double values d) join - dataset constructed by joining 2 datasets of the same type int a[] = {1,2,3}; int b[] = {7,8,9}; data::make(a) + data::make(b) - dataset with 6 integer values e) zip - dataset constructed by zipping 2 datasets of the same size, but not necessarily the same type This dataset has an arity which is sum of argument dataset arities. int a[] = {1,2,3}; char* b[] = {"qwe", "asd", "zxc"}; data::make(a) ^ data::make(b) dataset with 3 samples which are pairs of int and char*. f) grid - dataset constructed by "multiplying" 2 datasets of the same different sizes and types type This dataset has an arity which is sum of argument dataset arities. int a[] = {1,2,3}; char* b[] = {"qwe", "asd"}; double c[] = {1.1, 2.2}; data::make(a) * data::make(b) * data::make(c) dataset with 12 samples which are tuples of int and char* and double. g) xrange generator dataset which produes samples in some range data::xrange( 0., 3., 0.4 ) - dataset with 8 double samples data::xrange<int>((data::begin=9, data::end=15)) - dataset with 6 int samples data::xrange( 1., 7.5 ) - dataset with 7 double samples data::xrange( 5, 0, -1 ) - dataset with 5 int samples h) random - generator dataset with unlimited number of random samples data::random(data::distribution = std::normal_distribution<>(5.,2)) dataset with random double numbers following specified distribution data::random(( data::engine = std::minstd_rand(), data::distribution = std::discrete_distribution<>(), data::seed = 20UL )); dataset with random int numbers following specified distribution While all this interfaces can be used by itself to build complex datasets with various purposes, primary use case it was developped for is new data driven test case interface: BOOST_DATA_TEST_CASE( test_name, dataset, parameter_names... ) Here are couple examples: int samples1[] = {1,2,3}; BOOST_DATA_TEST_CASE( t1, samples1, sample ) { BOOST_CHECKA( foo(sample) > 0 ); } Above test case is going to be executed 3 times with different sample values char* strs[] = {"qwe", "asd", "zxc", "mkl" }; BOOST_DATA_TEST_CASE( t1, data::xrange(4) ^ strs ^ data::random(), intval, str, dblval ) { MyObj obj( dblval, str ); BOOST_CHECKA( obj.goo() == intval ); } Above test case will be executed 4 times with different values of parameters intval, str, and dblval. Polymorphic datasets are still being developed, but should appear soon(ish). III. Auto-registered test unit decorators. Previously is was not possible and/or convenient to assign attributes to the automatically registered test units. To alleviate this I've introduced a notion of test unit decorator. These can be "attached" to any test unit similarly to like it is done in other languages Following decorators already implemented: label - adds labels to a test unit expected_failures - set expected failures for a test unit timeout - sets timeout for a test unit description - sets a test unit description depends_on - sets a test unit dependency enable_if/disable_if - facilitates a test unit status change fixture - assigns fixture to a test units Test unit description is new test unit attribute, which is reported by new list_content command line argument described below. Usage of labels covered below as well. enable_if/disable_if allow new, much more flexible test management. By adding enable_if/disable_if decorators to the test unit you can conditionally select which test units to run at construction time based on some compile time or run-time parameters. And we finally we have suite level fixtures which are set by attaching fixture decorator to a test suite (suite level fixtures executed once per test suite). Attachment of decorator is facilitated by using of BOOST_TEST_DECORATOR. Note that you can use any of '+', '-', '*' symbols to attach decorator (and any number of '*'): BOOST_TEST_DECORATOR( + unittest::fixture<suite_fixture>() ) BOOST_AUTO_TEST_SUITE( my_suite1 ) { } BOOST_TEST_DECORATOR( - unittest::timeout( 100 ) - unittest::expected_failures( 1 ) - unittest::enable_if( 100 < 50 ) ) BOOST_AUTO_TEST_CASE( my_test5 ) BOOST_TEST_DECORATOR( **** unittest::label( "L3" ) **** unittest::description( "suite description" ) **** unittest::depends_on( "my_suite2/my_test7" ) ) BOOST_AUTO_TEST_CASE( my_test11 ) IV Support for "run by label" plus more improvements for filtered runs Previously you only had an ability to filter test unit to execute by name. Now you can attach labels to test units and create collections to run which are located in arbitrary positions in test tree. For example you can have special label for performance test cases, which is attached to all test units which are responsible for testing performance of your various components. Or you might want to collect exception safety tests etc. To filter test units by level you still use --run_test CLA. Labels are dented by @prefix: test.exe --run=@performance You can now repeat --run_test argument to specify multiple conditions: test.exe --run=@performance,@exception_safety --run=prod/subsystem2 In addition run by name/label now recognizes dependencies. So if test unit A depends on test unit B and test unit B is disabled/is not part of current run test unit A will not run as well. Finally you now have an ability to specify "negative" conditions, by prefixing name or label with ! test.exe --run=!@performance This will run all test units which are not labeled with "performance". V. Support for failure context In many scenarios it is desirable to specify an additional information to a failure, but you do not need to see it if run is successful. Thus using regular print statements is undesirable. This becomes especially important when you develop common routine, which performs your testing and invoke it from multiple test units. In this case failure location is no help at all. To alleviate this problem two new tools are introduced: BOOST_TEST_INFO BOOST_TEST_CONTEXT BOOST_TEST_INFO attaches context to next assertion which is executed. For example: BOOST_TEST_INFO( "a=" << a ); BOOST_CHECKA( foo(a) == 0 ); BOOST_CHECK_CONTEXT attaches context to all assertions within a scope: BOOST_CHECK_CONTEXT( "Starting test foo from subset " << ss ) { BOOST_CHECKA( foo(ss, a) == 1 ); BOOST_CHECKA( foo(ss, b) == 2 ); } VI. Two new command line arguments: list_context, wait_for_debugger Using list_context you can see a full or partial test tree of your test module. wait_for_debugger allows to force test module to wait till you attach debugger. VII. Colored output. Using new CLA --color_output you can turn on colored output for error and information messages VIII New production testing tools interface introduced This feature was covered in details in my presentation in BoostCon 2010. The gist if this is an ability to use Boost.Test testing tools interfaces in production (nothing to do with testing) code. User supplied implementation is plugged in IX. Number of smaller improvements: * Notion of framework shutdown. Allows to eliminate some fake memory leaks * Added checkpoints at fixture entry points, test case entry point and test case exit point for auto registered test cases * New FPE portable interfaces introduced and FPE handling is separated from system errors handling. You can detect FPE even if catch_system_error is false * Added an ability to erase registered exception translator * execution_monitor: new interface vexecute - to be used to monitor nullary functions with no result values * test_tree_visitor interface extended to facilitate visitors applying the same action to all test units * execution_monitor use typeid to report "real" exception type if possible. * New ability to redirect leaks report into a file Thank you for your time, Gennadiy

21 66

[config] Macro for null pointer
by Edward Diener 08 Dec '12

08 Dec '12

I have found something like this to be helpful, when working with multiple compilers: #include <boost/config.hpp> #if defined(BOOST_NO_NULLPTR) #define BOOST_XXX_NULLPTR 0 #else #define BOOST_XXX_NULLPTR nullptr #endif where XXX is some local name for my own use. And then use BOOST_XXX_NULLPTR in places where a null pointer is needed. Would this be a candidate for a BOOST_NULLPTR macro in the config library instead ? Edward Diener

16 63

Re: [boost] [boost-steering] Re: [Git] Documentation for Git and Modular Boost conversion
by Brian Wood 08 Dec '12

08 Dec '12

Dave Abrahams: > Boost is making this transition. It *will* cause some disruption. It > will also make things easier for some people. I'm glad to hear this effort is continuing. > IMO we should not burden this move, which is supposed to > make it easier and more efficient overall for Boost to operate, > with any unnecessary obligations. That sounds harsh, but I guess that's the way the cookie crumbles. -- Brian Wood Ebenezer Enterprises -- so far G-d has helped us. http://webEbenezer.net

1 0

[serialization] Proposal: make 'version' trait (and others) enable_if-friendly
by Gabriel Redner 07 Dec '12

07 Dec '12

I have recently run up against a limitation of the serialization library in terms of specializing the 'version' trait. Fortunately, I believe the issue has a simple workaround which I don't believe will break existing code. In general, one can change the version of a serialized class by specializing the 'version' template class: ============================== template <typename T> struct version { BOOST_STATIC_CONSTANT(unsigned int, value = 0); }; ... template <> struct version<MyType> { BOOST_STATIC_CONSTANT(unsigned int, value = 1); }; ============================== However, this approach does not work if 'MyType' is of the form (see [1]): ============================== template <typename T> struct Foo { struct MyType { int data1; }; }; template <typename T> struct version<Foo<T>::MyType> // ERROR { BOOST_STATIC_CONSTANT(unsigned int, value = 1); }; ============================== It's not possible for the compiler to deduce the enclosing type, so this doesn't work. However, if MyType can be identified by a metafunction, then I can use enable_if to select the specialization of 'version' that I want. However, this requires support from 'version' itself: ============================== template <typename T, typename Enable = void> // NOTE new template parameter struct version { BOOST_STATIC_CONSTANT(unsigned int, value = 0); }; ... template <typaneme T> struct version<MyType, typename boost::enable_if<is_mytype<T> >::type> { BOOST_STATIC_CONSTANT(unsigned int, value = 1); }; ============================== So, my proposal is simply to add this extra template parameter to 'version'. I do not believe other uses of 'version' will be affected, but it would not surprise me if I've overlooked something. Presumably the same modification could be made to implementation_level etc. A patch (for 'version' only) against trunk is enclosed below. Comments are welcome! Thanks, -Gabe [1] http://boost.2283326.n4.nabble.com/serialization-versioning-for-class-neste… =================================================================== --- version.hpp (revision 81723) +++ version.hpp (working copy) @@ -32,7 +32,7 @@ // default version number is 0. Override with higher version // when class definition changes. -template<class T> +template<class T, class Enable=void> struct version { template<class U> @@ -53,8 +53,8 @@ }; #ifndef BOOST_NO_INCLASS_MEMBER_INITIALIZATION -template<class T> -const int version<T>::value; +template<class T, class Enable> +const int version<T, Enable>::value; #endif } // namespace serialization ===================================================================

5 12

Inspect Report
by Daniel James 07 Dec '12

07 Dec '12

Hi, The snapshot builds and inspect results haven't been running for some time, so I've added running the inspect script to the documentation build for more up to date results. You can see them at: http://boost.cowic.de/rc/docs-inspect-trunk.html http://boost.cowic.de/rc/docs-inspect-release.html These are generated after building documentation, which is not exactly the same as the final release, but it's close. Daniel

4 10

[context] asm_context_sources breaking regression testing for WinCE
by David Deakins 07 Dec '12

07 Dec '12

Hi Oliver, I finally got a little bit of time to investigate recent strange behavior on the VeecoFTC regression tester and found that the build jamfile for the context library is halting Boost.Build during the regression tests. It appears that, when it can't find an appropriate architecture to use, it actually generates an argument error in try-one-generator-really. I attached the output of the bjam.log and perhaps it will be useful for investigating. Let me know if you would like me to try anything. Thanks, -Dave

2 12

[iterator] UB when implicitly using default constructed counting_iterator<unsigned>
by Peter Sommerlad 07 Dec '12

07 Dec '12

Hi Jeffrey, hi all, I believe the usability of counting iterator could be improved, by value-initializing its Iterator type in the default constructor, because integral types won't be initialized by its default constructor. This can lead to hard to recognize user errors, e.g., when wrapping such a counting iterator with a filter iterator. counting_iterator is special in that sense, because to my understanding it is intended to adapt integral types to become iterators. And a default initialized scalar type, isn't. I suggest a one line change: counting_iterator() { } should become counting_iterator() : super_t(Incrementable()) { } The following example program shows the interesting UB, because the 3rd argument of make_filter_iterator, default constructs a counting_iterator<unsigned>(). Any thoughts? Objections? Teachings... Regards Peter. =====>8 #include <iostream> #include <boost/iterator/filter_iterator.hpp> #include <boost/iterator/counting_iterator.hpp> #include <algorithm> #include <iterator> #include <functional> struct is_prime{ bool operator()(unsigned int val) const { if (val < 2) return false; using std::placeholders::_1; auto ce=boost::make_counting_iterator(val); return ce==std::find_if_not(boost::make_counting_iterator(2u),ce, bind(std::modulus<unsigned>{},val,_1)); } }; int main(){ std::copy_n(boost::make_filter_iterator(is_prime{},boost::make_counting_iterator(1u) // if the following line is omitted we have undefined behavior, because of uninitialized unsigned value // ,boost::make_counting_iterator(std::numeric_limits<unsigned>::max()) // must be different from above value ),40,std::ostream_iterator<unsigned>{std::cout,", "}); } =====8< -- Prof. Peter Sommerlad Institut für Software: Bessere Software - Einfach, Schneller! HSR Hochschule für Technik Rapperswil Oberseestr 10, Postfach 1475, CH-8640 Rapperswil http://ifs.hsr.ch http://cute-test.com http://linticator.com http://includator.com tel:+41 55 222 49 84 == mobile:+41 79 432 23 32 fax:+41 55 222 46 29 == mailto:peter.sommerlad@hsr.ch

3 2

[coroutine] permission to merge to boost-release?
by Oliver Kowalke 07 Dec '12

07 Dec '12

Hello, because the merge window for new libraries is closed on Monday I'd like to ask for permission to merge boost.coroutine into boost-release. regards, Oliver

2 2