- Boost - lists.preview.boost.org

[random] new threefry random engine
by Thijs van den Berg 13 Jun '14

13 Jun '14

Hi all, I've completed a nice new random engine that I would like to propose for addition to boost/random. The engine is called "threefry" and it's based on the paper "Parallel random numbers: as easy as 1, 2, 3" by Salmon, John K. and Moraes, Mark A. and Dror, Ron O. and Shaw, David E. I've been using it myself a lot for the last couple of years, and now I've rewritten it so that it will fit in the boost random framework and adhere to the concepts. It has some really nice properties, in particular for large scale parallel computing: * High quality randomness (according to the BigCrush tests) with a cycle length of 2^258 * Fast (comparable to Mersenne Twister) & little memory usage (13x 64 bit integers) * O(1) discard and guarantees for non-overlapping sequences when the (up to 256 bit) seeds are unequal I've uploaded the code, description and tests to https://github.com/sitmo/threefry The actual engine is at https://github.com/sitmo/threefry/blob/master/random/include/boost/random/t… I would really appreciate any feedback about the idea for inclusion and of course comments about the quality of the code,tests,docs kind regards, Thijs Sitmo Consultancy B.V. Financial Modelling & Data Science + 31 6 24110061 thijs(a)sitmo.com P.O. Box 1059, 2600BB, Delft, The Netherlands

10 60

Errors Compiling in AIX 7.1 with gcc
by Axel Ismirlian 13 Jun '14

13 Jun '14

Hello, I am trying to compile boost on AIX 7.1 with gcc, but I am getting several errors. The configuration checks report that zlib support is disabled even though I do have that package installed. I also don't have icu support. Is there a package for that in AIX? I was not able to find one. Performing configuration checks - symlinks supported : yes - 32-bit : yes - arm : no - mips1 : no - power : yes - lockfree boost::atomic_flag : yes - has_icu builds : no warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - zlib : no - iconv (libc) : no - iconv (separate) : yes - icu : no - icu (lib64) : no - x86 : no - gcc visibility : no - long double support : yes warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. - zlib : no I also tried adding a user-config.jam in the boost/ (the same place as the project-config.jam) in order to add some flags to my gcc compilation and to use mpi, but my jam was soundly ignored. However, the most concerning of these errors is some apparent assembler error. gcc.compile.asm bin.v2/libs/context/build/gcc-4.8.1/release/link-static/threading-multi/asm/make_ ppc32_sysv_xcoff_gas.o Assembler: /tmp//cc0uhEhf.s: line 5: 1252-016 The specified opcode or pseudo-op is not valid. Use supported instructions or pseudo-ops only. /tmp//cc0uhEhf.s: line 8: 1252-016 The specified opcode or pseudo-op is not valid. Use supported instructions or pseudo-ops only. /tmp//cc0uhEhf.s: line 8: 1252-016 The specified opcode or pseudo-op is not valid. Use supported instructions or pseudo-ops only. /tmp//cc0uhEhf.s: line 8: 1252-016 The specified opcode or pseudo-op is not valid. Use supported instructions or pseudo-ops only. /tmp//cc0uhEhf.s: line 8: 1252-016 The specified opcode or pseudo-op is not valid. Use supported instructions or pseudo-ops only. /tmp//cc0uhEhf.s: line 11: 1252-142 Syntax error. /tmp//cc0uhEhf.s: line 15: 1252-142 Syntax error. /tmp//cc0uhEhf.s: line 19: 1252-142 Syntax error. /tmp//cc0uhEhf.s: line 22: 1252-142 Syntax error. /tmp//cc0uhEhf.s: line 25: 1252-142 Syntax error. /tmp//cc0uhEhf.s: line 27: 1252-142 Syntax error. /tmp//cc0uhEhf.s: line 28: 1252-142 Syntax error. /tmp//cc0uhEhf.s: line 30: 1252-142 Syntax error. /tmp//cc0uhEhf.s: line 32: 1252-142 Syntax error. /tmp//cc0uhEhf.s: line 34: 1252-142 Syntax error. /tmp//cc0uhEhf.s: line 37: 1252-142 Syntax error. /tmp//cc0uhEhf.s: line 40: 1252-142 Syntax error. /tmp//cc0uhEhf.s: line 46: 1252-142 Syntax error. /tmp//cc0uhEhf.s: line 48: 1252-142 Syntax error. /tmp//cc0uhEhf.s: line 50: 1252-142 Syntax error. /tmp//cc0uhEhf.s: line 53: 1252-142 Syntax error. I'm not sure how to go about fixing that. When I go to my /tmp/ directory ccvhH2Fc.s is not an assembler file present. Right after this message another error appears. ...failed gcc.compile.asm bin.v2/libs/context/build/gcc-4.8.1/release/link-static/threading-multi /asm/jump_ppc32_sysv_xcoff_gas.o... gcc.compile.c++ bin.v2/libs/context/build/gcc-4.8.1/release/link-static/threading-multi/untested. o libs/context/src/untested.cpp:7:2: error: #error "! code for this platform is untested - please r emove this file from build/Jamfile.v2 and report the test-result on boost-track !" #error "! code for this platform is untested - please remove this file from build/Jamfile.v2 and report the test-result on boost-track !" What is the complete path for the Jamfile.v2 that this error refers to? Any advice the community can offer would be greatly appreciated. Sincerely, -Axel

