- Boost - lists.preview.boost.org

[community] request for revision: generic programming
by Steve Lorimer 06 Jun '13

06 Jun '13

In the light of C++11, the page on generic programming techniques http://www.boost.org/community/generic_programming.html is somewhat outdated. Any chance of a revision?

2 1

BOOST_STRONG_TYPEDEF
by Eric Niebler 05 Jun '13

05 Jun '13

Someone on stackoverflow is having a problem with BOOST_STRONG_TYPEDEF getting defined twice. There's a good recommendation there about boost/strong_typedef.hpp merely including boost/serialization/strong_typedef.hpp. Regardless, it's strange that trunk and release have been out of sync in this regard for so long. Robert? http://stackoverflow.com/questions/16901250/why-does-boost-include-two-diff… -- Eric Niebler Boost.org http://www.boost.org

1 0

[DNS] Heads up: svn.boost.org moving to a new server; IP address changing
by Beman Dawes 05 Jun '13

05 Jun '13

At 2:00 pm Eastern US time (i.e 30 minutes from now) we will switch svn.boost.org to a new server with a new IP address. It would be best to hold off on any SVN commits until after the change over, and after your DNS server has the new IP address. If command line "ping svn.boost.org" is going to [129.79.245.252], you are still getting the old IP address. Once svn.boost.org is resolving to [129.79.13.13] it should be OK to resume normal Subversion activity. Thanks, --Beman

1 2

[1.54.0] Beta 1 Available
by Marshall Clow 05 Jun '13

05 Jun '13

Boost release 1.54.0 beta 1 is now available from SourceForge See http://sourceforge.net/projects/boost/files/boost/1.54.0.beta.1/ This release contains 3 new libraries: • Log: Logging library, from Andrey Semashev. • TTI: Type Traits Introspection library, from Edward Diener. • Type Erasure: Runtime polymorphism based on concepts. and numerous enhancements and bug fixes for existing libraries. For details of what's in the release, see http://www.boost.org/users/history/version_1_54_0.html. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

3 2

[git] Library metadata
by Daniel James 04 Jun '13

04 Jun '13

Hello, Is anyone thinking about storing library metadata in modules? I'm thinking about this in context of the data required for the website, it'd be nice to automatically pull that from the library modules rather than having to maintain it myself, but I guess this might be something that others are thinking about (e.g. for the expected test failures, the library maintainer). So I was wondering if anyone has any plans? For anyone who isn't aware of it, the website data is stored in an xml file at: http://svn.boost.org/svn/boost/website/public_html/live/doc/libraries.xml Of course, it could be desirable to store modularized metadata in a different format. Daniel

3 4

[python] non-standard iteration / wrapping member function return value
by Matus Chochlik 04 Jun '13

04 Jun '13

Hi, I'm stuck at trying to make python bindings for a set of classes that use a non-c++-standard iteration protocol. I've made a minimal example of what I'm trying to do: the python-ized classes look in essence like this: //------------------------------------------------------------- class int_range { private: int i, max; public: int_range(int m) : i(0), max(m) { } bool empty(void) const { return i > max; } int front(void) const { return i; } void next(void) { ++i; } }; class range_maker { public: int_range make(void) const { return int_range(10); } }; //------------------------------------------------------------- the boost.python module that I've come up with so far: //------------------------------------------------------------- using namespace boost::python; class _py_int_range_iter { private: int_range _range; public: _py_int_range_iter(int_range range) : _range(range) { } _py_int_range_iter self(void) { return *this; } int next(void) { if(_range.empty()) objects::stop_iteration_error(); int result = _range.front(); _range.next(); return result; } }; class_<_py_int_range_iter>("_py_int_range_iter", init<const int_range&>()) .def("self", &_py_int_range_iter::self) .def("next", &_py_int_range_iter::next) ; class _py_int_range { private: int_range _range; public: _py_int_range(int_range range) : _range(range) { } _py_int_range_iter iter(void) { return _py_int_range_iter(_range); } }; class_<_py_int_range>("_py_int_range", init<const int_range&>()) .def("__iter__", &_py_int_range::iter) ; //------------------------------------------------------------- the problem is that when I register range_maker as follows... //------------------------------------------------------------- class_<range_maker>("range_maker") .def("make", &range_maker::make) ; //------------------------------------------------------------- ... it compiles but (obviously) fails in python at run-time because range_maker::make returns int_range and not _py_int_range. what do I need to do to make this work? I know that I could write _py_range_maker wrapping range_maker and let it return _py_int_range, but this approach does not scale very well. Is there some way to tell the def(...) function that I want to wrap the return value into an object of another type? Is there a return value policy for that or do I need to write my own? If so how? Thanks in advance Matus

