December 2012 - 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

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

Arguing about names in Boost libraries
by Edward Diener 06 May '15

06 May '15

What is wrong with the people commenting on libraries for Boost who are so concerned about the names being used ? We are talking only about C++ identifiers and yet there are now endless discussions where people disagree on names or argue that some name is not what they want or that they like some other name, with a list of names that they find adequate. This is irrelevant. There is something mentally wrong about all those peoples spending endless amounts of time around this issue. I notice this does not happen nowadays for just one library but for ever single library, or proposed library, which is mentioned on this mailing list. Is this the way all of you people actually work in your daily jobs, or on your own projects, spending hours and days arguing with others about C++ identifiers for every little thing ? Are you not aware of the absurdity of your endless remarks ? Grow up ! Surely there are better things to do than carry on endlessly about some name, that is should be x or y or z or some other inane preferable list. It's time for somebody to say this, so I will do it. A C++ identifier name, as long as it is vaguely about what the functionality entails, is perfectly adequate. It does not have to satisfy everyone in the universe. Period !

9 10

IDE for developing Boost
by Jens Müller 20 Dec '14

20 Dec '14

Hi, I am looking for recommendations for developing Boost, especially code in the graph library. At work, most developers (not for Boost, for some commercial software), most developers are using Eclipse. This works quite fine as soon as it has properly auto-discovered include paths etc. But before fiddling around with Eclipse to get all the settings right, I'd wanted to to ask for your recommendations. And maybe there are already settings available to make it "just work", at least initially. Cheers, Jens

16 22

Why no non-null smart pointers?
by Ross MacGregor 29 Apr '14

29 Apr '14

I just created a very small smart pointer libary for our project. It will contain two types of shared pointers: SharedHandle and NullableSharedHandle. SharedHandle will be a shared pointer that cannot be null by ensuring a non-null construction while NullableSharedHandle will basically be a typedef for boost::shared_ptr. I firmly believe that code can be made more reliable by minimizing the use of nullable pointers. To this end, I think it is important that we start using non-null pointer types. Ideally the compiler would be able to understand a non-null pointer and catch bugs at compile time, but I think we can still improve things with a few runtime checks. If we make sure that a shared pointer is constructed with a non-null pointer and ban any reset() type methods, we guarentee that it points to something. This can be beneficial for the following reasons: 1. Any function that uses this type will no longer be burdened with precondition checks to make sure variables of this type are not null. 2. It's type is simply more explicit and better explains its function. 3. Moving the non-null check to the creation phase will reduce the possibility of encountering null pointer exceptions at runtime (assuming there are many more pointer references than constructor calls). So my little pointer library seems to make a lot of sense, but if so why hasn't this simple smart pointer variation made it into boost yet? Has this been discussed somewhere already? My search on non-null smart pointers is not revealing much discussion on the topic. Regards, Ross

9 16

Interest in Base2/16/32/64 Encoding Library?
by Thomas Kemmer 27 Jan '14

27 Jan '14

Dear Boost Developers, I would like to know if there is interest in incorporating a generic Base2/16/32/64 encoding library into Boost. I am the author of such a libray, hosted at http://code.google.com/p/stlencoders/ and would be willing to contribute and make the effort of "Boostifying" it, if the Boost community is interested in such a thing. There have been several suggestions for a Base64 encoding library on this mailing list in the past. Most of them have been dismissed, since Boost already provides a Base64 implementation with Boost.Serialization's "Dataflow Iterators". Though I appreciate the dataflow iterator's design, from personal experience I think that for the basic task of encoding/decoding, a higher-level interface, e.g. one that takes padding and intermittent whitespace (MIME) into account, would benefit many developers. Currently, the stlencoders library - implements the Base16, Base32 and Base64 encoding schemes as defined in RFC 4648. Base2, i.e. binary encoding, is also supported. - implements encoding and decoding operations as generic algorithms that operate on STL-style iterators - supports different encoding alphabets using custom traits classes - supports different character types - lets the user define if/which non-alphabet characters should be ignored via predicates - provides reasonable performance that matches most "plain C" implementations stlencoders is currently designed as a stand-alone library with no dependencies on Boost (or anything but C++03); it would therefore take some effort and guidance from the community to properly integrate it with the rest of Boost. I would therefore appreciate any feedback regarding your interest in this. Kind Regards, Thomas

7 11

[mpl] integral_c [type_traits] integral_constant limits
by vicente.botet 21 Oct '13

21 Oct '13

Hi, I was testing Boost.Ratio with gcc-4.6 c++0x and I get some compile errors when instantiating std::cout << boost::mpl::integral_c< boost::intmax_t, boost::integer_traits<boost::intmax_t>::const_max >::value ; ..\..\..\../boost/mpl/aux_/integral_wrapper.hpp: In instantiation of 'mpl_::integral_c<long long int, 0x7fffffffffffffffll>': ratio_io\ratio_io.pass.cpp:24:6: instantiated from here ..\..\..\../boost/mpl/aux_/integral_wrapper.hpp:72:96: warning: integer overflow in expression [-Woverflow] ..\..\..\../boost/mpl/aux_/integral_wrapper.hpp:72:96: error: '-0x8000000000000000ll' is not a valid template argument for type 'long long int' because it is a non-constant expression ..\..\..\../boost/mpl/aux_/integral_wrapper.hpp:72:96: error: '-0x8000000000000000ll' is not a constant expression integral_wrapper.hpp:72 contains typedef AUX_WRAPPER_INST( BOOST_MPL_AUX_STATIC_CAST(AUX_WRAPPER_VALUE_TYPE, (value + 1)) ) next; The same line pass with gcc-4.6, gcc-4.5 and gcc-4.5 c++0x with just a warning. ..\..\..\../boost/mpl/aux_/integral_wrapper.hpp: In instantiation of 'mpl_::integral_c<long long int, 0x7fffffffffffffffll>': ratio_io\ratio_io.pass.cpp:23:6: instantiated from here ..\..\..\../boost/mpl/aux_/integral_wrapper.hpp:72:96: warning: integer overflow in expression [-Woverflow] integral_c is by integral_constant, but integral_constant doesn't needs next a prior types. This means that with the current implementation we can not use integral_constant with the max value of the type. Do you think this is a bug in integral_constant? Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

4 6

[scope_exit] D-style scope(failure) and scope(success) in C++
by Evgeny Panasyuk 30 Sep '13

30 Sep '13

Hello all, D language has scope(exit), scope(success) and scope(failure) features - http://dlang.org/statement.html#ScopeGuardStatement : "... scope(exit) executes NonEmptyOrScopeBlockStatement when the scope exits normally or when it exits due to exception unwinding. scope(failure) executes NonEmptyOrScopeBlockStatement when the scope exits due to exception unwinding. scope(success) executes NonEmptyOrScopeBlockStatement when the scope exits normally. ..." Andrei Alexandrescu describes some of uses cases for scope(exit), scope(success), scope(failure) at his recent talk : http://channel9.msdn.com/Events/Lang-NEXT/Lang-NEXT-2012/Three-Unlikely-Suc… There is Boost.ScopeExit library which emulates D's scope(exit) via BOOST_SCOPE_EXIT macro, but there are no analogues for D's scope(failure) and scope(success). Current alternative for these features is ScopeGuard idiom ( http://en.wikibooks.org/wiki/More_C%2B%2B_Idioms/Scope_Guard , http://www.drdobbs.com/cpp/generic-change-the-way-you-write-excepti/1844037… ). Boost.ScopeExit library itself suggests to use ScopeGuard - http://www.boost.org/doc/libs/1_51_0/libs/scope_exit/doc/html/scope_exit/al… : " Boost.ScopeExit is similar to scope(exit) feature built into the D programming language. A curious reader may notice that the library does not implement scope(success) and scope(failure) of the D language. Unfortunately, these are not possible in C++ because failure or success conditions cannot be determined by calling std::uncaught_exception (see Guru of the Week #47 for details about std::uncaught_exception and if it has any good use at all). However, this is not a big problem because these two D's constructs can be expressed in terms of scope(exit) and a bool commit variable (similarly to some examples presented in the Tutorial section). " I have made small library ( https://github.com/panaseleus/stack_unwinding#d-style-scope-guardsactions ) which supplies primitives (class unwinding_indicator, UNWINDING_AWARE_DESTRUCTOR macro) to determining when object destructor is called due to stack-unwinding or due to normal scope leaving. Currently it is implemented on top of platform-specific implementation of uncaught_exception_count function and tested on: {MSVC2005, MSVC2008, MSVC2010, MSVC2012, GCC4.1.2, GCC4.4.6, Clang3.2}x{x32, x64}x{default settings}. uncaught_exception_count is a function similar to std::uncaught_exception from standard library, but instead of boolean result it returns unsigned int showing current count of uncaught exceptions. Such primitives allow us to implement scope(success) and scope(failure) features in C++. I have made several proof-of-concepts: * https://github.com/panaseleus/stack_unwinding/blob/master/examples/scope_ac… * https://github.com/panaseleus/stack_unwinding/blob/master/examples/example_… * https://github.com/panaseleus/stack_unwinding/blob/master/examples/scope_gu… * https://github.com/panaseleus/stack_unwinding/blob/master/examples/boost_sc… boost_scopes.cpp example shows usage of BOOST_SCOPE_FAILURE and BOOST_SCOPE_SUCCESS: try { cout << "Case #1: stack unwinding" << endl; BOOST_SCOPE_EXIT(void) { cout << "exit" << endl; } BOOST_SCOPE_EXIT_END BOOST_SCOPE_FAILURE(void) { cout << "failure" << endl; } BOOST_SCOPE_FAILURE_END BOOST_SCOPE_SUCCESS(void) { cout << "success" << endl; } BOOST_SCOPE_SUCCESS_END throw 1; } catch(int){} { cout << "Case #2: normal exit" << endl; BOOST_SCOPE_EXIT(void) { cout << "exit" << endl; } BOOST_SCOPE_EXIT_END BOOST_SCOPE_FAILURE(void) { cout << "failure" << endl; } BOOST_SCOPE_FAILURE_END BOOST_SCOPE_SUCCESS(void) { cout << "success" << endl; } BOOST_SCOPE_SUCCESS_END } Output is: " Case #1: stack unwinding failure exit Case #2: normal exit success exit " Currently BOOST_SCOPE_FAILURE and BOOST_SCOPE_SUCCESS are implemented based on boost_1_51_0/boost/scope_exit.hpp by copy-paste and replace (just for proof-or-concept, of course it is possible solution with much less duplication). Semantically meaningful changes can be viewed as diff at https://github.com/panaseleus/stack_unwinding/commit/d5513404323490ea99d9b6… Before posting here, I made posts on several C++ forums, but unfortunately get only a few feedbacks regarding ScopeFailure and ScopeSuccess. What do you think? Thank you. P.S. Related discussion: http://lists.boost.org/Archives/boost/2010/09/171051.php Best Regards, Evgeny Panasyuk