2 1

[thread] Mass test failures on clang
by Andrey Semashev 13 Jun '14

13 Jun '14

Hi, I'm seeing mass test failures in Atomic and Log both in develop and master. E.g.: http://www.boost.org/development/tests/develop/developer/atomic.html http://www.boost.org/development/tests/master/developer/atomic.html The logs are not descriptive (as usual) but point to Thread compilation: http://www.boost.org/development/tests/develop/developer/output/teeks99-04b… Could this be resolved? The freeze deadline is nearing, so I'd like to see my test results at least once before it is reached.

4 12

Code review for bug no. 7396
by ullas srinivas 13 Jun '14

13 Jun '14

Hi, I have fixed bug no. 7396 Bug # 7396 :filesystem::path::remove_all(path, error_code) throws filesystem_error exception Description : Several methods in filesystem::path, including remove_all, have an overload in which an extra error_code& argument is taken. According to the docs, this is supposed to cause failure (other than failure to allocate storage) to be reported in the error_code rather than as a thrown filesystem_error exception. However, remove_all can still throw filesystem_error exceptions because it uses a directory_iterator internally but makes no attempt to catch exceptions thrown by it. For example, if a subdirectory is deleted by another thread or process just before remove_all tries to list its contents, directory_iterator_construct will throw a filesystem_error that propagates up to remove_all's caller. As a side note, I think path and directory_iterator are both excessively exception-happy. It makes them painful to use. Root Cause : The exceptions thrown by fs::directory_iterator were not handled in remove_all_aux function of operations.cpp file. Fix: The exceptions thrown by fs::directory_iterator are handled by catching the exception and proper ly assigning error values . Try-catch statement has been put inside remove_all_aux function of operations.cpp file. I kindly request you to please find the patch file attached and review the bug Regards Ullas

1 0

[test] Compilation errors on MinGW 4.8.1
by Adam Wulkiewicz 12 Jun '14

12 Jun '14

Hi, When I try to compile Boost.Test (develop) tests or any other tests using execution_monitor on MinGW-GCC 4.8.1 I get the following errors: ..\..\../boost/test/execution_monitor.hpp:364:27: error: 'FE_DIVBYZERO' was not declared in this scope BOOST_FPE_DIVBYZERO = FE_DIVBYZERO, ^ ..\..\../boost/test/execution_monitor.hpp:365:27: error: 'FE_INEXACT' was not declared in this scope BOOST_FPE_INEXACT = FE_INEXACT, ^ ..\..\../boost/test/execution_monitor.hpp:366:27: error: 'FE_INVALID' was not declared in this scope BOOST_FPE_INVALID = FE_INVALID, ^ ..\..\../boost/test/execution_monitor.hpp:367:27: error: 'FE_OVERFLOW' was not declared in this scope BOOST_FPE_OVERFLOW = FE_OVERFLOW, ^ ..\..\../boost/test/execution_monitor.hpp:368:27: error: 'FE_UNDERFLOW' was not declared in this scope BOOST_FPE_UNDERFLOW = FE_UNDERFLOW, ^ ..\..\../boost/test/execution_monitor.hpp:370:27: error: 'FE_ALL_EXCEPT' was not declared in this scope BOOST_FPE_ALL = FE_ALL_EXCEPT, ^ When I use MinGW-GCC 4.8.0 shipped with Qt5 everything is ok. I though I'll let you know since AFAIS this toolset isn't tested. If you decided to take a look at this and needed a guinea pig I'd be here. Regards, Adam