2 2

Re: [boost] ATTN: Boost GSoC mentors and students: Continuous Integration for GSoC thoughts
by Niall Douglas 04 Jun '13

04 Jun '13

> > Personally speaking, I think this depth and degree of CI is > > *invaluable* to modern software development practice. > > I could not agree more. > > One thing you may want to add is coverage analysis with > https://coveralls.io/: > > If you build with gcc, pass "-fprofile-arcs -ftest-coverage" both to the compiler > and the linker. After running the tests, you can analyze the coverage with gcov > and send it to coveralls. > To collect and upload, I use the following script: > https://github.com/purpleKarrot/Karrot/blob/develop/test/coveralls.in > (Note that gcov 4.6 does not support all flags that I use in the script, I use it wiht > 4.8 only). That's really super useful of you Daniel. I wasn't aware that such a service existed for code coverage. Thank you. I don't suppose you'd know the answer to this question though: Travis CI's reporting is not great, it either reports success or failure and not *what* failed nor *why*. Specifically, if for example a build fails, I'd like to know which source files and what the compiler errors were. Similarly, if a unit test fails, I want to know which one and what the error was. Do you know if this can be done? Niall --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.

1 0

Re: [boost] ATTN: Boost GSoC mentors and students: Continuous Integration for GSoC thoughts
by Niall Douglas 04 Jun '13

04 Jun '13

> Just curious: is Visual Studio support not included because not deemed > important? Or not supported by this particular lib? Or not supported by Travis CI > for some reason? (licensing?) As others have mentioned, Travis CI provides only Ubuntu 12.04 x64 instances and none other. Interestingly, you /could/ actually package up MSVC and run it under wine, but Travis CI's free service limits test runs to 20 mins and getting wine et al installed in that time is probably more trouble than it's worth. Besides, I have another very good reason not to: my primary development platform is Visual Studio. Why? It has the least C++11 support, but also the best debugger. Any C++11 feature supported by the Nov 2012 CTP experimental MSVC is easily supported in GCC or clang, whereas the converse is most certainly not true. A further factor is that the library is an async file i/o abstraction layer intended for Boost, and the only true async backend currently is Windows IOCP. Therefore, naturally development, and especially performance tuning, currently focuses there. Travis CI is really useful though for checking Visual Studio work: MSVC I am told does not use an AST internally, and therefore permits C++ no other compiler will allow. Very often I write template metaprogramming which MSVC is absolutely fine with but chokes either GCC or clang or both. Travis CI emails me to tell me when I've done that. This is very, very useful. Niall --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.

1 0

[thread] call_once regression or it is planed so?
by Antony Polukhin 04 Jun '13

04 Jun '13

Hi, With 1.54.0_beta1 following code fails to compile: #include <boost/thread/once.hpp> void init_host(int); void init_host(); boost::once_flag instance_flag = BOOST_ONCE_INIT; int main() { boost::call_once(&init_host, instance_flag); } In 1.53 it worked fine. Is that meant to be so and no workaround is possible, or is it a bug? -- Best regards, Antony Polukhin

3 2

Asking for permission to merge small bugfix (Spirit)
by Hartmut Kaiser 04 Jun '13

04 Jun '13

I would like to merge a small bugfix to the release branch (commit set 84631, patch below). Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu Index: C:/CVS/boost/boost/spirit/home/lex/lexer/support_functions.hpp =================================================================== --- C:/CVS/boost/boost/spirit/home/lex/lexer/support_functions.hpp (revision 84630) +++ C:/CVS/boost/boost/spirit/home/lex/lexer/support_functions.hpp (revision 84631) @@ -49,7 +49,7 @@ { typedef typename typename remove_reference< - remove_const< + typename remove_const< typename mpl::at_c<typename Env::args_type, 4>::type >::type >::type

2 1