6 27

[asio] Randomly having problems reading from the socket
by Torben Wiggerich 29 Jul '13

29 Jul '13

Hi all, I have some problems using the boost.asio.read for a TCP-socket. So far it works fine, but it randomly stops the transfer for at least 5 seconds. To resolve the error I used a simple synchronous server and client from the boost examples and modified it too send a larger amount of data. (307400 Bytes; this size comes from the program I'm trying to get run). On the client side I also changed the reading from the socket to read the complete data with boost.asio.read and transfer_all as argument. Both, server and client, measure the time for sending and reading to the socket and will give an error if it needs more than 1 second. Here is the sourcecode for the server: #include <iostream> #include <string> #include <boost/asio.hpp> #include <boost/date_time/posix_time/posix_time.hpp> using boost::asio::ip::tcp; using namespace boost::posix_time; int main() { try { boost::asio::io_service io_service; tcp::acceptor acceptor(io_service, tcp::endpoint(tcp::v4(), 8002)); tcp::socket socket(io_service); acceptor.accept(socket); unsigned char * array = new unsigned char[307400]; for (;;) { boost::system::error_code ignored_error; ptime startTime = microsec_clock::universal_time(); boost::asio::write(socket, boost::asio::buffer( array, 307400 ), boost::asio::transfer_all(), ignored_error); time_duration neededTime = microsec_clock::universal_time() - startTime; if ( neededTime.total_milliseconds() > 1000 ) { std::cout << "ERROR needed too much time: " << neededTime.total_milliseconds() << "ms" << std::endl; } } } catch (std::exception& e) { std::cerr << e.what() << std::endl; } return 0; } My client sourcecode: #include <iostream> #include <boost/array.hpp> #include <boost/asio.hpp> #include <boost/date_time/posix_time/posix_time.hpp> using boost::asio::ip::tcp; using namespace boost::posix_time; int main(int argc, char* argv[]) { try { if (argc != 2) { std::cerr << "Usage: client <host>" << std::endl; return 1; } boost::asio::io_service io_service; boost::asio::ip::tcp::endpoint endpoint( boost::asio::ip::address::from_string( argv[1] ), 8002 ); tcp::socket socket(io_service); boost::system::error_code error = boost::asio::error::host_not_found; socket.connect( endpoint, error ); if (error) throw boost::system::system_error(error); int counter = 0; unsigned char* array = new unsigned char[307400]; for (;;) { boost::system::error_code error; ptime startTime = microsec_clock::universal_time(); size_t len = boost::asio::read( socket, boost::asio::buffer( array, 307400 ), boost::asio::transfer_all(), error ); time_duration neededTime = microsec_clock::universal_time() - startTime; if ( error ) { printf( "body read error %s\n", error.message().c_str() ); } if ( counter % 5000 == 0 ) { std::cout << "passed: " << counter << "\r"; } ++counter; if ( neededTime.total_milliseconds() > 1000 ) { std::cout << "ERROR needed too much time: " << neededTime.total_milliseconds() << "ms" << std::endl; } } } catch (std::exception& e) { std::cerr << e.what() << std::endl; } return 0; } To reproduce the error just let it run for a while. It can take up to 30 minutes or even more... After a while it will produce the line: "ERROR needed too much time: 5007ms". Maybe with slightly different times, but all around 5 seconds. I tested it on different machines with Windows Vista and Seven. So am I'm doing sth. wrong? Is the reading from the socket correct? I'm using boost version 1.44. Kind regards Torben Wiggerich

6 11

A more convenient Variant visitation syntax
by Kevin Wu Won 19 Jul '13

19 Jul '13

While Boost Variant is a wonderful library that fills a genuine hole in the C++ language, it is not as nice to use as it could be. The "correct" way to unwrap a variant is to apply a static visitor, but this method carries a high syntactic burden because it needs the user to define a class (probably somewhere far away) just so they can "switch" on the type of the object stored in the variant. I came up with a solution where the handler functions can be specified inline with C++11 lambdas. Here's an example: boost::variant< int, std::string > u("hello world"); int result = match(u, [](int i) -> int { return i; }, [](const std::string & str) -> int { return str.length(); }); The `match` function accepts the variant followed by the handler functions. The functions can be specified in any order. It will fail to compile if the functions do not match the types of the variant, if the return types are not all the same, or if a non-unary function is supplied. This is C++11 only because it's quite pointless without lambda functions. I've tested it with gcc 4.7. It doesn't work on gcc 4.6, which can't handle the variadic templates. Here's the code: https://github.com/exclipy/inline_variant_visitor What do you think? This started out for me as an exercise to learn template metaprogramming and C++11, but hopefully, it can actually evolve into something useful.

7 8

De Bruijn Bind (alternate bind syntax) Interest?
by David Sankel 24 Jun '13

24 Jun '13

Hello all, I've been working on an alternate bind syntax based on De Bruijn indices[1]. The syntax is very simple, yet the terms are very powerful. Here is an example of a function const that takes in an argument c and returns another function that, for all input, returns c: //λx.λy.x = λλ1 with De Bruijn indices. auto const_ = abs<1>( abs<1>( var<1,0>() ) ); More examples, further explanation, and an implementation are available here[2]. I'm thinking that this library could also be useful as a core for more syntax heavy bind variations. David [1] http://en.wikipedia.org/wiki/De_Bruijn_index [2] http://bitbucket.org/camior/de-bruijn-bind/ -- David Sankel Sankel Software www.sankelsoftware.com 585 617 4748 (Office)

11 73

[TypeErasure] references
by Chapman, Alec 10 May '13

10 May '13

Hi Steven, I have a somewhat-generic type erasure class that I would like to switch to yours. The main difficulty I can see is in the way capturing by reference is handled. The approach I take in my class is to pass a boost::reference_wrapper to the constructor: typedef mpl::vector<copy_constructible<>, type_id_<>, incrementable<> > requirements; int i = 0; any<requirements> x(boost::ref(i)); // capture i by reference ++x; // i == 1 any<requirements> y(x); // makes a copy of i ++y; // i == 1, any_cast<int>(y) == 2 My motivation is that I have a bunch of template functions already written that I often call directly, but in other cases I need to compile them separately by instantiating them with any<...>: ---------------------- module 1 ------------------------- // some long algorithm that I don't want to modify to be aware of any<...> template<class T> void f(T& t) { ++t; T t2 = t; ++t2; // do something with t2 } // make a type-erased version for separate compilation void any_f(any<requirements>& x) { return f(x); } -------------------- module 2 ---------------------------- // provide a thin wrapper that applies type erasure before calling any_f template<class T> void f_fwd(T& t) { any<requirements> x(boost::ref(t)); any_f(x); } // some function that needs to call f void g(int& i) { // do something with i... // then pass it to f f_fwd(i); } Is something like this possible with your method? Are there advantages that I'm not seeing to having the type signature contain information about whether the object is held by reference? Thanks, Alec

3 6

What Should we do About Boost.Test?
by Dave Abrahams 16 Apr '13

16 Apr '13

Hi All, I was just going through Boost.Test to try to figure out how to teach it, and while it looks to have substantial value, it is also in quite a mess. It contains loads of features that are exercised in the examples/ directory but neither included in any of the tests nor documented. There are facilities for command-line argument parsing! There are "decorators" that turn on/off features for test cases. There is support for mock objects! These are cool and sometimes necessary features, but who knew? The third tutorial page (http://www.boost.org/doc/libs/1_51_0/libs/test/doc/html/tutorials/new-year-…) has a glaring typo in the code examples: "BOOST_AUTO_EST_CASE". There's no reference manual at all. There are nearly-identical files in the examples/ directory called "est_example1.cpp" and "test_example1.cpp" (Did the "t" key on someone's keyboard break?) I could go on, but where would I stop? I don't know what to do about this. Because of the lack of redundancy (i.e. tests and documentation), it's hard to tell whether this library is correct or even to define what "correct" should mean. It seems like, as long as the code is incompletely / incorrectly documented and tested, it's just someone's personal coding project that we happen to keep shipping with Boost, and not really a library for general use. This situation reflects poorly on Boost as a whole and the fact that it centers around a _testing_ library, which is concerned with robustness... well, let's just say that the irony isn't lost on me. I don't mean this posting as an attack on Gennadiy in any way, but I think the situation is unacceptable and therefore am opening a discussion about what should happen. As a straw man, I'll make this suggestion: - Boost.Test is officially deprecated in the next release - Its documentation, such as it is, is removed from the release after that - Meanwhile, other tests in Boost that use this library are rewritten to use a different mechanism - The code is removed from Boost thereafter I am not at all attached to removing Boost.Test from Boost, but IMO rescuing it would require a significant new investment of time and energy from people who are committed to bringing the library up to par with the rest of what we do. (I seriously thought about volunteering for this myself, but realistically speaking, I don't have the time, and volunteering for something you can't actually do is worse than not volunteering at all.) Even if volunteers show up, I'd suggest proceeding with the plan above, subject to reversal at any time the work actually gets done. Thoughts? -- Dave Abrahams BoostPro Computing Software Development Training http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost

34 85

[fusion] What do we do with nil ?
by Joel de Guzman 31 Mar '13

31 Mar '13

Hello, This is a constantly nagging issue. There are a couple of places where nil is a PP define especially on the Mac: - objc.h #ifndef nil #define nil __DARWIN_NULL #endif and - MacTypes.h #ifndef nil #define nil NULL #endif So people complain because fusion uses nil as: namespace boost { namespace fusion { struct nil; }} So, nil is a reserved word in Objective-C. But this is C++! And that define is SUCH A BAD PRACTICE in C++! Some folks, like Paul Mensonides maintains a strong stance against this: I would just use #define nil nil as a sanity check and call it done. If the symbol is already defined, compilation error (or at least warning on overly permissive compilers). The symbol will be need to be undefined in between the inclusion of the two libraries. Workarounds like nil_ and (min)(...) just perpetuate the problem. Fix the root problem rather than treating the symptom indefinitely. Otherwise, where is the line drawn? Even if you can't provide a transparent fix (such as defining nil as a constant and min/max as functions), the backwards compatibility argument fails in the long run. The amount of effort required to make the necessary changes to existing code will eventually be outweighed by the effort to implement workarounds put into new code (as well as educate everyone that they are necessary)--especially in cases like these which can mostly be emulated in a way that causes most existing code to work. As I said over and over again, I'm listening and I would want to "fix" this issue if someone comes up with a reasonable (tested) patch that: 1) Detects the platform 2) Renames fusion::nil to something else (only for the affected platform) Yet, no-one wants to do this. Instead we get nasty remarks such as those found here: https://svn.boost.org/trac/boost/ticket/5010#comment:16 What do we do? I'm seeking for a resolution. Regards, -- Joel de Guzman http://www.boostpro.com http://boost-spirit.com

4 5

[config] consexpr workaround
by vicente.botet 21 Mar '13

21 Mar '13

Hi, in order to make easier the introduction of constexpr in a portable way I would like we add a Boost Config workarround. We can define some macros depending on whether BOOST_NO_CONSTEXPR is defined or not. #if defined(BOOST_NO_CONSTEXPR) #define BOOST_CONSTEXPR #define BOOST_CONSTEXPR_OR_CONST const #else #define BOOST_CONSTEXPR constexpr #define BOOST_CONSTEXPR_OR_CONST constexpr #endif For most of the constexpr functions or constructors BOOST_CONSTEXPR will work. constexpr tuple(); =versus= BOOST_CONSTEXPR tuple(); When used for static constants BOOST_CONSTEXPR_OR_CONST is needed as we need to preserv the const keyword when consexpr is not available. static constexpr UIntType xor_mask = a; =versus= static BOOST_CONSTEXPR_OR_CONST UIntType xor_mask = a; We could also add a STATIC_CONSTEXPR macro #define BOOST_STATIC_CONSTEXPR static BOOST_CONSTEXPR_OR_CONST static constexpr UIntType xor_mask = a; =versus= BOOST_STATIC_CONSTEXPR UIntType xor_mask = a; For this case the existing macro BOOST_STATIC_CONSTANT could be modified to use BOOST_CONSTEXPR_OR_CONST when static const was used. static constexpr UIntType xor_mask = a; =versus= BOOST_STATIC_CONSTANT(UIntType, xor_mask = a); Can we introduce this workaround? Best regards, Vicente _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

6 17

[thread] thread_specific_ptr leaks on VS2012 when using std::async()
by Klaim - Joël Lamotte 05 Mar '13

05 Mar '13

Hi, The title says it all. I think I found a memory leak with the help of boost.log author Andrei Semashev. I was using Boost.Log in Visual Studio 2012 (released one) and tried to use Visual Leak Detector because Visual Studio basic leak detector was reporting leaks. I isolated the leaks to usage of log and switched to VLD to check if the basic detector wasn't giving me false positive. I contacted Andrei to see if he could check it but he don't have VS2012 available so I setup some tests to isolate the problem. In the end of our exchange we concluded it was a false positive (it only leak on end of program). However it is still an annoying noise in the leak report logs, so people not understanding the source of this problem might be interested in this email. I attach the whole email exchange to this email, tell me if leak logs are necessary too. The last version of my test is at the end of the email (first program). Basically, the leak appear only when using std::async() in combination of boost::thread_specific_ptr : - using exclusively boost threading libraries (both with dynamic and static linking) result in no leak - using exclusively std threading libraries but not std::async() result in no leak - using std::async() result in a leak The second test program shows that using Intel Threading Building Blocks, I get leaks only if : - I use std::async() in combination with boost::thread_specific_ptr, as before (I mean I use tbb without a leak, then I add a std::async() call to the same task function and there is a leak) - I don't use std::async() but I don't manage the lifetime of tbb task scheduler We think the threads spawned by both tbb (that is supposed to be a superset of ppl) and std::async() (that is supposed to use ppl/concrt task scheduler) are not ended yet when the program reach the end of main (which seems logical as the task scheduler is then managed as a static global), making boost::thread_specific_ptr not release some data on thread destruction, as it is notified too late and any leak detection tool willl generate noise due to this. A way to fix this is to explicitely end the task scheduler, being tbb or ppl/concrt. I will use tbb task scheduler explicitely initialized/terminated in my project so it will solve the problem on my side. Joel Lamotte ------------------------------------ // this program was used to see the memory leak #define TEST_ASYNC // comment this to make it linear and not leak //#define WITH_BOOST_THREADS #define WITH_STD_ASYNC // uncomment this to leak //#define WITH_BOOST_LOG // boost log also leak if std::async is used #include <boost/thread.hpp> #ifdef WITH_BOOST_THREADS # include <boost/thread/future.hpp> # include <boost/chrono.hpp> # define THIS_THREAD boost::this_thread # define THREAD_LIB boost::thread # define CHRONO_LIB boost::chrono # define MY_FUTURE boost::future #else # include <future> # include <thread> # include <chrono> # define THIS_THREAD std::this_thread # define THREAD_LIB std::thread # define CHRONO_LIB std::chrono # define MY_FUTURE std::future #endif #ifdef WITH_BOOST_LOG # include <boost/log/trivial.hpp> # define MY_LOG BOOST_LOG_TRIVIAL(info) #else # include <iostream> # define MY_LOG std::cout << '\n' #endif #define BASIC_VS_LEAK_DETECTOR 0 #define VISUAL_LEAK_DETECTOR 1 #define LEAK_DETECTOR VISUAL_LEAK_DETECTOR #if LEAK_DETECTOR == BASIC_VS_LEAK_DETECTOR # define _CRTDBG_MAP_ALLOC # include <stdlib.h> # include <crtdbg.h> #else # include "vld.h" #endif struct my_data { char data[1024]; my_data() { MY_LOG << "CONSTRUCTOR my_data - " << THIS_THREAD::get_id(); } ~my_data() { MY_LOG << "DESTRUCTOR my_data - " << THIS_THREAD::get_id(); } }; boost::thread_specific_ptr< my_data > ts_ptr; void my_thread_foo() { ts_ptr.reset(new my_data()); } int work() { for( int i = 0; i < 42; ++i ) { MY_LOG << "THIS IS A MESSAGE - I = " << i; MY_LOG << "ts_ptr = " << ts_ptr.get(); my_thread_foo(); THIS_THREAD::sleep_for( CHRONO_LIB::milliseconds(10) ); } return 0; } int main(int argc, char *argv[]) { #if LEAK_DETECTOR == BASIC_VS_LEAK_DETECTOR // First simple memory leak detection for Visual Studio // use _crtBreakAlloc to put a breakpoint on the provided memory leak id allocation //_crtBreakAlloc = 1149; _CrtSetDbgFlag ( _CRTDBG_ALLOC_MEM_DF | _CRTDBG_LEAK_CHECK_DF ); #endif //int* k = new int[42]; // to check that memory leak detection does work MY_LOG << "Hello, World!"; #ifdef TEST_ASYNC # ifndef WITH_BOOST_THREADS std::vector< std::future<int> > work_in_progress(2); # ifdef WITH_STD_ASYNC for( auto& ftr : work_in_progress ) { ftr = std::async( work ); } # else for( auto& ftr : work_in_progress ) { std::packaged_task< int() > task(work); ftr = task.get_future(); std::thread thread( std::move(task) ); thread.detach(); } # endif for( auto& ftr : work_in_progress ) { ftr.get(); } # else std::vector< boost::unique_future<int> > work_in_progress(42); for( auto& ftr : work_in_progress ) { boost::packaged_task<int> task(work); // boost's packaged_task don't take the full signature as parameter, it takes the return type only ftr = task.get_future(); boost::thread thread( boost::move(task) ); thread.detach(); } for( auto& ftr : work_in_progress ) { ftr.get(); } # endif #else for( int i = 0; i < 42; ++i ) { work(); } #endif MY_LOG << "END"; return EXIT_SUCCESS; } -------------------------------------- // this program tests if the memory leaks appear with Threading Building Blocks #define BASIC_VS_LEAK_DETECTOR 0 #define VISUAL_LEAK_DETECTOR 1 #define LEAK_DETECTOR VISUAL_LEAK_DETECTOR #define WITH_ROOT_TASK //#define WITH_BOOST_LOG //#define WITH_STD_ASYNC // uncomment to leak #ifdef WITH_STD_ASYNC # include <future> #endif #include <thread> #include <atomic> #include <boost/thread.hpp> #include <tbb/tbb.h> #include <tbb/task_scheduler_init.h> #ifdef WITH_BOOST_LOG # include <boost/log/trivial.hpp> # define MY_LOG BOOST_LOG_TRIVIAL(info) #else # include <iostream> # define MY_LOG std::cout << '\n' #endif #if LEAK_DETECTOR == BASIC_VS_LEAK_DETECTOR # define _CRTDBG_MAP_ALLOC # include <stdlib.h> # include <crtdbg.h> #else # include "vld.h" #endif namespace test { struct my_data { char data[1024]; }; boost::thread_specific_ptr< my_data > ts_ptr; void my_thread_foo() { ts_ptr.reset(new my_data()); } class UpdateTask : public tbb::task { public: UpdateTask() : idx( s_idx++ ) { MY_LOG << "[UpdateTask " << idx << " ] " << std::endl; } ~UpdateTask() { MY_LOG << "[/UpdateTask " << idx << " ]" << std::endl; } tbb::task* execute() { MY_LOG << "[" << std::this_thread::get_id() << "] Tick "<< m_count <<std::endl; my_thread_foo(); ++m_count; if( m_count < 100 ) { // make sure this is re-executed this->increment_ref_count(); this->recycle_as_safe_continuation(); } return nullptr; } private: static std::atomic<int> s_idx; std::atomic<int> m_count; const int idx; }; std::atomic<int> UpdateTask::s_idx = 0; class TaskScheduler // using TBB { public: #ifdef WITH_ROOT_TASK TaskScheduler() : m_root_task( *new (tbb::task::allocate_root()) tbb::empty_task ) { m_root_task.increment_ref_count(); } ~TaskScheduler() { m_root_task.destroy(m_root_task); } #endif void register_update_task() { #ifdef WITH_ROOT_TASK m_root_task.increment_ref_count(); UpdateTask& updater = *new(m_root_task.allocate_child()) UpdateTask(); #else UpdateTask& updater = *new(tbb::task::allocate_root()) UpdateTask(); #endif m_task_list.push_back( updater ); } void run_and_wait() { #ifdef WITH_ROOT_TASK m_root_task.spawn( m_task_list ); m_root_task.wait_for_all(); #else tbb::task::spawn_root_and_wait( m_task_list ); #endif } private: tbb::task_list m_task_list; // uncomment the following line to not leak tbb //tbb::task_scheduler_init m_engine_instance; // We explicitly create and destroy the TBB task scheduler to avoid memory leak warning noises. #ifdef WITH_ROOT_TASK tbb::task& m_root_task; #endif }; void tbb_test() { TaskScheduler task_scheduler; for( int i = 0; i < 50; ++i ) { task_scheduler.register_update_task(); } task_scheduler.run_and_wait(); } } int main(int argc, char *argv[]) { #if LEAK_DETECTOR == BASIC_VS_LEAK_DETECTOR // First simple memory leak detection for Visual Studio // use _crtBreakAlloc to put a breakpoint on the provided memory leak id allocation //_crtBreakAlloc = 148; _CrtSetDbgFlag ( _CRTDBG_ALLOC_MEM_DF | _CRTDBG_LEAK_CHECK_DF ); #endif #ifdef WITH_STD_ASYNC std::atomic<bool> finished = false; std::async( [&]{ while( !finished ) { MY_LOG << "POP"; test::my_thread_foo(); std::this_thread::sleep_for( std::chrono::milliseconds(500) ); } } ); #endif test::tbb_test(); #ifdef WITH_STD_ASYNC finished = true; #endif MY_LOG << "\nEND"; std::this_thread::sleep_for( std::chrono::seconds(4) ); return 0; }

3 5

[thread] boost::thread and thread safety annotations
by Wladimir 04 Mar '13

04 Mar '13

Hello, The Clang C++ compiler project is currently working on a thread safety analyzer. By making use of so-called thread safety annotations within the source code, several problems with synchronization primitives can be found statically. For example: usage of a data structure without acquiring its guarding lock. See here for an overview of the available attributes: http://clang.llvm.org/docs/LanguageExtensions.html#threadsafety It is customary to use these attributes by defining macros, for compatibility: http://www.mail-archive.com/linuxkernelnewbies@googlegroups.com/msg01455.ht… At one time, it was also supposed to end up in G++, but this was abandoned in favor of clang (see http://gcc.gnu.org/wiki/ThreadSafetyAnnotation) But at least the annotations are fairly standardized. I think it would be useful to add these annotations to boost::thread, so that projects using that library can make use of the static checking. As I understand it, is only a matter of marking data structures that serve as lock/scoped_lock (such as boost::mutex, boost::recursive_mutex, ...), and methods that act upon the lock with the appropriate attributes. Any interest in this? Regards, Wladimir

2 1

Fwd: [Thread] Solution to conflict with MFC?
by Thorsten Ottosen 28 Feb '13

28 Feb '13

Hi Thread maintainers, Anthony speaks about a patch to make this work. Does anyone know where it is? And could it be applied? Thanks -Thorsten -------- Original Meddelelse -------- Subject: [Thread] Solution to conflict with MFC? Date: Tue, 26 Apr 2011 13:28:56 +0200 From: Christian Larsen <contact(a)dword.dk> Reply-To: boost-users(a)lists.boost.org To: boost-users(a)lists.boost.org Newsgroups: gmane.comp.lib.boost.user Hello, I know this has been asked before, but I could not find a good solution. I'm experiencing problems with an application using both MFC and Boost.Thread. Specifically the assertion ASSERT(AfxGetModuleState() != AfxGetAppModuleState()); in AfxCoreInitModule() fails. I link Boost.Thread statically into a DLL in my project. From previous posts to this list and elsewhere, e.g. http://lists.boost.org/boost-users/2009/04/46929.php, I see that the issue is caused by setting _pRawDllMain in tss_pe.cpp. Commenting this line does "solve" the problem, but I would rather not have to hack the Boost source code this way. It seems there is a patch somewhere for this problem (referred to in http://lists.boost.org/boost-users/2009/04/47015.php) but it appears it never made it into the source. Is there any chance of this issue being solved in a better way? Best regards, Christian Larsen

5 9

[Config] N3276 decltype support on VC++ 11
by Michel Morin 28 Feb '13

28 Feb '13

IIRC, Stephan said that VC++ 11 supports N3276 decltype. Shall we "undef" BOOST_NO_CXX11_DECLTYPE_N3276 for VC++ 11? This enables automatic use of decltype-based `boost::result_of`. Trivial patch attached. Regards, Michel

11 79

[multi_index] Move Semantics
by Mark Snelling 27 Feb '13

27 Feb '13

Hi, I've been a user of Boost.MultiIndex for a number of years and think it's a great library. Is there any firm plan to add move semantics? It's been noted under "Future Work" in the docs since Boost 1.32. Regards, Mark

6 10

Problems with building quickbook docs
by Andrey Semashev 21 Feb '13

21 Feb '13

Hi, I'm having problems with building quickbook docs for my library. I have the using quickbook ; as well as doxygen, xsltproc and boostbook in my ~/user-config.jam. When I run: bjam -j 2 release link=static libs/log/doc I get the following error: .../boost-release/tools/build/v2/build/generators.jam:978: in try-one-generator-really *** argument error * rule object(generator)(a)60.run ( project name ? : property-set : sources + ) * called with: ( object(project-target)@1010 filters_reference-xml : object(property-set)@1387 : ) * missing argument sources .../boost-release/tools/build/v2/build/generators.jam:370:see definition of rule 'object(generator)(a)60.run' being called .../boost-release/tools/build/v2/build/generators.jam:1040: in try-one-generator .../boost-release/tools/build/v2/build/generators.jam:1254: in construct-really .../boost-release/tools/build/v2/build/generators.jam:1338: in generators.construct .../boost-release/tools/build/v2/build/targets.jam:1495: in construct .../boost-release/tools/build/v2/build/targets.jam:1298: in object(typed-target)(a)1058.generate .../boost-release/tools/build/v2/build/targets.jam:732: in generate-really .../boost-release/tools/build/v2/build/targets.jam:704: in object(main-target)(a)1164.generate .../boost-release/tools/build/v2/build/targets.jam:848: in targets.generate-from-reference .../boost-release/tools/build/v2/build/targets.jam:1217: in generate-dependencies .../boost-release/tools/build/v2/build/targets.jam:1269: in object(typed-target)(a)1061.generate .../boost-release/tools/build/v2/build/targets.jam:732: in generate-really .../boost-release/tools/build/v2/build/targets.jam:704: in object(main-target)(a)1165.generate .../boost-release/tools/build/v2/build/targets.jam:848: in targets.generate-from-reference .../boost-release/tools/build/v2/build/targets.jam:1217: in generate-dependencies .../boost-release/tools/build/v2/build/targets.jam:1269: in object(typed-target)(a)1062.generate .../boost-release/tools/build/v2/build/targets.jam:732: in generate-really .../boost-release/tools/build/v2/build/targets.jam:704: in object(main-target)(a)1166.generate .../boost-release/tools/build/v2/build/targets.jam:848: in targets.generate-from-reference .../boost-release/tools/build/v2/build/targets.jam:1217: in generate-dependencies .../boost-release/tools/build/v2/build/targets.jam:1269: in object(install-target-class)(a)1065.generate .../boost-release/tools/build/v2/build/targets.jam:732: in generate-really .../boost-release/tools/build/v2/build/targets.jam:704: in object(main-target)(a)1167.generate .../boost-release/tools/build/v2/build/targets.jam:848: in targets.generate-from-reference .../boost-release/tools/build/v2/build/targets.jam:1217: in generate-dependencies .../boost-release/tools/build/v2/build/targets.jam:1399: in basic-target.compute-usage-requirements .../boost-release/tools/build/v2/build/alias.jam:47: in compute-usage-requirements .../boost-release/tools/build/v2/build/targets.jam:1319: in object(alias-target-class)(a)1068.generate .../boost-release/tools/build/v2/build/targets.jam:732: in generate-really .../boost-release/tools/build/v2/build/targets.jam:704: in object(main-target)(a)1168.generate .../boost-release/tools/build/v2/build/targets.jam:258: in object(project-target)(a)1010.generate .../boost-release/tools/build/v2/build-system.jam:736: in load .../boost-release/tools/build/v2/kernel/modules.jam:283: in import .../boost-release/tools/build/v2/kernel/bootstrap.jam:142: in boost-build .../boost-release/boost-build.jam:17: in module scope index.html libs/index.html more/getting_started.html tools/index.html I'm using the release branch. Does anyone know what the problem could be?

2 2

Release Managers: permission to merge small feature to release?
by Marshall Clow 19 Feb '13

19 Feb '13

I have a ticket <https://svn.boost.org/trac/boost/ticket/7652> asking for compile-time checked access to elements of a boost::array. I have implemented a specialization of boost::get (and for c++11, std::get) that does this, and it's been on the trunk and being tested for a couple weeks. This is technically not a bug fix, but new functionality, but I'd like to get it into the next release. So, I'm asking permission to merge to release. The change lists are 82083 (for the functionality), 82084 and 82102 (for the tests), and 82103 (for the docs) Thanks! -- Marshall

5 5

[Lockfree] ringbuffer
by Rich E 17 Feb '13

17 Feb '13

First off, all Boost.Lockfree tests in trunk are passing for me on clang 4.0 on OS X, hurrah! Thank you Tim for working on this for so long... I'm running through the examples now, only with the outdated documentation as a guide (more than a couple years old). I cannot find the ringbuffer container - was it renamed or removed altogether during the review period? I notice spsc_queue acts awefully like a ringbuffer, and it's implementation contains many

2 6

[fixed_point] Request for interest in a binary fixed point library
by Vicente J. Botet Escriba 02 Feb '13

02 Feb '13

Hi, the recent discussion on the MultiplePrecission Arithmetic library has show that some people has its ow fixed point library. Is there an interest in a Boost library having as base http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3352.html? I have started a prototype http://svn.boost.org/svn/boost/sandbox/fixed_point (there is no doc yet but the basic goal is quite close to the N3352 C++ proposal). This prototype should allow you to play a little bit with. If yes, what would you like to be changed, added or improved in n3352? Next follows some design decisions that IMO need to be decided before hand. * Should integers and reals be represented by separated classes? * Should signed and unsigned be represented by separated classes? * Should the library use a specific representation for signed numbers (separated sign, 2-complement? Let the user choose? * Should the library provide arbitrary range and resolution and allocators? * Should the library be open to overflow and rounding or just implement some of the possible policies? and in this case which ones? * Should fixed_point be convertible to/from integer/float/double? * Could the result of an arithmetic operation have more range and resolution than his arguments? * Is there a need for a specific I/O? * is there a need for radix other than 2 (binary)? * Should the library implement the basic functions, or should it imperatively implement the C++11 math functions? Could a first version just forward to the c++11 math functions? * Should the library support just one of the know ways to name a fixed-point, a U(a,b), nQm, ...? Provide some ways to move from one to another? * Could expect the same/better performances respect to hand written code? * What should be the size used by a fixed_point instance? _fast? _least? Should the user be able to decide which approach is better for his needs? * Which should be the namespace? boost? boost/fixed_point? boost/binary_fixed_point? boost/bfp? ... * others you can think of. Please, replay if you are interested, have some experience in the domain, good ideas, .. Best regards, Vicente

6 44

program_options: Support for open-end options
by ST 27 Jan '13

27 Jan '13

Hi, It would be great to implement support for open-end options, something like that: item_1 = 23 item_2 = 45 ... item_N = 465 The idea is to to be able to provide following input: configOptions.add_options() ("item_", value<int>(), "items"); now if add_options() sees a key that ends with a "_" it accepts all options with keys that start with item_, no matter what comes after it, and treat all of them as int . Nesting should also be possible - like this: "item_.subitem_.subsubitem_" (item_3.subitem_FOO.subsubitem_34 should be a valid option key). I can try to implement it, however only if it will have a chance to be merged into the boost library. Whom should I contact regarding this? Thank you, Simone

5 13

[1.53.0] Release Notes
by Daniel James 26 Jan '13

26 Jan '13

Hello everyone, Please can you send me your library's release notes for 1.53. Or if you prefer you can add them yourself to: http://svn.boost.org/svn/boost/website/public_html/live/feed/history/boost_… thanks, Daniel

9 13

Boost Support for Android and iOS
by rohit dhamija 25 Jan '13

25 Jan '13

Hi, Boost libraries are intended to be widely useful, and usable across a broad range of applications, but yet there is no official support available for Android and iOS 1. Is there any specific reason behind the same (like not optimized for embedded devices)? Or any other reason? 2. Are there (at all) any known issues if we use boost libraries for networking and thread synchronization for Smartphone application development ? Will it be a good idea to use BOOST ASIO for the same? I found some articles to compile boost but it would be great if we have some official links. FYI are the links found https://github.com/MysticTreeGames/Boost-for-Android http://www.codexperiments.com/android/2011/05/tips-tricks-building-boost-wi… RDX

10 10

[variant] Basic rvalue and C++11 features support
by Antony Polukhin 20 Jan '13

20 Jan '13

Hi, There is a patch in ticket #7620 that adds some rvalue assignment operators and rvalue constructors for Boost.Variant library. I saw no activity from authors of Boost.Variant Eric Friedman and Itay Maman for a long time, so if there will be no objections, I'll commit patch to trunk in the middle of November. Any suggestions and comments are welcomed. -- Best regards, Antony Polukhin

19 74

Changes to VS 2012 config
by Marshall Clow 17 Jan '13

17 Jan '13

Just so people know - I'm updating the Visual Studio configuration to more accurately reflect the capabilities of VS 2012. The first step was in http://svn.boost.org/trac/boost/changeset/81613 ; the next step will be to update the compiler features. If you see any problems, please let me know. -- Marshall

14 26

[parameter] std proposal
by Lorenzo Caminiti 07 Jan '13

07 Jan '13

Hello all, Is there a C++ standard proposal for named parameter addition? I am looking for an "N-paper" for named parameters similar to N2081 for concepts, or N1962 for contracts. Thank you. -- Sent from my mobile device Lorenzo

6 8

[utf8_codecvt_facet]
by Robert Ramey 06 Jan '13

06 Jan '13

change Revision: 81616 Author: marshall Date: 11:12:42 AM, Wednesday, November 28, 2012 Message: Fixed incorrect 'const' param for utf8_codecvt_facet::do_length ---- Modified : /trunk/boost/detail/utf8_codecvt_facet.hpp This change causes the a failure in the serialization library test suite with "test_utf8_codecvt" on all platforms which use the gcc standard library. I'm not sure what motivated the change or what it addressed but I'm pretty sure it's causing this (and a couple other) test failures. Note that all the failures are related to usage of wchar_t - perhaps that helps. Note that the test is part of the serialization library test suite - but it has nothing to do with serialization per se and doesn't use any of the serialization library. It just happens to be there because there was no more convenient place to put it. Marshall - could you please look into this? Robert Ramey

2 9

[Range] Proposal: a sub-maintainer of Boost.Range
by Michel Morin 05 Jan '13

05 Jan '13

Dear Neil, Dear Nate, First I'd like to say thank you for your library, Neil. It is a very useful library and it's great fun to writing codes with range adaptors. Boost.Range is one of the most important Boost libraries that are not yet added to the Standard. I know that Neil has made an effort to make time for developing the library, but recently making time for development seems difficult. And there are several open tickets of trivial bugs (e.g. #5603, #6110). Considering this situation, I'd like to make a proposal about Boost.Range: ** Adding a sub-maintainer to Boost.Range ** This reduces author's maintenance burden and also helps more stable development of the library. I recommend Nathan Ridge as a sub-maintainer of Boost.Range. His knowledge, experiences and contribution to Boost are great. If both of Neil and Nate accept the proposal, and if Nate needs some support for the start-up, I'll try my best to support him. I also believe that Jeff will also support him ;) Neil, what do you think about this proposal? I would appreciate and respect any of your reply. Yours sincerely, Michel

11 42

[smart_ptr] error with nullptr_t
by Vicente J. Botet Escriba 05 Jan '13

05 Jan '13

Hi, next follows a compile error with clang 3.1 c++11 just including #include <boost/shared_ptr.hpp> iMac-de-Vicente-Botet-Escriba:test viboes$ time bjam toolset=clang-3.1x ts_ -q ...patience... ...found 1100 targets... ...updating 50 targets... clang-darwin.compile.c++ ../../../bin.v2/libs/thread/test/test_so.test/clang-darwin-3.1x/debug/threading-multi/test_so.o In file included from ../example/test_so.cpp:6: In file included from ../../../boost/shared_ptr.hpp:17: ../../../boost/smart_ptr/shared_ptr.hpp:344:22: error: non-friend class member 'nullptr_t' cannot have a qualified name shared_ptr( std::nullptr_t ) BOOST_NOEXCEPT : px( 0 ), pn() // never throws ~~~~~^ ../../../boost/smart_ptr/shared_ptr.hpp:344:33: error: expected ';' at end of declaration list shared_ptr( std::nullptr_t ) BOOST_NOEXCEPT : px( 0 ), pn() // never throws ^ ;

9 22

[Release managers] Permission to rollback Boost.Thread breaking changes
by Vicente J. Botet Escriba 04 Jan '13

04 Jan '13

Hi, I would like to apply the following patch to trunk and release branch to avoid the Boost.Thread breaking changes. * [@http://svn.boost.org/trac/boost/ticket/6229 #6229] Rename the unique_future to future following the c++11. * [@http://svn.boost.org/trac/boost/ticket/6266 #6266] Breaking change: thread destructor should call terminate if joinable. * [@http://svn.boost.org/trac/boost/ticket/6269 #6269] Breaking change: thread move assignment should call terminate if joinable. This will let us the time to discuss the best way to manage with this breaking changes. Is someone against this late change? Best, Vicente svn diff boost/thread libs/thread Index: boost/thread/detail/config.hpp =================================================================== --- boost/thread/detail/config.hpp (revision 82295) +++ boost/thread/detail/config.hpp (working copy) @@ -78,9 +78,9 @@ #define BOOST_THREAD_RVALUE_REFERENCES_DONT_MATCH_FUNTION_PTR #endif -// Default version is 3 +// Default version #if !defined BOOST_THREAD_VERSION -#define BOOST_THREAD_VERSION 3 +#define BOOST_THREAD_VERSION 2 #else #if BOOST_THREAD_VERSION!=2 && BOOST_THREAD_VERSION!=3 && BOOST_THREAD_VERSION!=4 #error "BOOST_THREAD_VERSION must be 2, 3 or 4" Index: libs/thread/src/win32/thread.cpp =================================================================== --- libs/thread/src/win32/thread.cpp (revision 82295) +++ libs/thread/src/win32/thread.cpp (working copy) @@ -12,7 +12,7 @@ #ifndef WINVER #define WINVER 0x400 #endif -#define BOOST_THREAD_VERSION 3 +//#define BOOST_THREAD_VERSION 3 #include <boost/thread/thread.hpp> #include <boost/thread/once.hpp> Index: libs/thread/src/pthread/thread.cpp =================================================================== --- libs/thread/src/pthread/thread.cpp (revision 82295) +++ libs/thread/src/pthread/thread.cpp (working copy) @@ -6,7 +6,7 @@ // Distributed under the Boost Software License, Version 1.0. (See accompanying // file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -#define BOOST_THREAD_VERSION 3 +//#define BOOST_THREAD_VERSION 3 #include <boost/thread/detail/config.hpp> #include <boost/thread/thread.hpp>

2 9

Release managers: Boost.Thread breaking changes in 1.53
by Vicente J. Botet Escriba 04 Jan '13

04 Jan '13

Hi, there has been some threads about the following Boost.Thread breaking change in release 1.53. "Breaking changes when BOOST_THREAD_VERSION==3 (Default value since Boost 1.53): There are some new features which share the same interface but with different behavior. These breaking features are provided by default when BOOST_THREAD_VERSION is 3, but the user can however choose the version 2 behavior by defining the corresponding macro. As for the deprecated features, these broken features will be only available until boost 1.55. * [@http://svn.boost.org/trac/boost/ticket/6229 #6229] Rename the unique_future to future following the c++11. * [@http://svn.boost.org/trac/boost/ticket/6266 #6266] Breaking change: thread destructor should call terminate if joinable. * [@http://svn.boost.org/trac/boost/ticket/6269 #6269] Breaking change: thread move assignment should call terminate if joinable. " I would like to request advise from the release managers and of course the Boost community. Should I rollback the default to BOOST_THREAD_VERSION==3 for 1.53 and let the time to discuss the best way to manage with these breaking changes? Best, Vicente

21 40

[log] Most recent version
by Alexander Arhipenko 04 Jan '13

04 Jan '13

Hi, We're going to update boost.log sources in our code base. Could you please recommend what version to use? The code is taken from: https://boost-log.svn.sourceforge.net/svnroot/boost-log/. And currently I consider 3 options: branches/v1 branches/bleeding-edge trunk Thanks in advance. Regards

5 7

utf8_codecvt facet - volunteer opportuntiy
by Robert Ramey 03 Jan '13

03 Jan '13

Our implementation for a codecvt facet internal wide char to/from utf8 format requires some maintainence. We have our own implementation since 2001. Since then, the standard libary has come to specify some implementations and some libraries have implemented some or all of this aspect of the standard library. I've come to believe that we should: a) tweak our code to use the standard library implementations if they exist. b) tweak our code to use the names of the standard library implementation b) tweak our build so that our version replaces the the standard library implementation when and only when there is no standard implemenation available. This seemingly simple task is complicated by the following circumstances. a) The relationshp between UCS and Unicode is pretty confusing. b) The iterface for codecvt is confusing. c) a number of standard library implementations have non-conforming codecvt interface. d) a number of standard library implementations don't have any codecvt header at all. This is not a problem for our current implementation because we never import it. Anyone interested in working on this should contact Marshall, Beman or myself (in that precedance). Robert Ramey

2 1

[config] Proposed BOOST_NOEXCEPT_NOTHROW macro
by Beman Dawes 03 Jan '13

03 Jan '13

The three current BOOST_NOEXCEPT* macro variants miss the case where C++03 code has a "throw()" throw-specifier. Classes that derive from standard library exceptions need this to avoid breaking code on C++03 compilers. I'm not enamored with the BOOST_NOEXCEPT_NOTHROW name, so feel free to offer suggestions for alternate names. Here is the full set of macros: #ifdef BOOST_NO_NOEXCEPT # define BOOST_NOEXCEPT # define BOOST_NOEXCEPT_NOTHROW throw() <---- new macro # define BOOST_NOEXCEPT_IF(Predicate) # define BOOST_NOEXCEPT_EXPR(Expression) false #else # define BOOST_NOEXCEPT noexcept # define BOOST_NOEXCEPT_NOTHROW noexcept <---- new macro # define BOOST_NOEXCEPT_IF(Predicate) noexcept((Predicate)) # define BOOST_NOEXCEPT_EXPR(Expression) noexcept((Expression)) #endif Unless there are objections, I'll commit the changes Wednesday afternoon Eastern US time. --Beman

7 11

Flow-based programming library for Boost?
by Marcus Tomlinson 03 Jan '13

03 Jan '13

Is there any interest out there for a library that allows you to create fast, efficient flow-based programs with an easy-to-use object-oriented interface? (http://en.wikipedia.org/wiki/Flow-based_programming) I've created an open-source library that does this, called "DSPatch" ( http://sourceforge.net/projects/dspatch) and would like to contribute it to the Boost Libraries. Please let me know if this sounds like something you'd like to see in Boost. Thanks!

15 64

[GitHelp]TryModBoost gives fatal: reference is not a tree.
by Larry Evans 01 Jan '13

01 Jan '13

Trying the instructions here: https://svn.boost.org/trac/boost/wiki/TryModBoost resulted in an error at the `git submodule updata --init step. How can this be corrected? TIA. Larry Details of steps taken follow: ~/prog_dev/boost-modular $ git clone http://github.com/boost-lib/boost modular-boost Initialized empty Git repository in /home/evansl/prog_dev/boost-modular/modular-boost/.git/ remote: Counting objects: 8096, done. remote: Compressing objects: 100% (2982/2982), done. remote: Total 8096 (delta 5190), reused 8001 (delta 5095) Receiving objects: 100% (8096/8096), 1.98 MiB | 387 KiB/s, done. Resolving deltas: 100% (5190/5190), done. ~/prog_dev/boost-modular $ ls modular-boost ~/prog_dev/boost-modular $ cd modular-boost/ ~/prog_dev/boost-modular/modular-boost $ ls INSTALL boost.css bootstrap.sh index.html status Jamroot boost.png doc libs tools LICENSE_1_0.txt boostcpp.jam forward_headers.cmake more boost-build.jam bootstrap.bat index.htm rst.css ~/prog_dev/boost-modular/modular-boost $ git submodule update --init Submodule 'libs/accumulators' (git://github.com/boost-lib/accumulators.git) registered for path 'libs/accumulators' Submodule 'libs/algorithm' (git://github.com/boost-lib/algorithm.git) registered for path 'libs/algorithm' Submodule 'libs/any' (git://github.com/boost-lib/any.git) registered for path 'libs/any' Submodule 'libs/array' (git://github.com/boost-lib/array.git) registered for path 'libs/array' Submodule 'libs/asio' (git://github.com/boost-lib/asio.git) registered for path 'libs/asio' Submodule 'libs/assign' (git://github.com/boost-lib/assign.git) registered for path 'libs/assign' Submodule 'libs/atomic' (git://github.com/boost-lib/atomic.git) registered for path 'libs/atomic' Submodule 'libs/bimap' (git://github.com/boost-lib/bimap.git) registered for path 'libs/bimap' Submodule 'libs/bind' (git://github.com/boost-lib/bind.git) registered for path 'libs/bind' Submodule 'libs/chrono' (git://github.com/boost-lib/chrono.git) registered for path 'libs/chrono' Submodule 'libs/circular_buffer' (git://github.com/boost-lib/circular_buffer.git) registered for path 'libs/circular_buffer' Submodule 'libs/compatibility' (git://github.com/boost-lib/compatibility.git) registered for path 'libs/compatibility' Submodule 'libs/concept_check' (git://github.com/boost-lib/concept_check.git) registered for path 'libs/concept_check' Submodule 'libs/config' (git://github.com/boost-lib/config.git) registered for path 'libs/config' Submodule 'libs/container' (git://github.com/boost-lib/container.git) registered for path 'libs/container' Submodule 'libs/context' (git://github.com/boost-lib/context.git) registered for path 'libs/context' Submodule 'libs/conversion' (git://github.com/boost-lib/conversion.git) registered for path 'libs/conversion' Submodule 'libs/core' (git://github.com/boost-lib/core.git) registered for path 'libs/core' Submodule 'libs/coroutine' (git://github.com/boost-lib/coroutine.git) registered for path 'libs/coroutine' Submodule 'libs/crc' (git://github.com/boost-lib/crc.git) registered for path 'libs/crc' Submodule 'libs/date_time' (git://github.com/boost-lib/date_time.git) registered for path 'libs/date_time' Submodule 'libs/disjoint_sets' (git://github.com/boost-lib/disjoint_sets.git) registered for path 'libs/disjoint_sets' Submodule 'libs/dynamic_bitset' (git://github.com/boost-lib/dynamic_bitset.git) registered for path 'libs/dynamic_bitset' Submodule 'libs/exception' (git://github.com/boost-lib/exception.git) registered for path 'libs/exception' Submodule 'libs/filesystem' (git://github.com/boost-lib/filesystem.git) registered for path 'libs/filesystem' Submodule 'libs/flyweight' (git://github.com/boost-lib/flyweight.git) registered for path 'libs/flyweight' Submodule 'libs/foreach' (git://github.com/boost-lib/foreach.git) registered for path 'libs/foreach' Submodule 'libs/format' (git://github.com/boost-lib/format.git) registered for path 'libs/format' Submodule 'libs/function' (git://github.com/boost-lib/function.git) registered for path 'libs/function' Submodule 'libs/function_types' (git://github.com/boost-lib/function_types.git) registered for path 'libs/function_types' Submodule 'libs/functional' (git://github.com/boost-lib/functional.git) registered for path 'libs/functional' Submodule 'libs/functional_hash' (git://github.com/boost-lib/functional_hash.git) registered for path 'libs/functional_hash' Submodule 'libs/fusion' (git://github.com/boost-lib/fusion.git) registered for path 'libs/fusion' Submodule 'libs/geometry' (git://github.com/boost-lib/geometry.git) registered for path 'libs/geometry' Submodule 'libs/gil' (git://github.com/boost-lib/gil.git) registered for path 'libs/gil' Submodule 'libs/graph' (git://github.com/boost-lib/graph.git) registered for path 'libs/graph' Submodule 'libs/graph_parallel' (git://github.com/boost-lib/graph_parallel.git) registered for path 'libs/graph_parallel' Submodule 'libs/heap' (git://github.com/boost-lib/heap.git) registered for path 'libs/heap' Submodule 'libs/icl' (git://github.com/boost-lib/icl.git) registered for path 'libs/icl' Submodule 'libs/integer' (git://github.com/boost-lib/integer.git) registered for path 'libs/integer' Submodule 'libs/interprocess' (git://github.com/boost-lib/interprocess.git) registered for path 'libs/interprocess' Submodule 'libs/intrusive' (git://github.com/boost-lib/intrusive.git) registered for path 'libs/intrusive' Submodule 'libs/io' (git://github.com/boost-lib/io.git) registered for path 'libs/io' Submodule 'libs/iostreams' (git://github.com/boost-lib/iostreams.git) registered for path 'libs/iostreams' Submodule 'libs/iterator' (git://github.com/boost-lib/iterator.git) registered for path 'libs/iterator' Submodule 'libs/lambda' (git://github.com/boost-lib/lambda.git) registered for path 'libs/lambda' Submodule 'libs/local_function' (git://github.com/boost-lib/local_function.git) registered for path 'libs/local_function' Submodule 'libs/locale' (git://github.com/boost-lib/locale.git) registered for path 'libs/locale' Submodule 'libs/lockfree' (git://github.com/boost-lib/lockfree.git) registered for path 'libs/lockfree' Submodule 'libs/logic' (git://github.com/boost-lib/logic.git) registered for path 'libs/logic' Submodule 'libs/math' (git://github.com/boost-lib/math.git) registered for path 'libs/math' Submodule 'libs/move' (git://github.com/boost-lib/move.git) registered for path 'libs/move' Submodule 'libs/mpi' (git://github.com/boost-lib/mpi.git) registered for path 'libs/mpi' Submodule 'libs/mpl' (git://github.com/boost-lib/mpl.git) registered for path 'libs/mpl' Submodule 'libs/msm' (git://github.com/boost-lib/msm.git) registered for path 'libs/msm' Submodule 'libs/multi_array' (git://github.com/boost-lib/multi_array.git) registered for path 'libs/multi_array' Submodule 'libs/multi_index' (git://github.com/boost-lib/multi_index.git) registered for path 'libs/multi_index' Submodule 'libs/multiprecision' (git://github.com/boost-lib/multiprecision.git) registered for path 'libs/multiprecision' Submodule 'libs/numeric/conversion' (git://github.com/boost-lib/numeric_conversion.git) registered for path 'libs/numeric/conversion' Submodule 'libs/numeric/interval' (git://github.com/boost-lib/interval.git) registered for path 'libs/numeric/interval' Submodule 'libs/numeric/odeint' (git://github.com/boost-lib/odeint.git) registered for path 'libs/numeric/odeint' Submodule 'libs/numeric/ublas' (git://github.com/boost-lib/ublas.git) registered for path 'libs/numeric/ublas' Submodule 'libs/optional' (git://github.com/boost-lib/optional.git) registered for path 'libs/optional' Submodule 'libs/parameter' (git://github.com/boost-lib/parameter.git) registered for path 'libs/parameter' Submodule 'libs/phoenix' (git://github.com/boost-lib/phoenix.git) registered for path 'libs/phoenix' Submodule 'libs/polygon' (git://github.com/boost-lib/polygon.git) registered for path 'libs/polygon' Submodule 'libs/pool' (git://github.com/boost-lib/pool.git) registered for path 'libs/pool' Submodule 'libs/preprocessor' (git://github.com/boost-lib/preprocessor.git) registered for path 'libs/preprocessor' Submodule 'libs/program_options' (git://github.com/boost-lib/program_options.git) registered for path 'libs/program_options' Submodule 'libs/property_map' (git://github.com/boost-lib/property_map.git) registered for path 'libs/property_map' Submodule 'libs/property_tree' (git://github.com/boost-lib/property_tree.git) registered for path 'libs/property_tree' Submodule 'libs/proto' (git://github.com/boost-lib/proto.git) registered for path 'libs/proto' Submodule 'libs/ptr_container' (git://github.com/boost-lib/ptr_container.git) registered for path 'libs/ptr_container' Submodule 'libs/python' (git://github.com/boost-lib/python.git) registered for path 'libs/python' Submodule 'libs/random' (git://github.com/boost-lib/random.git) registered for path 'libs/random' Submodule 'libs/range' (git://github.com/boost-lib/range.git) registered for path 'libs/range' Submodule 'libs/ratio' (git://github.com/boost-lib/ratio.git) registered for path 'libs/ratio' Submodule 'libs/rational' (git://github.com/boost-lib/rational.git) registered for path 'libs/rational' Submodule 'libs/regex' (git://github.com/boost-lib/regex.git) registered for path 'libs/regex' Submodule 'libs/scope_exit' (git://github.com/boost-lib/scope_exit.git) registered for path 'libs/scope_exit' Submodule 'libs/serialization' (git://github.com/boost-lib/serialization.git) registered for path 'libs/serialization' Submodule 'libs/signals' (git://github.com/boost-lib/signals.git) registered for path 'libs/signals' Submodule 'libs/signals2' (git://github.com/boost-lib/signals2.git) registered for path 'libs/signals2' Submodule 'libs/smart_ptr' (git://github.com/boost-lib/smart_ptr.git) registered for path 'libs/smart_ptr' Submodule 'libs/spirit' (git://github.com/boost-lib/spirit.git) registered for path 'libs/spirit' Submodule 'libs/spirit_classic' (git://github.com/boost-lib/spirit_classic.git) registered for path 'libs/spirit_classic' Submodule 'libs/statechart' (git://github.com/boost-lib/statechart.git) registered for path 'libs/statechart' Submodule 'libs/static_assert' (git://github.com/boost-lib/static_assert.git) registered for path 'libs/static_assert' Submodule 'libs/system' (git://github.com/boost-lib/system.git) registered for path 'libs/system' Submodule 'libs/test' (git://github.com/boost-lib/test.git) registered for path 'libs/test' Submodule 'libs/thread' (git://github.com/boost-lib/thread.git) registered for path 'libs/thread' Submodule 'libs/timer' (git://github.com/boost-lib/timer.git) registered for path 'libs/timer' Submodule 'libs/tokenizer' (git://github.com/boost-lib/tokenizer.git) registered for path 'libs/tokenizer' Submodule 'libs/tr1' (git://github.com/boost-lib/tr1.git) registered for path 'libs/tr1' Submodule 'libs/tti' (git://github.com/boost-lib/tti.git) registered for path 'libs/tti' Submodule 'libs/tuple' (git://github.com/boost-lib/tuple.git) registered for path 'libs/tuple' Submodule 'libs/type_traits' (git://github.com/boost-lib/type_traits.git) registered for path 'libs/type_traits' Submodule 'libs/typeof' (git://github.com/boost-lib/typeof.git) registered for path 'libs/typeof' Submodule 'libs/units' (git://github.com/boost-lib/units.git) registered for path 'libs/units' Submodule 'libs/unordered' (git://github.com/boost-lib/unordered.git) registered for path 'libs/unordered' Submodule 'libs/utility' (git://github.com/boost-lib/utility.git) registered for path 'libs/utility' Submodule 'libs/uuid' (git://github.com/boost-lib/uuid.git) registered for path 'libs/uuid' Submodule 'libs/variant' (git://github.com/boost-lib/variant.git) registered for path 'libs/variant' Submodule 'libs/wave' (git://github.com/boost-lib/wave.git) registered for path 'libs/wave' Submodule 'libs/xpressive' (git://github.com/boost-lib/xpressive.git) registered for path 'libs/xpressive' Submodule 'tools/auto_index' (git://github.com/boost-lib/auto_index.git) registered for path 'tools/auto_index' Submodule 'tools/bcp' (git://github.com/boost-lib/bcp.git) registered for path 'tools/bcp' Submodule 'tools/boostbook' (git://github.com/boost-lib/boostbook.git) registered for path 'tools/boostbook' Submodule 'tools/build' (git://github.com/boost-lib/build.git) registered for path 'tools/build' Submodule 'tools/inspect' (git://github.com/boost-lib/inspect.git) registered for path 'tools/inspect' Submodule 'tools/litre' (git://github.com/boost-lib/litre.git) registered for path 'tools/litre' Submodule 'tools/quickbook' (git://github.com/boost-lib/quickbook.git) registered for path 'tools/quickbook' Initialized empty Git repository in /home/evansl/prog_dev/boost-modular/modular-boost/libs/accumulators/.git/ remote: Counting objects: 475, done. remote: Compressing objects: 100% (201/201), done. remote: Total 475 (delta 319), reused 407 (delta 252) Receiving objects: 100% (475/475), 204.69 KiB | 335 KiB/s, done. Resolving deltas: 100% (319/319), done. Submodule path 'libs/accumulators': checked out '853400b2e1b4321696a90184d49cbb6610738806' Initialized empty Git repository in /home/evansl/prog_dev/boost-modular/modular-boost/libs/algorithm/.git/ remote: Counting objects: 681, done. remote: Compressing objects: 100% (370/370), done. remote: Total 681 (delta 392), reused 544 (delta 255) Receiving objects: 100% (681/681), 1.66 MiB | 383 KiB/s, done. Resolving deltas: 100% (392/392), done. fatal: reference is not a tree: a601c9ad632035076bb3c0feee75e915cfb54fca Unable to checkout 'a601c9ad632035076bb3c0feee75e915cfb54fca' in submodule path 'libs/algorithm'

2 1

[string_ref] Feature requests
by Daniel James 01 Jan '13

01 Jan '13

Hi, I've been trying to convert quickbook to use boost::string_ref, and there are a few missing features that might be useful: Construction from a pair of iterators, either std::basic_string::const_iterator, or boost::basic_string_ref::const_iterator. Which of course can be the same type, which is annoying but not too hard to work around. Easy conversion to std::basic_string. There's a C++11 explicit string operator, but that isn't much good for portable code. Something like a 'string' or 'to_string' member would do the trick. Support for comparisons with std::basic_string. The comparison operators are templates so they aren't called with an implicit conversion. Could use a template parameter for the type so that it picks up anything which is (implicitly?) convertible to boost::basic_string_ref, maybe using SFINAE. I didn't need it, but could probably also could do with a 'hash_value' function for boost::hash support. Is potentially error prone if the original string is modified or destroy, but there are some valid use cases. thanks, Daniel

4 13

[exception][iostream] link error in boost_1_52_0
by Jeff Flinn 31 Dec '12

31 Dec '12

I'm getting the following link error using boost_1_52_0 with Xcode 3.2.6 gcc 4.2: "std::bad_alloc::what() const", referenced from: vtable for boost::exception_detail::error_info_injector<std::bad_alloc>in libboost_iostreams-mt.a(zlib.o) vtable for boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::bad_alloc> >in libboost_iostreams-mt.a(zlib.o) Boost exception is listed as a header only library, but there is clone_current_exception_non_intrusive.cpp in ..\boost_1_52_0\libs\exception\src. Does boost.exception lib need to be built? thanks, jeff

2 2

[trunk] permission denied?
by Oliver Kowalke 31 Dec '12

31 Dec '12

Did you reset the passwords for trunk? Until today I was able to commit changes to boost-trunk - but my password is invalid now?! Oliver

7 9

[Git] Regression testing modular Boost
by Beman Dawes 30 Dec '12

30 Dec '12

Starting a new thread - this is far to important to bury in the long documentation thread! On Tue, Dec 11, 2012 at 10:52 AM, Rene Rivera <grafikrobot(a)gmail.com> wrote: >What is the procedure that testers will follow? I've been assuming testers will follow the same general procedure. But other than verifying that hand-invoked b2 runs tests as expected, nothing else has been done that I'm aware of. > Is there documentation equivalent to < > http://www.boost.org/development/running_regression_tests.html> for the new > setup? None yet. I've been assuming we will just update www.boost.org/development/running_regression_tests.html > What changes to the current tools need to happen to the adjust to > the new setup? As a first cut, branch the current tools and convert any code that currently uses svn commands to use git commands. But before any testing is done, it would be helpful if Boost.Build was updated to handle the generation of boost-root/boost header file links, rather than relying on the workaround cmake script. Do you feel comfortable enough with git to handle the conversion? --Beman

6 22

[Trac] Internal Server Error
by Vicente J. Botet Escriba 30 Dec '12

30 Dec '12

Hi, I'm getting a Internal Server Error TracError: IOError: [Errno 13] Permission denied: u'/opt/trac/boost/log/trac.log Could someone take a look? Vicente

1 0

[type_traits] Typo in Boost.TypeTraits
by Michel Morin 30 Dec '12

30 Dec '12

Patch attached for fixing typos in Boost.TypeTraits P.S. John, could you also apply the patch attached in #7683? https://svn.boost.org/trac/boost/ticket/7683 Regards, Michel

3 5

[algorithm] Typo in Boost.Algorithm
by Michel Morin 30 Dec '12

30 Dec '12

Patch attached for fixing typos in Boost.Algorithm P.S. Marshall, could you also apply the patch attached in #7714? https://svn.boost.org/trac/boost/ticket/7714 Regards, Michel

2 2

[Git] Modularization of Boost.Any, Boost.Array, and Boost.StaticAssert
by Daniel Pfeifer 29 Dec '12

29 Dec '12

Hi, according to our preliminary modularization, the candidates Boost.Any, Boost.Array, and Boost.StaticAssert each have their own repository, even though each of them consists of a single header file only (disregarding tests, examples and documentation). I propose to put all three of them into the Boost.Utility repository. Comments? --Daniel

7 9

[git] Boost.Build location
by Vladimir Prus 29 Dec '12

29 Dec '12

I am wondering what will be the location of Boost.Build after the git switch. It seems to be part of http://github.com/boost-lib/boost right now. Maybe, it would be best to have separate git repository for Boost.Build? In particular, that would allow to fork just Boost.Build, which is important given git's inability to handle partial checkouts. It would also allow giving push access for Boost.Build to other people, without also giving access to superproject. Comments? Thanks, Volodya

18 44

[python] Proposal: RAII for Global Interpreter Lock (GIL)
by John Zwinck 29 Dec '12

29 Dec '12

There are many questions and example classes online for dealing with Python's Global Interpreter Lock (GIL) using RAII. I think Boost.Python should provide this functionality, rather than having users who build hybrid C++/Python applications copy-pasting code from various places. I was one of those users recently, and the code I developed to deal with it is now public: https://github.com/jzwinck/pccl/blob/master/InterpreterLockGuard.hpp https://github.com/jzwinck/pccl/blob/master/InterpreterLockGuard.cpp https://github.com/jzwinck/pccl/blob/master/test/InterpreterLockGuard.test.… Comments in the header explain how to use it in the context of Boost.Python, and contain a link to a wiki from which some of the code was originally copied. Why add this to Boost? It's clearly code that a bunch of people need, often people who are already using Boost.Python. It has a permissive license, and I can re-license it if need be. And it depends on Boost (mostly for thread-specific storage--I hope this dependency won't be seen as a liability here, though it could be removed if needed). This particular implementation was used successfully in a few programs in a commercial setting on Fedora and RHEL systems. It has some extra checks that we found helpful compared to some of the versions you'll find posted online. The code also builds and passes its tests with GCC on Mac OS X. I welcome any feedback regarding the suitability for inclusion in Boost of this particular code and/or the concepts it implements. John Zwinck

2 2