3 6

Building Boost on Haiku
by Andrew Hudson 12 Jun '14

12 Jun '14

Hi, New booster here. I am building Boost 1.55 on Haiku X86 and have a build issue: -pthreads is not recognized by GCC 4.8 on Haiku X86 and gives an error. pthreads are supported by Haiku by default, so I need to suppress the compiler option but enable pthreads in the build. I used ./bootstrap.sh -PREFIX to set the default lib path as /usr is not used in Haiku Then I started the build with ./b2 install Where and how can I make this config change? I have little jam experience. I also need to suppress use of MPI as this is not ported yet. Many thanks!

1 0

Meeting C++ Schedule released
by Jens Weller 12 Jun '14

12 Jun '14

Hello C++ & Boost Community, since last week the schedule for Meeting C++ is released: http://meetingcpp.com/index.php/schedule14.html Like last year Meeting C++ will feature 21 Talks in 3 Tracks, the conference will be opened by Scott Meyers, the closing Keynote will be given by Hartmut Kaiser. This years Theme Track is "Scientific Programming with C++". Also, if your are a student, you have the chance to participate in our student program which will give 50 Students access to the conference: http://meetingcpp.com/index.php/newsreader/items/meeting-cpp-2014-the-stude… kind regards, Jens Weller

1 0

[config] config_test fails on g++ 4.8/4.9
by Peter Dimov 12 Jun '14

12 Jun '14

... due to In file included from ../libs/config/test/config_test.cpp:376:0: ../libs/config/test/boost_no_lambdas.ipp: In function ???int boost_no_cxx11_lambdas::test()???: ../libs/config/test/boost_no_lambdas.ipp:21:4: error: expected primary-expression before ???void??? (void)[](){}; ^ ../libs/config/test/boost_no_lambdas.ipp:21:4: error: expected ???)??? before ???void??? I'm not sure why.

3 5

[review] Convert library
by Jeroen Habraken 12 Jun '14

12 Jun '14

Hi, As promised my review of the boost::convert library. Note that the questions were answered in a seemingly random order, thus I hope it all comes together. Secondly, being the author of the boost::coerce library [2][3] I may be a little biased at times, please forgive me. -- What is your evaluation of the design? There are two parts to this, the design of the backend and the design of the interface that the user predominantly sees. I have little to say on the first, the notion of multiple backend converters is a big step forwards and their interface is sane. I'm far less convinced when it comes to the user-facing interface as I believe the simple tasks should be simple and intuitive, whereas the harder tasks may be harder. The most trivial use of boost::convert, and boost::lexical_cast and boost::coerce simply don't compare in my opinion. boost::cstringstream_converter cnv; int i = boost::convert<int>::from("23", cnv).value(); versus int i = boost::lexical_cast<int>("23"); int j = boost::coerce::as<int>("23"); When the convert library makes it into boost I'd want to mentally deprecate lexical_cast as a library I should use, and always use convert instead. This means convert should have a default converter, which may well be backed by lexical_cast with an interface such as: int i = boost::convert<int>::from("23").value(); This still doesn't completely satisfy me as I'd like to write int i = boost::convert<int>::from("23"); but it'd be an improvement in my opinion. Now I'm aware lexical_cast doesn't have a non-throwing interface, and it probably never will, but I've solved the problem as follows in boost::coerce: int i = boost::coerce::as_default<int>("XXX"); int j = boost::coerce::as_default<int>("XXX", tag::hex()); int k = boost::coerce::as_default<int>("XXX", 23); int l = boost::coerce::as_default<int>("XXX", tag::hex(), 23); The former two returning the default-constructed int, 0, the latter two returning 23. That said, I'll be the first to admit the coerce interface isn't perfect, the fact that I need SFINAE to distinguish between as_default calls with two parameters, the second either being a tag (somewhat similar to your converters but not quite) or the default value goes to show just that. However I'd prefer int i = boost::convert<int>::from("23", cnv); int i = boost::convert<int>::from_default("23", cnv, 0); to the current interface using value_or(0). This is subjective though, and quite possibly a matter of taste. In summary, before this turns into too long a rant, I think the current user-facing interface can be improved substantially, but I'm well aware this is subjective. -- What is your evaluation of the implementation? I've only had a quick glance at the code and it still looks fine. The gripe I had two years ago regarding the use of reserved names (include guards prefixed with "__") has been fixed. A few comments though: In the boost::lexical_cast based converter there is a try { } catch (...) { } which I believe to be an overly broad catch as lexical_cast explicitly throws a boost::bad_lexical_cast. If in an unlikely event a std::bad_alloc were to be thrown for example I'd rather not have boost::convert hide it from me. In the std::strtol based converter errno isn't checked, and it must be noted that strtol accepts leading whitespace which may or may not be wanted. I've implemented what I believe to be a correct converter using strtol which checks for the leading whitespace in [0], but it comes with no guarantees as it's quite tricky indeed. The new C++11 wrapper std::stol and friends in [1] may be of use here, but unfortunately they only have a throwing interface. All converters are added to the main boost namespace which is crowded enough as it is -- hi boost::_1 --, and libraries should add their functionality to their own namespaces in my opinion. With the current design it's not possible to add them in the boost::convert namespace but I believe they should be in their own namespace, may I suggest boost::converter. It must be said that the first two comments are minor at best, the last regarding the namespace is more important but potentially quite trivial to fix. -- What is your evaluation of the documentation? I've found it to be very hard to write documentation as the library author as at some point you're so intimately familiar with your library that it's hard to get a feel for what the user needs. Whilst there are some rough edges I think the current documentation is decent enough for it not to pose a problem. Again a few comments: The motivation should probably be addressed first, not near the end. The printf and std::strtol based converters aren't documented, and the converters should probably be grouped into a sub-section along with an explanation of how to write your own. Last of all I'd like to see an examples directory showing the examples from the documentation, you already have a test/encryption.hpp which probably belongs there. -- What is your evaluation of the potential usefulness of the library? In the previous review I've argued the library its functionality should be added to boost::lexical_cast. Whilst I still hold that position for the previous version of the library I believe this is no longer the case for the present version, largely due to the added support for multiple backends. There would be no practical way for lexical_cast to add this, and I believe it to be very useful indeed. -- Did you try to use the library? With what compiler? Did you have any problems? I've tried the library with Clang 3.2 and 3.4, and GCC 4.6 and 4.8 on Mac OS X 10.9.3 and the examples from the documentation using the sstream converter compile and run fine. When I tried the printf_converter something as simple as: #include <boost/convert/api.hpp> #include <boost/convert/converter/printf.hpp> int main(int, char *[]) { return boost::convert<int>::from("23", boost::printf_converter()).value(); } failed to compile. It's missing includes as adding the following to converter/printf.hpp fixes the problem: #include <boost/mpl/find.hpp> #include <boost/mpl/vector.hpp> This probably indicates that you're trying to test too much in a single file, and had the includes included via a different boost library. In the previous review I noticed that boost::convert<int>::from('1', cnv).value() spew a rather long error message. This has since been fixed, the error message is now considerably shorter making it easier -- will it ever be easy with C++ -- to figure out what's going on. I must note here that the error message the latest versions of GCC produced is actually easier to figure out than the one Clang produced. -- How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? Something between a quick reading and an in-depth study, now probably leaning towards the latter. -- Are you knowledgeable about the problem domain? As the author of boost::coerce, which I've admittedly ignored for far too long, I'm familiar with the conversion domain. Consequently I've seen the pitfalls and endured the hardships in designing and implementing such a library, my utmost respect for having it reviewed not once, but twice! And finally: -- Do you think the library should be accepted as a Boost library? In my previous review this was a straight no, stating that the functionality should be added to boost::lexical_cast. With the current design supporting multiple backends this no longer holds true as I've stated in the evaluation of the potential usefulness of the library. Again, the library is quite useful, but, I so strongly disagree with the current user-facing interface that I can't straight-out accept it. Once the library is accepted this interface is set in stone and like marriage it's "speak now or forever hold your peace". As such I'm voting YES, CONDITIONALLY on the interface being simplified for the seemingly simple cases as most of my other comments were minor or quite trivial to fix. With that out of the way I'd like to propose the following if you're interested. Let's have a look at whether it may be possible to merge the functionally of boost::convert and boost::coerce, as they seem to have grown towards each other with the possibility to support multiple backends. Two years ago I'd never have proposed this, but I've mellowed a bit since then. You seem to have focussed on backends primarily backed by std::stringstream and friends whereas I have focussed on a backend backed by boost::spirit. These may end up complementing leading to a single library capable of supporting both, being more generic and powerful to the user when done right. Regardless of whether we end up going this way I'd love to have a discussion on the interface, either on the mailing list or offline as this is currently a major stumbling block for me. Jeroen [0] https://github.com/VeXocide/coerce/blob/master/libs/coerce/example/backend.… [1] http://en.cppreference.com/w/cpp/string/basic_string/stol [2] https://github.com/VeXocide/coerce/ [3] http://vexocide.org/coerce/

15 78

Even newer dependency report
by Peter Dimov 12 Jun '14

12 Jun '14

Shows significant progress. http://www.pdimov.com/tmp/report-d6c23cf/module-overview.html http://www.pdimov.com/tmp/report-d6c23cf/module-levels.html

2 3

a new library Global Object Manager submission interest check
by George Georgiev 11 Jun '14

11 Jun '14

Hi, I have code that deals with problems related to initialization of global objects (singletons). 1. Multi-threading - problems occurring in some singleton patterns based on the fact that local for a function or method static variables are not initialized in a thread safe manner 2. Initialization order - there is no multi-platform/multi-compiler standard way to control the global objects initialization order 3. Static linking of global objects code without need - some patterns result in global objects to be linked in the final executable, even if they are provided from static libraries and the code that uses them is not in use 4. Capability for easy replacement of a global implementation object with a mock object I was struggling with shutdown issues in complex c++ application for years in several different projects. With the solution I come up a few years ago I have no issues in any project I have used it. Please let me know if this is something of interest to the boost community. Note that the boost singleton pattern used for path_locale (boost filesystem path) is having the multi-thread issue I mentioned in point 1. This is a small test that demonstrates the problem: https://github.com/ggeorgiev/boost-filesystem-singletons/blob/master/filesy… Thanks, George

3 10

[range] why not adding conversion operator std::pair<FTI.FTI> to boost iterator_range
by Andreas Fabri 11 Jun '14

11 Jun '14

Wouldn't it be a good idea to add a conversion operator to the class iterator_range? This would allow to write functions returning a range, instead of a pair of iterators, but boost::tie would still work with it. Best regards, andreas -- Andreas Fabri, PhD Chief Officer, GeometryFactory Editor, The CGAL Project phone: +33.492.954.912 skype: andreas.fabri

3 4

[BGL]
by Pablo Madoery 11 Jun '14

11 Jun '14

Hello, I Have 2 graphs: graph1 and graph2, and two sets of edge descriptors. One set is associated to edges of graph1 and another set associated to edges of graph2. I don't understand why is it possible to access information about edges of graph2 by using graph1 and the edge descriptors of graph2. I realized of that because of an own mistake when using graphs. What I would like to know is why is that possible to do and if it should be an exception that can handle this situation. I send the code I was using to test this: #include <iostream> #include <boost/graph/adjacency_list.hpp> #include <boost/graph/graphviz.hpp> #include <fstream> #include "GraphInfo.h" using namespace std; using namespace boost; typedef adjacency_list<setS, vecS, bidirectionalS, VertexInfo, EdgeInfo> Graph; void printGraph(Graph graph, string file) { ofstream ofs(file.c_str()); dynamic_properties dp; dp.property("node_id", get(vertex_index, graph)); dp.property("label", get(&EdgeInfo::weight, graph)); write_graphviz_dp(ofs, graph, dp); } int main() { Graph graph1; Graph::vertex_descriptor a1 = add_vertex(graph1); Graph::vertex_descriptor b1 = add_vertex(graph1); Graph::vertex_descriptor c1 = add_vertex(graph1); Graph::edge_descriptor e1 = (add_edge(a1, b1, graph1)).first; Graph::edge_descriptor e2 = (add_edge(b1, a1, graph1)).first; graph1[a1].id = 10; graph1[b1].id = 20; graph1[c1].id = 30; graph1[e1].weight = 1; graph1[e2].weight = 2; Graph graph2; Graph::vertex_descriptor a2 = add_vertex(graph2); Graph::vertex_descriptor b2 = add_vertex(graph2); Graph::vertex_descriptor c2 = add_vertex(graph2); Graph::vertex_descriptor d2 = add_vertex(graph2); Graph::edge_descriptor e4 = (add_edge(c2, b2, graph2)).first; Graph::edge_descriptor e5 = (add_edge(b2, c2, graph2)).first; Graph::edge_descriptor e6 = (add_edge(d2, a2, graph2)).first; Graph::edge_descriptor e7 = (add_edge(a2, d2, graph2)).first; graph2[a2].id = 10; graph2[b2].id = 20; graph2[c2].id = 30; graph2[e4].weight = 13; graph2[e5].weight = 14; graph2[e6].weight = 15; graph2[e7].weight = 16; // WHY IS THIS POSSIBLE TO DO // IT IS ASKING FOR AN EDGE OF GRAPH2 BUT USING GRAPH1 ??? double weight = graph1[e7].weight; cout<<"weight: "<<weight<<endl; printGraph(graph1, "graph1.dot"); printGraph(graph2, "graph2.dot"); cout << "end" << endl; return 0; } Thank you very much

1 0

[pimpl] No documentation for pointer semantics
by Edward Diener 10 Jun '14

10 Jun '14

The documentation for "Pimpl with Value Semantics" has: "and was deployed in the previous chapter for the Pimpls with pointer semantics..." but there is no previous chapter about Pimpl with pointer semantics. From that point on the documentation of "Pimpl with Value Semantics makes no sense to me and I do not know what is being explained.

8 24

[Modularization] new Memory module
by Vicente J. Botet Escriba 10 Jun '14

10 Jun '14

|What about creating a Memory module containing| most of the things the standard defines in <memory> except maybe what is already in SmartPptr, e.g. ||* boost/interprocess/allocators/*|| |* boost/intrusive/pointer_traits.hpp Vicente |

5 22

Tick: Trait instrospection library for C++14
by paul Fultz 10 Jun '14

10 Jun '14

Hi, I developed a trait introspection library for C++14 based on Eric Niebler's concept checking, here: https://github.com/pfultz2/Tick So you can build a simple `is_incrementable` trait like this: TICK_TRAIT(is_incrementable) { template<class T> auto requires(T&& x) -> TICK_VALID( x++, ++x ); }; Then use it like this: static_assert(is_incrementable<T>(), "Not incrementable"); Also, you can validate the return of an expressions like this: TICK_TRAIT(is_equality_comparable) { template<class T, class U> auto requires(T&& x, U&& y) -> TICK_VALID( returns<bool>(x == y), returns<bool>(x != y) ); }; You can also match against another trait using placeholder expressions: TICK_TRAIT(is_incrementable) { template<class T> auto requires(T&& x) -> TICK_VALID( return<std::is_integral<_>>(x++), return<std::is_integral<_>>(++x) ); }; Any feedback would be appreciated. Also, I don't knw if there would be any interest in incorporating this into boost. Thanks, Paul

7 13

[config] RTTI detection on Intel C++
by Peter Dimov 10 Jun '14

10 Jun '14

I was going to prepare a simple pull request that basically added #if !defined(__RTTI) && !defined(__INTEL_RTTI__) && !defined(__GXX_RTTI) && !defined(_CPPRTTI) #define BOOST_NO_RTTI #define BOOST_NO_TYPEID #endif to intel.hpp, but then I saw that this file doesn't contain any logic for BOOST_NO_EXCEPTIONS, relying instead on common_edg.hpp to check __EXCEPTIONS. So I wonder whether the preferred approach wouldn't be to check __RTTI in common_edg.hpp instead. Opinions? There's also a slight complication here because I suspect that when Intel is in Microsoft mode, when RTTI is off it will still support typeid, as MSVC does; so just BOOST_NO_RTTI would need to be defined, and not BOOST_NO_TYPEID.

2 2

quickbook equivalent of <simplesect>?
by Peter Dimov 10 Jun '14

10 Jun '14

Does Quickbook support <simplesect> or an equivalent? This is useful for the 'Authors' sections in Core, which don't need to clutter the ToC.

2 9

documentation (ToC) question
by Peter Dimov 10 Jun '14

10 Jun '14

When using Quickbook/BoostBook, how can a section ToC have two levels instead of just one? That is, if we have [library Boost.Core] [section:addressof addressof] [section Header 1] [section Synopsis] [section Example] [section Header 2] [section Synopsis] [section Example] how can the ToC of [section:addressof] show the Synopsis and Example nested within Header 1 and Header 2? I have tried various combinations of generate.section.toc.level, toc.max.depth, toc.section.depth, but nothing seems to produce the result I want.

4 7

[modularization] Recommendations
by Stephen Kelly 10 Jun '14

10 Jun '14

Hello, My last set of recommendations is here: http://thread.gmane.org/gmane.comp.lib.boost.devel/245078/focus=245806 The current graph of strongly connected modules is: http://www.steveire.com/boost/2014_june8_all.dot http://www.steveire.com/boost/2014_june8_all.png The type_traits mpl typeof core form a closed cylce. I consider this a small problem and I recommend deferring efforts to resolve it for now and focusing on the other edges which impact the rest of the graph. It may not be realistic to resolve every cycle or doing so may involve merging modules etc. I recommend deferring that discussion/work until after the major cycle-forming-edges are resolved. Group the above in the graph as a single node for now, removing many cycles: http://www.steveire.com/boost/2014_june8_with_kernel.png http://www.steveire.com/boost/2014_june8_with_kernel.dot Recommendation 1) Move parenthesized_type.hpp from parameter to core This removes the dependency from concept_check on parameter. Recommendation 2) Move implicit_cast.hpp and cast.hpp from conversion to core This also requires moving select_type.hpp from detail to core. This allows removal of the dependencies from iterator and range to conversion. As a side effect, it leaves lexical_cast as the only remaining public header in the conversion library. You can decide what impact that has for the recent 'Extracting lexical_cast from conversion' discussion. This requires removing the include of numeric/conversion/cast.hpp from cast.hpp. The content of that was moved to the numeric library in 2005 and the include was left behind for source compatibility. The result of the above recommendations is: http://www.steveire.com/boost/2014_june8_conversion_rdep.png http://www.steveire.com/boost/2014_june8_conversion_rdep.dot Recommendation 3) Remove use of algorithm from range Range includes boost/algorithm/string/config.hpp for no known purpose. According to git log -S BOOST_STRING_TYPENAME that define was never used in the range library. According to the history of boost/algorithm/string/config.hpp it never really had anything else useful. It might have made sense to include it for the Borland portability with the BOOST_STRING_TYPENAME, but that define was never used in range. Simply remove the use of the boost/algorithm/string/config.hpp header. Use boost/type_traits/detail/yes_no_type.hpp instead of boost/algorithm/string/yes_no_type.hpp in include/boost/range/detail/collection_traits_detail.hpp The resulting strongly connected graph is http://www.steveire.com/boost/2014_june8_range_deps.png http://www.steveire.com/boost/2014_june8_range_deps.dot There are more recommendations which can be made to reduce the strongly connected graph further, but I think the above are enough for now, so let's see if we can get through those first. Thanks, Steve.

6 19

[testing] Dissapearing regression results
by Adam Wulkiewicz 10 Jun '14

10 Jun '14

Hi, I noticed that for the latest runs the tests of Geometry are missing. Surprisingly not all, 2 tests for geometry/index sublib are present. Initially I thought that it may be caused by the recent modularization but I didn't noticed any problems in any of the libraries I checked randomly. Besides, I made some changes in Geometry recently, which AFAIU shouldn't cause any problems, but I guess you may never know. What I changed was: - creation of some files - moving of some files - adding a Jamfile in a directory different than test directories (doc/src/docutils/tools/support_status) - uncommenting tests in file extensions/test/nsphere/Jamfile.v2 So I decided to try running the tests by myself. I tried: 1. Windows + GitBash -> a lot of "can't find xxx file" errors (b2 headers didn't work properly) 2. Windows + GitBash with admin rights -> exactly what can be seen in the tests, bjam.log shows that only 2 tests from Geometry was choosen for testing 3. Windows + cmd with admin rights -> everything is ok (in case you wanted to check it - runner Test2) 4. Linux -> also everything is ok (runner Test) Is it possible that I was lucky and something was fixed yesterday evening (between 2nd and 3rd attempt)? Might my changes cause some problems? E.g. because of some state kept by the runners? In Geometry we have Jamfiles not only in test and xxx/test directories but also in examples, docs and in the main module directory. May this cause some problems? At least for me, on Windows b2 headers now requires admin rights. Otherwise the links just aren't created. Is it because of the replacing hardlinks with symlinks? Another thing is that symlinks aren't properly created for all libraries. AFAIR previously something like this happened after the addition of sublibs file. I don't remember exactly but it was probably caused by the same names of the older tests and newer ones from different directories, so not the same issue? Is there something we could do about it? Regards, Adam

3 9

- Request to join the community maintenance team
by Neil Groves 10 Jun '14

10 Jun '14

Hi! Please may I would like to join all the cool kids in the community maintenance team?! I would like to assist on various maintenance issues and with the modularisation effort. I think this requires broader write access than I have at the moment as a maintainer of Boost.Range. It seems to me that joining the community maintenance team will both allow me to help more with general maintenance and assist with modularisation. If the correct procedure is to make different requests, then please let me know. Regards, Neil Groves

2 1

[pimpl] Boost.Pimpl review canceled
by Glen Fernandes 09 Jun '14

09 Jun '14

Hi everyone, Vladimir has elected to withdraw Boost.Pimpl submission and cancel the formal review. On behalf of Vladimir, thank you for the feedback provided in response to the pre-view announcement mail: it was especially useful to him. Best, Glen

1 0

[Modularization] About adding sub-modules?
by Vicente J. Botet Escriba 09 Jun '14

09 Jun '14

Hi, some libraries can be seen as a set of sub-modules, as it is Math, Numeric or Thread. Could we add these sub-modules ? * Chrono/Stopwatches * Thread/Executors * Detail/WinApi Best, Vicente

4 13

Re: [boost] [Modularization] new Memory module
by Vicente J. Botet Escriba 09 Jun '14

09 Jun '14

I forget to sent this message to the boost ML. Le 09/06/14 15:18, Vicente J. Botet Escriba a écrit : > Le 09/06/14 12:17, Ion Gaztañaga a écrit : >> El 09/06/2014 10:11, Vicente J. Botet Escriba escribió: >>> Le 04/06/14 13:27, Vicente J. Botet Escriba a écrit : >>>> |What about creating a Memory module containing| most of the things >>>> the standard defines in <memory> except maybe what is already in >>>> SmartPptr, e.g. >>>> >>>> ||* boost/interprocess/allocators/*|| >>>> |* boost/intrusive/pointer_traits.hpp >>>> | >>> Any comments on this new module? Ion? >> >> Thanks for the ping, I'm not closely following modularization threads. >> >> Interprocess allocators are only usable by Interprocess users, I >> don't think they should be outside. > > Sorry, I wanted to say container| > > <boost/container/allocator_traits.hpp>|| > <boost/container/scoped_allocator.hpp>||| > > >> intrusive::pointer_traits is usable from other libraries. Container >> uses it extensively, but Container heavily depends on Intrusive. I >> don't know if other libraries use it. > > Boost.Thread uses allocators for future<T>. >> >> We also have a portable allocator_traits implementation in >> Boost.Container that might be reusable by other boost containers. We >> need to see real use cases to see if this class makes sense in >> Boost.Memory or its place should be Container. > I'm for Memory as it is in the standard. See my use case for future<T> >> >> For Boost 1.56 we'll have new allocators in Boost.Container, and >> those take advantage of Boost.Container internals to offer >> reallocation, burst allocation, etc. They could be usable by other >> Boost containers, but they are still experimental and unless there is >> a strong need for that, I would not move them to a new module now. >> >> pointer_traits offers extensions not found in std::pointer_traits >> (like pointer casting). We need to to carefully think about this >> (Boost.Intrusive needs to make some conversions not covered by >> std::pointer_traits). >> >> In any case, if reusable, I would make a new library (with >> documentation and test cases), not only a new git module. >> > Agreed. >> So my opinion is: Don't move interprocess allocators, let's see if a >> strong need arises for a common pointer_traits/allocator_traits and >> we'll think about solutions. >> > We don't move nothing we can not do either because we are the owners > or because these are libraries managed by the community maintenance team. > > Please, take the time you need about this new module/library that > could contain things similar to the ones found in <memory> except the > smart pointer part. > > Best, > Vicente

2 1