- Boost - lists.preview.boost.org

[assert] Proposed assert submodule
by Beman Dawes 02 Jan '14

02 Jan '14

The release managers with help from Peter Dimov have been developing super-project workflow documentation. See https://svn.boost.org/trac/boost/wiki/SuperProjectWorkflow In that discussion, Peter wrote: >Hi everyone, > >As a first step of moving Boost.Assert out of Utility and into its own submodule, >I've extracted its files (along with the history) into a test repository of mine: > > https://github.com/pdimov/assert > >If you consider its contents acceptable, please let me know what should the procedure >be for moving this repository into boostorg and making it a proper submodule. I've take the liberty of moving this discussion to the main list for wider input on three questions. Please respond on this thread to the question asked in the subject line, and comment on "How to create a new submodule from existing submodule components" and Super-project workflow on their threads. Thanks, --Beman

1 0

[Trac] Captcha not working - blocking contributions
by Alexander Lamaison 02 Jan '14

02 Jan '14

I tried to include some code in a ticket (#9531, to be precise) and Trac tried to make me complete a captcha to prove I'm not spam. However, the captcha doesn't appear: https://drive.google.com/file/d/0B-RwWpWIiF0VRXVjTE5nM0VHekE/edit?usp=shari… Any ideas? Alex -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org)

1 1

[Boost.Container] documentation problems
by John M. Dlugosz 01 Jan '14

01 Jan '14

A slightly old version of the flat_map documentation <http://www.boost.org/doc/libs/1_49_0/doc/html/boost_container_header_refere…> defines flat_map's Pred wrong: template<typename Key, typename T, typename Pred = std::less< std::pair< Key, T> >, typename A = std::allocator<T> > class flat_map; It should be std::less<Key>. Why do I care about a slightly old version, you might ask? Well, the current version doesn't seem to document it at all! If I go to the "latest version" link, <http://www.boost.org/doc/libs/1_55_0/doc/html/boost_container_header_refere…> doesn't show any definition for flat_map itself, just for comparison operators and other non-member templates. I can't find any means of navigating into the actual documentation for the class members, assuming it still exists. This is generally true for the other containers on that web page.

2 1

[git] Bumping git version requirement to 1.7.10
by Beman Dawes 01 Jan '14

01 Jan '14

https://svn.boost.org/trac/boost/wiki/Git/GitHome documents Boost's version requirement for Git, currently at 1.7.3. The regression scripts are using the clone --single-branch option, which became available at git 1.7.10, so we are planning to bump the version requirement. Done anyone have a problem with this? --Beman

6 11

[urgent] Testing help needed..
by Rene Rivera 31 Dec '13

31 Dec '13

I finally have the changes to the regression scripts sufficiently complete that I've managed to do a few minimal cycles of regression testing from the git repos. I now need some help in various ways: 1. General testing.. I need some of the regular testers to do runs with their setups with the new scripts. To test I suggest starting from a new testing location. And follow the usual instructions except get the run.py script from < https://raw.github.com/boostorg/boost/develop/tools/regression/src/run.py>. The options are exactly the same as the SVN version of the scripts (the --tag is mapped to master or develop as needed). If you run patch scripts you will have to adjust paths for the new arrangement. In particular the boost tree is now checked out to <testing-root>/boost_root. 2. Non-nix testing.. I don't have the time or resources available to check if the scripts and git invocations work on Windows. I need one person to test and likely make changes to the regression script to do the right things on Windows. Testing should be the same as above. But doing changes locally and testing them is challenging. The procedure I use is (as shell commands): > mkdir testing-dev > cd testing-dev > link <BOOST_DEVELOP>/tools/regression/src/run.py run.py > ln -s < BOOST_DEVELOP>/tools/regression/xsl_reports xsl_reports > ln -s < BOOST_DEVELOP>/tools/regression/src tools_regression_src > ./run.py --runner=<RUNNER_NAME> --skip-script-download --use-local That lets you edit the regression.py and run.py scripts in your local develop checkout. The options make it skip most of the run.py code, but otherwise make it behave as the regular testing except using your local changes. If you need to test changes to run.py in the normal use case you will have to commit+push the changes and then test. 3. Report generation.. It seems that the reports are failing to get generated for some reason. I suspect that the new scripts putting the git commit SHAs as the tested version number are messing up the results generation. I need someone familiar with the result generation to fix this. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

4 6

[Boost][Proto] BOOST_PROTO_USE_NORMAL_RESULT_OF seems incorrectly defined
by Hui Li 31 Dec '13

31 Dec '13

In proto/proto_fwd.hpp, based on how the macro BOOST_PROTO_USE_NORMAL_RESULT_OF is used, it's meant to be defined when the compiler supports c++11 decltype and implements N3276, for example, BOOST_PROTO_RESULT_OF is boost::result_of when BOOST_PROTO_USE_NORMAL_RESULT_OF is defined. However, its definition seems incorrect, and is inconsistent with the comments next to it. #ifdef BOOST_NO_CXX11_DECLTYPE_N3276 ^^^^^^ should this be #ifndef ? # // Proto can only use the decltype-based result_of if N3276 has been # // implemented by the compiler. # // See http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2011/n3276.pdf # ifndef BOOST_PROTO_USE_NORMAL_RESULT_OF # define BOOST_PROTO_USE_NORMAL_RESULT_OF # endif #endif Am i missing something here? Hui

2 2

Versioning of individual modules
by Peter A. Bigot 31 Dec '13

31 Dec '13

Forked from Re: [boost] [git] tagging in modules Context below. Guided questions follow the quoted context. On 12/30/2013 11:02 AM, Beman Dawes wrote: > On Thu, Dec 26, 2013 at 7:24 PM, Peter A. Bigot <pab(a)pabigot.com> wrote: > >> Not relevant to the original thread, but since I just noticed it: >> >> git-push by default does not push tags: you need to specifically ask for >> the tag to be pushed (by name), or use --tags. So this sequence does >> nothing visible: >> >> git tag -a 1.2 >> git push >> >> Personally I'd prefer if tag symbols were a little more informative than >> "1.2", and followed a pattern that places them in a namespace reserved for >> the module, such as timer-1.2. Because tags aren't normally pushed, >> they're useful for individual developers to use as markers. However, >> git-pull will automatically retrieve tags attached to commits that are >> fetched unless --no-tags is given, so if a repository (from boostorg, or >> another developer) defines (or moves) a tag it might overwrite your local >> tag without warning. So it's important to know what tags you can expect >> might conflict with those in a remote repository to avoid conflicts. >> > Updated: > > https://svn.boost.org/trac/boost/wiki/StartModWorkflow#Releasetags > <https://svn.boost.org/trac/boost/wiki/StartModMaint#Lightweightlibraryrelea…> > https://svn.boost.org/trac/boost/wiki/StartModMaint > #Lightweightlibraryrelease<https://svn.boost.org/trac/boost/wiki/StartModMaint#Lightweightlibraryrelea…> > > >> I'd also really like to see any module that uses internal versioning also >> provide a mechanism by which code can determine which version is being >> used. E.g., for the above there ought to be a <boost/timer/version.hpp> >> header which has: >> >> #define BOOST_TIMER_VERSION_MAJOR 1 >> #define BOOST_TIMER_VERSION_MINOR 2 >> >> Otherwise I'm not seeing any value for module-level version tags in the >> repository. Matter of taste, though. >> > While I'm sympathetic, we should get comments and buy in from library > maintainers before recommending this. Are a lot of libraries already doing > something similar? If so, what? And do we follow Rene's suggestion and > recommend Predef? Could you please start a separate discussion with a > subject that let's maintainers know this is affects them? Thanks! > > There is a tangentially related issue: The git and modular boost related > docs are being developed without any reference to or updating of existing > developer documentation. We need to get that underway. Ditto web site > changes. > > >> I would expect, on superproject release, that each module would continue >> to receive a boost-X.Y tag marking the module commit that corresponds to >> the submodule SHA1 used for the release. This is another reason to make >> sure module-level tags are clearly distinguished (lest somebody think the >> tag corresponds to a boost version rather than a module version). >> > Sounds about right, but we would need to work out the mechanics. Who does > the tagging? A script release managers run? General questions related to this topic: *) When a module pushes to master, must all commits that appear directly on the master branch be considered "stable" or is it only necessary that the HEAD always be stable? The context for this is actually in "[git] avoiding fast forward merges" at http://lists.boost.org/Archives/boost/2013/12/210110.php. It's primarily a superproject decision but module maintainers should be aware of it. *) Should all modules be assigned version numbers, or may module "releases" be unversioned master commits that "inherit" the Boost version when incorporated into a release? My opinion: Don't bother unless there's clear evidence that the module will be shipped or used outside of a versioned Boost installation. *) If a module has a module-specific version number, should it be expected to provide that version number in a standard location and name so that preprocessor directives interrogate and adapt user code based on it? What mechanism should be used for this? My opinion: Absolutely. If the module is named timer (sorry I keep picking on that module), then I would like to see: #include <boost/timer/version.hpp> define a macro BOOST_TIMER_VERSION which has an ordinal integer value that may be used in comparisons in preprocessor conditionals to select available features. I support Rene Rivera's suggestion to use the BOOST_VERSION_NUMBER macro from Boosts.Predef to accomplish this. Of course, if no modules need module-level versioning, this won't be necessary. *) What syntactic format should be used for git tags that record version numbers? My opinion: If the module is named timer, and the version number is 1.2, the tag timer-1.2 would be created and pushed to the boostorg timer repository by the timer maintainer. *) By what process is the superproject version associated with the commit on the master branch that is selected for a given Boost release? My opinion: If the Boost release is 1.56, every module incorporated into that release has a boost-1.56 tag created, identifying the master branch commit that is incorporated into the release. This tag would be added by the release manager when the superproject is tagged using a trivial "git submodule foreach git tag boost-1.56" in the superproject master branch followed by "git submodule foreach push origin boost-1.56" after sanity checks. Other inputs? Peter

2 3

[git-help] clone asks for passphrase for every library
by Nathan Ridge 30 Dec '13

30 Dec '13

Hello, I'm trying out git + modular boost for the first time. When I try to clone the repository as described here [1], I run into a problem where the recursive clone process asks me for my SSH key's passphrase for every submodule (library) that it is checking out. Is there a way to avoid this? Thanks, Nate [1] https://svn.boost.org/trac/boost/wiki/TryModBoost

4 4

[GIL] Pixel Layout Padding?
by TONGARI J 30 Dec '13

30 Dec '13

Hi there, The current gil::pixel design has a deficiency that you can't specify the align of pixel, for example, you can't have an RGBX pixel in GIL where X is padding. An alternative is to introduce a dummy channel for X, but that doesn't seem to be a good idea as we don't want to mess up the color space. So, maybe it'd be better to extend the current design, say, pixel<ChannelValue, Layout>, to something like pixel<ChannelValue, Layout, Align>. Then we can specify RGBX as pixel<uint8_t, rgb_layout_t, 4>, or XRGB as pixel<uint8_t, rgb_layout_t, -4> where minus means left justify. Ideas?

3 11

[git-help][urgent] How do I ignore an upstream change to one file?
by Rene Rivera 30 Dec '13

30 Dec '13

When I attempt to do an update of the boost superproject I get and error: Froggy:develop grafik$ git pull error: Your local changes to the following files would be overwritten by merge: tools/regression/src/regression.py Please, commit your changes or stash them before you can merge. Aborting Froggy:develop grafik$ I know I've made changes. I also know I don't want to throw away my changes. I also know that I don't want to merge the upstream changes to that one file. Hence.. How do I do a pull and have git ignore the upstream of only that file? (i.e. throw away the upstream changes because I know that my changes supersede them) Rene. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

8 13

[git] New doc page: Cautions and Suggestions
by Beman Dawes 30 Dec '13

30 Dec '13

https://svn.boost.org/trac/boost/wiki/GitCautions\ Corrections, comments, and suggestions welcome. --Beman

2 2

[git] Post svn conversion merge point instructions moved
by Beman Dawes 30 Dec '13

30 Dec '13

The post svn conversion merge point instructions have been moved to a separate page. See https://svn.boost.org/trac/boost/wiki/PostCvtMergePoint A set of preparatory steps suggested by Peter Dimov have been added. I'm unsure how Peter's prep steps interact with the actual merge point instructions. Particularly, what SHA is used for the merge point? Please take a look, and then suggest corrections or clarifications. Thanks, --Beman

2 2

[range] Should html docs be checked in?
by Mostafa 30 Dec '13

30 Dec '13

Can the maintainer(s) of range answer this question that came up in the documentation ML: On Sat, 28 Dec 2013 02:09:06 -0800, Daniel James <daniel(a)calamity.org.uk> wrote: > On 28 December 2013 00:15, Mostafa <mostafa_working_away(a)yahoo.com> > wrote: >> >> If html files, or any other files for that matter, are auto-generated >> then >> why are they included in the repo? The reason I ask because this >> difference >> in boostbook version causes a lot of extraneous noise when I do a git >> status. Instead of the three html files I was expecting to be modified >> when >> I changed a qbk file there are 153 extra html files that show up as >> modified. > > For many libraries they aren't. It's up to the library maintainer how > they're managed. What you can do is rebuild the documentation from a > clean checkout and commit that, then later edits shouldn't result in > so many changes.

5 9

[test] still broken in release
by Tim Blechmann 30 Dec '13

30 Dec '13

hi all, i've reported an issue before that boost.test in the release branch is pretty broken. *all* tests of the boost.heap testsuite segfault like this: --Program received signal SIGSEGV, Segmentation fault. 0x00000000005f4975 in boost::unit_test::test_suite::add (this=0x8cefa0, tu=0x9, expected_failures=0, timeout=0) at ../../../boost/test/impl/unit_test_suite.ipp:139 139 m_members.push_back( tu->p_id ); (gdb) bt #0 0x00000000005f4975 in boost::unit_test::test_suite::add (this=0x8cefa0, tu=0x9, expected_failures=0, timeout=0) at ../../../boost/test/impl/unit_test_suite.ipp:139 #1 0x00000000005fda9c in boost::unit_test::ut_detail::test_init_caller::operator() (this=0x8d4e08) at ../../../boost/test/impl/framework.ipp:96 #2 0x00000000006031a2 in boost::unit_test::ut_detail::invoker<int>::invoke<boost::unit_test::ut_detail::test_init_caller> (this=0x7fffffffc36f, f=...) at ../../../boost/test/utils/callback.hpp:42 #3 0x0000000000603071 in boost::unit_test::ut_detail::callback0_impl_t<int, boost::unit_test::ut_detail::test_init_caller>::invoke (this=0x8d4e00) at ../../../boost/test/utils/callback.hpp:89 #4 0x000000000060e03d in boost::unit_test::callback0<int>::operator() (this=0x7fffffffcfc0) at ../../../boost/test/utils/callback.hpp:118 #5 0x000000000060de8a in boost::detail::do_invoke<boost::scoped_ptr<boost::detail::translate_exception_base>, boost::unit_test::callback0<int> > (tr=..., F=...) at ../../../boost/test/impl/execution_monitor.ipp:281 #6 0x000000000060d1a8 in boost::execution_monitor::catch_signals (this=0x7fffffffcfd0, F=...) at ../../../boost/test/impl/execution_monitor.ipp:885 #7 0x000000000060d262 in boost::execution_monitor::execute (this=0x7fffffffcfd0, F=...) at ../../../boost/test/impl/execution_monitor.ipp:1211 #8 0x00007ffff7b0bf33 in boost::unit_test::framework::init (init_func=0x4e3f30 <init_unit_test()>, argc=1, argv=0x7fffffffd198) at ../../../boost/test/impl/framework.ipp:268 #9 0x00007ffff7b22267 in boost::unit_test::unit_test_main (init_func=0x4e3f30 <init_unit_test()>, argc=1, argv=0x7fffffffd198) at ../../../boost/test/impl/unit_test_main.ipp:177 #10 0x00000000004e3f62 in main (argc=1, argv=0x7fffffffd198) at ../../../boost/test/unit_test.hpp:59 -- boost.test in trunk works fine, though ... i wonder, will it eventually be merged to release? tim

7 28

[test] Interest in 'hamcrest'-style checks?
by Jared Grubb 29 Dec '13

29 Dec '13

I recently read "Modern C++ Programming with Test-Driven Development", and I really enjoyed this book and highly recommend it. One of the styles I saw for the first time was "hamcrest"-style assertions. ("Hamcrest" is an anagram of "matchers"; also see http://en.wikipedia.org/wiki/Hamcrest.) For a quick idea, imagine there is a BOOST_CHECK_THAT macro that looks like this: (excuse my choice of names here, we can pick better ones if people like the idea) BOOST_CHECK_THAT( str, IsEqualTo(expStr) ); BOOST_CHECK_THAT( str, HasSubstring(needleStr) ); BOOST_CHECK_THAT( str, Not(HasSubstring(badStr)) ); BOOST_CHECK_THAT( vec, Contains(42) ); Comparing them to current boost::test assertions, usually the two are directly equivalent, and it's just a matter of style. At first, I was unconvinced of a need for this. However, there are a few scenarios where the hamcrest-style actually are really helpful: BOOST_CHECK_THAT(vec, Any(Contains(42), Contains(-42)) ); BOOST_CHECK_THAT(str, All(StartsWith("abc"), HasSubstring("lmnop"), EndsWith("xyz")) ); BOOST_CHECK_THAT(count, All(GE(0), LT(10)) ); BOOST_CHECK_THAT(vec, HasSubsequence(otherVec) ); BOOST_CHECK_THAT(vec, Sorted(IsEqualTo({1, 2, 3})) ); BOOST_CHECK_THAT(optionalStr, Any(IsEqualTo(boost::none), Deref(IsEqualTo("str"))); Sure, almost all of this is already doable: BOOST_CHECK_EQUAL_COLLECTIONS( /* sorry, but I really dislike this one :) */ ); BOOST_CHECK( std::count(vec.begin(), vec.end(), 42) && std::count(vec.begin(), vec.end(), -42) ); And, yes, you can create a helper functors today: BOOST_CHECK( Contains(vec, 42) && Contains(vec, -42) ); But hamcrest still gives these advantages over even that: * Dont repeat yourself: -- the value under test appears only once in the check expression; this is really helpful if you want to test an expression ("future.get()") that can only be called once * Better diagnostics: -- when something fails, you can get a detailed error (eg: "blah does not contain the element blah" or "str does not start with blah") -- when you have "Any" conditions, "errors" get squashed if some other condition passes, but all are shown if none pass -- composed tests can provide nested diagnostics; eg: for All(A, Any(B,C)), you'd get something like "'...A...' is true, but none of { '...B...' , '...C...' } are true", but spread over many lines -- and even with indentation if we want * Intentional Asymmetry: Is it BOOST_CHECK_EQ(expected, actual) or (actual, expected)? It really doesnt matter in the end, but a message like "expected 34, got 33" is actually kinda nice. Putting the value under test at the start creates an asymmetry that helps guide the user to put the values in the "right" order. * Composability * Extendibility: once the facility is there, its actually really easy to write more ("CanLockMySemaphoreType(timeout)") I wasnt able to find any discussion on boost's list for this, so I thought I'd bring it up. As for difficulty, implementing the examples above is actually already quite easy using boost::test predicates, and the extra macro would be fairly simple to implement. Almost all the work would be in creating the library of matchers, which is the fun part :) What do you think? Jared

5 11

[TortoiseGit] Screen shots becoming available + submodule update bug
by Beman Dawes 29 Dec '13

29 Dec '13

I've started to post screen shots of TortoiseGit performing the various operations described in "Getting Started with Modular Boost Library Maintenance". See https://svn.boost.org/trac/boost/wiki/TortoiseGitLibMaint Since each screen shot takes a bit of time and effort, I'd like to hear the opinions from some from TortoiseGit users as to whether or not the screen shots seem worthwhile. I particularly wanted to get a screen shot of a submodule update, but hit a bug in TG's "Submodule update...". It was reported yesterday, and the TG folks have already identified the problem as a bug in a library named libgit2, and reported that to the libgit2 folks, citing the boost super-project as the test case. The libgit2 folks have already created a pull request with a patch, so let's hope the fix reaches us reasonably soon. --Beman

2 1

[boost.test] Correct usage?
by Philip Bennefall 29 Dec '13

29 Dec '13

Hello, I just started writing unit tests for a large project that I am involved in, and boost.test has been absolutely fantastic to work with so far. True the documentation could be clearer, but as far as functionality I am very much impressed with the library. I have a question though. I read the following: http://lists.boost.org/Archives/boost/2011/10/186439.php This concerns me. What is the status here? When I build boost_1_54_0, in my stage/lib directory I see: libboost_test_exec_monitor-vc100-mt-s-1_54.lib My test cases look as follows: #define BOOST_TEST_MODULE MyProgram #include <boost/test/unit_test.hpp> BOOST_FIXTURE_TEST_SUITE(basic_operations, basic_memory_logger) BOOST_AUTO_TEST_CASE( some_test ) { // ... // Using BOOST_REQUIRE_EQUAL, BOOST_CHECK_EQUAL, BOOST_CHECK, BOOST_REQUIRE_EQUAL_COLLECTIONS and friends here. } BOOST_AUTO_TEST_SUITE_END() My questions are: 1. Are all these macros still supported and not depricated? 2. Is the structure correct? Am I depending on something depricated? Am I including the right header? I am linking with the library mentioned above (via auto-linking), which is why I am concerned about deprication. Thanks in advance for any clarification on this. Kind regards, Philip Bennefall

3 2

[phoenix] how do i achieve this type of extension of phoenix
by Hui Li 28 Dec '13

28 Dec '13

I want to extend the phoenix library with my own expressions in a specific way. Would appreciate any help!! Thanks! The code below is what i want to achieve, with the intended behavior specified in the comments. The goal is to first build an expression (the expr0), and later bind some value to certain nodes and turn them into different types of nodes with internal states (expr1) but preserve the structure of the expression tree, and also be able to modify the internal states of those nodes. My question is, how to define myplus, mymult, myinit, and myreset to make it work? using boost::phoenix::arg_names::arg1; using boost::phoenix::arg_names::arg2; using boost::phoenix::arg_names::arg3; // how should i define myplus, mymult and myinit, so that // expr1 is arg1 + myplus_f<double>(3.0)(1,arg2) + mymult_f<double>(3.0)(2,arg3) auto expr0 = arg1 + myplus(1,arg2) + mymult(2,arg3); auto expr1 = myinit( expr0, 3.0 ); // evaluate expr1 with actual arguments double r = expr1(1,2,3); // modify the internally held values of myplus_f<double>(3.0) and mymult_f<double>(3.0) // so that expr1 becomes equivalent to arg1 + myplus_f<double>(5.0)(1,arg2) + mymult_f<double>(5.0)(2,arg3) myreset(expr1, 5.0); // evaluate with new value members of myplus_f and mymult_f double r2 = expr1(1,2,3); myplus_f and mymult_f are defined as follows: template < typename T > struct myplus_f { T value; explicit myplus_f(const T& v):value(v){} void reset(const T& new_value) { value = new_value; } template < typename Lhs, typename Rhs > auto operator()(const Lhs& lhs, const Rhs& rhs) const -> decltype(value+lhs+rhs) { return value + lhs + rhs; } }; template < typename T > struct mymult_f { T value; explicit mymult_f(const T& v):value(v){} void reset(const T& new_value) { value = new_value; } template < typename Lhs, typename Rhs > auto operator()(const Lhs& lhs, const Rhs& rhs) const -> decltype(value*lhs*rhs) { return value * lhs * rhs; } };

2 1

Getting Started with Modular Boost Library Maintenance
by Beman Dawes 27 Dec '13

27 Dec '13

I've been pecking away at "Getting Started with Modular Boost Library Maintenance". See https://svn.boost.org/trac/boost/wiki/StartModMaint I'd appreciate comments and corrections. One of the questions that came up was how to number releases for individual libraries. Say Boost.System wants to do a release before the next full Boost release ships. What do I call it? How do I document it? How do I tag it? Strawman proposal ------------------------ * Call it "Boost.System 1.55.1 Point Release". * Document it via the "readme" file that GitHub pesters you to add. Contents would give the title of the release and the release notes. * Create a gh-pages branch with the same release notice. * Tag it 1.55.1 Comments? --Beman

11 26

[Config] Failure with Clang-3.4 in C++14 mode
by Ben Pope 27 Dec '13

27 Dec '13

"clang++-3.4" -c -x c++ -std=c++1y -stdlib=libc++ -O0 -g -fno-inline -Wall -g -fPIC -DBOOST_ALL_NO_LIB=1 -I".." -o "/home/ben/development/boost/test/build/results/boost/bin.v2/libs/config/test/config_test.test/clang-linux-3.4~c14_libc++/debug/config_test.o" "../libs/config/test/config_test.cpp" In file included from ../libs/config/test/config_test.cpp:76: ../libs/config/test/boost_no_constexpr.ipp:37:3: error: no viable conversion from 'const boost_no_cxx11_constexpr::A' to 'int' X<a> xx; // OK: unique conversion to int ^ ../libs/config/test/boost_no_constexpr.ipp:27:14: note: candidate function not viable: 'this' argument has type 'const boost_no_cxx11_constexpr::A', but method is not marked const constexpr operator int() { return val; } ^ ../libs/config/test/boost_no_constexpr.ipp:28:14: note: candidate function not viable: 'this' argument has type 'const boost_no_cxx11_constexpr::A', but method is not marked const constexpr operator long() { return 43; } ^ In file included from ../libs/config/test/config_test.cpp:231: ../libs/config/test/boost_no_cxx11_user_lit.ipp:64:15: error: invalid operands to binary expression ('const boost_no_cxx11_user_defined_literals::my_literal' and 'boost_no_cxx11_user_defined_literals::my_literal') return ((a == my_literal(0x23)) && (b == my_literal(9))) ? 0 : 1; ~ ^ ~~~~~~~~~~~~~~~~ ../libs/config/test/boost_no_cxx11_user_lit.ipp:22:19: note: candidate function not viable: 'this' argument has type 'const boost_no_cxx11_user_defined_literals::my_literal', but method is not marked const constexpr bool operator==(const my_literal& a) { return val == a.val; } ^ ../libs/config/test/boost_no_cxx11_user_lit.ipp:64:42: error: invalid operands to binary expression ('const boost_no_cxx11_user_defined_literals::my_literal' and 'boost_no_cxx11_user_defined_literals::my_literal') return ((a == my_literal(0x23)) && (b == my_literal(9))) ? 0 : 1; ~ ^ ~~~~~~~~~~~~~ ../libs/config/test/boost_no_cxx11_user_lit.ipp:22:19: note: candidate function not viable: 'this' argument has type 'const boost_no_cxx11_user_defined_literals::my_literal', but method is not marked const constexpr bool operator==(const my_literal& a) { return val == a.val; } ^ ^ 6 warnings and 3 errors generated. Looks like a simple fix of marking the members const. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3598.html http://www.boost.org/development/tests/trunk/developer/output/BP%20x86_64%2… Ben

2 2

[boostbook] Unsupported doc elements.
by Mostafa 27 Dec '13

27 Dec '13

I was perusing Robert Ramey's very informative blincubator.com when I ran across this: "Though BoostBook specifies a large collection of tags to characterize documentation elements, the large majority of these are not used by Boost library documentation It seems that that they've been included in the hopes of being available for future use. This would be OK except for the fact that the attaching all these tags to one's documentation would be a huge job - which would yield no benefit with the current document preparation system. It's not clear from the BoostBook documentation which tags are used/useful and which should not be bothered with. This leaves one with questions about under what circumstances each tag should be used." Is the situation involving unsupported documentation elements still true? If so, can someone knowledgeable with the issue in the least identify which elements are supported and which are not? Any clarification appreciated, Mostafa

2 1

[PATCH Boost.smart_ptr] Add intrusive_ptr<>::release()
by Avi Kivity 26 Dec '13

26 Dec '13

This provides a way to escape from automatic reference counting, and taking manual control of the reference. Useful when interfacing to a C API that expects a pointer with an elevated reference count. Similar to std::unique_ptr<>::release(). --- include/boost/smart_ptr/intrusive_ptr.hpp | 7 +++++++ intrusive_ptr.html | 23 ++++++++++++++++++----- test/intrusive_ptr_test.cpp | 7 +++++++ 3 files changed, 32 insertions(+), 5 deletions(-) diff --git a/include/boost/smart_ptr/intrusive_ptr.hpp b/include/boost/smart_ptr/intrusive_ptr.hpp index a855a10..8c73fe2 100644 --- a/include/boost/smart_ptr/intrusive_ptr.hpp +++ b/include/boost/smart_ptr/intrusive_ptr.hpp @@ -151,6 +151,13 @@ public: return px; } + T * release() BOOST_NOEXCEPT + { + T * ret = px; + px = 0; + return ret; + } + T & operator*() const { BOOST_ASSERT( px != 0 ); diff --git a/intrusive_ptr.html b/intrusive_ptr.html index 562d27a..ef6238b 100644 --- a/intrusive_ptr.html +++ b/intrusive_ptr.html @@ -71,6 +71,7 @@ T & <A href="#indirection" >operator*</A>() const; // never throws T * <A href="#indirection" >operator-></A>() const; // never throws T * <A href="#get" >get</A>() const; // never throws + T * <A href="#release" >release</A>(); // never throws operator <A href="#conversions" >unspecified-bool-type</A>() const; // never throws @@ -174,11 +175,23 @@ intrusive_ptr & operator=(T * r);</pre> Throws: nothing. </blockquote> <h3><a name="get">get</a></h3> - <pre>T * get() const; // never throws</pre> - <blockquote> - Returns: the stored pointer. - Throws: nothing. - </blockquote> + <pre>T * get() const; // never throws</pre> + <blockquote> + Returns: the stored pointer. + Throws: nothing. + </blockquote> + <h3><a name="release">release</a></h3> + <pre>T * release(); // never throws</pre> + <blockquote> + Returns: the stored pointer. + Throws: nothing. + Postconditions: <code>get() == 0</code>. + Notes: The returned pointer has an elevated reference count. This + allows conversion of an intrusive_ptr back to a raw pointer, + without the performance overhead of acquiring and dropping an extra + reference. It can be viewed as the complement of the + non-reference-incrementing constructor. + </blockquote> <h3><a name="conversions">conversions</a></h3> <pre>operator unspecified-bool-type () const; // never throws</pre> <blockquote> diff --git a/test/intrusive_ptr_test.cpp b/test/intrusive_ptr_test.cpp index 614a9cb..90248fe 100644 --- a/test/intrusive_ptr_test.cpp +++ b/test/intrusive_ptr_test.cpp @@ -330,6 +330,13 @@ void test() BOOST_TEST(get_pointer(px) == px.get()); } + + { + boost::intrusive_ptr<X> px(new X); + X* released = px.release(); + BOOST_TEST(released->use_count() == 1); + delete released; + } } } // namespace n_access -- 1.8.3.1

7 15

Project for developing Binary Indexed Tree
by Arpit Mittal 26 Dec '13

26 Dec '13

Hi All, I am new to the group. I am interested to know that if developing a Binary Indexed Tree for Boost C++ will be a good project. Thanks and Regards Arpit Mittal

1 0

[quickbook] Broken link in repo.
by Mostafa 26 Dec '13

26 Dec '13

boost/tools/quickbook/index.html redirects to boost/doc/html/quickbook.html which redirects to http://boost-sandbox.sourceforge.net/doc/html/quickbook.html. The latter does not exist.

2 4

[git][multi_index] help merging from develop
by Joaquin M Lopez Munoz 26 Dec '13

26 Dec '13

Hi, I've tried following the instructions on https://svn.boost.org/trac/boost/wiki/StartModMaint but I obviously screwed up something. After creating my first merge point https://github.com/boostorg/multi_index/ commit/802543fd948b5cf41460addf2260693f08cf7f8d a subsequent merge from develop doesn't change any code: https://github.com/boostorg/multi_index/ commit/3239677c40b6e15d1bb49675cabb077460333538 even though branch develop is indeed different from (and more recent than) the code in master (it contains changes from about one month or so intended for Boost 1.56 that weren't published when the branch master was originally created) Heeeelp! Thanks for bearing with an incompetent Git user. Joaquín M López Muñoz Telefónica Digital

6 29

STL MAP Insertion and Updates ..!!
by Rahul Mathur 25 Dec '13

25 Dec '13

Hi, Looking for clue for below. Having a code which has to be inserted and updated with following status - 1. Insert with unique ID and initially with two values (viz . v1[1100] & v2[1000]) 2. If v1 [viz 1100] is NOT accepted exit. 3. Else value v2[1000] is accepted. With v2 being accepted, further insert with same unique ID on which v2 was accepted but now either with three values of v3[1001] or v4[1002] or v5[1003] and UPDATE the STL MAP. 4. Print the FINAL value (v2 or v3 or v5) of STL MAP with given unique ID. Did wrote below lines which works until value v1 [1000] insertion - --- #include <iostream> #include <algorithm> #include <map> #include <iterator> using namespace std; struct TBag { int UnqID; short value_code; TBag():UnqID(1234),value_code(1000){} }; TBag ms_var1; typedef std::map<int, short> map1; class Apple { map1 abc; public: void TypeInsert ( TBag *ms_var ); }; void Apple::TypeInsert ( TBag *ms_var ) { // Insert the 'UnqID' with messages of either TC = 1000 or 1100 only. typedef std::pair <map1::iterator, bool> itr; itr it1 = abc.insert( std::make_pair( ms_var->UnqID, ms_var->value_code ) ); typedef std::pair <map1::iterator, bool> itr; //Searching for value of Value Code = 1000 if (ms_var->value_code == 1100) { std::cout << "Value Error." << endl; exit (1); } if (it1.second) { // Checking correct insertion happened with 1000 std::cout << "Unq ID (" << it1.first->first << ") => " << "Value Code (" << it1.first->second << ")" << endl; std::cout << "The Status is .." << it1.first->first << " & " << it1.first->second << endl ; // INSERT now with Value code of either 1001 or 1002 or 1003 & finally UPDATE the STL MAP std::cout << "Final Status:" << endl ; for( map<int, short>::iterator iter = map1.begin(); iter != map1.end(); ++iter ) std::cout << iter->first << " " << iter->second << endl ; std::cout << "All Status successful." << endl; } else std::cout << "Status Error." << endl; } int main () { Apple ms; ms.TypeInsert( &ms_var1 ); return 0; } --- Any help is well appreciated ..:) ~ XoXo

2 1

[git] avoiding fast-forward merges
by Peter A. Bigot 25 Dec '13

25 Dec '13

Forked from Re: [boost] [git][multi_index] help merging from develop On 12/25/2013 06:03 AM, Daniel James wrote: > On 25 December 2013 11:57, Daniel James <daniel(a)calamity.org.uk> wrote: >> >> You can, but you don't need "-s ours": >> >> git checkout develop >> git merge master >> >> It should be a fast-forward merge. > > Oh sorry, I just remembered why I didn't suggest merging into develop. > The recommended work flow is not to do fast forward merges in order to > keep the two branches separate. Is this (keeping the two branches separate) the right rationale? I take "separate" to mean having no commit (SHA1) that is present on both branches (other than, for new modules, an initial master/develop branch fork which serves as the first merge base). A fast-forward merge necessarily places the same commit on both branches. git-flow recommends avoiding fast-forward merges to branch develop so the historical feature branch is preserved and to bundle the merge effect into a single commit, simplifying reversion. But this is more of a per-module traceability policy in the selected workflow than something that has a material effect on overall Boost process. In contrast, for Boost modules it's important not to do fast-forward merges to master, because a maintenance plan or email somewhere said super-project release managers may choose to select an earlier version on a module master branch to resolve integration failures.[*] To achieve that it must be possible for the manager to identify stable releases on the master branch, which would not be the case if a fast-forward merge added a commit series that did not stabilize until the final commit. The simplest derived requirement is that every commit on the master branch must represent a stable module, enforced by --no-ff. This I understood to be a strict requirement for the module master branch regardless of the module maintainers' chosen workflow within the module, but it does not affect workflow for develop. The effect of adopting these two practices may be that develop and master are kept separate. But that's not necessarily true if the develop branch itself is always kept at a releasable state, or if I misconstrued the strict requirement that stable release points on the module master branch be recognizable. If only master HEAD must be kept releasable the simplest work flow is to do a fast-forward merge from develop to master and push the results at any time where develop is considered stable enough to release. If there's an another rationale for keeping the branches separate I'd like to hear it to better my understanding of how git is expected to be used in Boost. Peter [*] I can't find the super-project release plan text about selecting non-HEAD module master branch contents from which this requirement is derived. https://svn.boost.org/trac/boost/wiki/ModBigPicture has a more lax requirement that pushes to master only be done when the content is stable, which will work in the more common case where there are no interoperability issues. The strict requirement makes sense, though, and I'm sure I read it somewhere.

1 0

[git-help] Clone / fetch specific submodule SHA?
by Rene Rivera 25 Dec '13

25 Dec '13

Does anyone know of a way to do a submodule update and clone that only fetches a specific SHA? In particular the SHA referenced in the superproject? Rene. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

3 6

Reminder about links when running b2 headers
by Edward Diener 25 Dec '13

25 Dec '13

There was already a discussion about why the creation of hard links to individual files in the boost directory is inferior to the creation of symbolic links when the ability to create symbolic links is supported by the OS. As a reminder, if a hard link is created and the submodule file is replaced by git, the hard link will still refer to the old file contents. Thus testing, when it refers to any of the hard linked header files in the boost subdirectory, will go awry if this happens. Can we please have this updated at the module boost superproject level by some Boost Build guru so that symbolic links are created when allowed by the OS ? Even if, as on Windows, administrator rights are needed to create symbolic links it seems we could have some b2 headers alternative, aka 'b2 headers_wadmin', which would create symbolic links on Windows for users who have administrator rights. Of course on Linux this is not a problem. I realize this might not be easy to do even by a Boost Build expert but unless we want to hear squawks and complaints from Boost developers/end-users using our git/modular boost setup we need to change to symbolic links when possible.

3 6

[range]slicing any_range
by Takatoshi Kondo 25 Dec '13

25 Dec '13

Hello, I'm using the Boost.Range library (Version:1.55.0). When I use any_range with sliced adaptor, slicing operation doesn't return. Is my code something wrong? If it is a bug, I will create a ticket. Here is the minimized code that reproduces the situation: #include <vector> #include <iostream> #include <cassert> #include <boost/range/any_range.hpp> #include <boost/range/adaptor/sliced.hpp> typedef boost::any_range<int, boost::random_access_traversal_tag, int, std::ptrdiff_t> int_range; int main() { std::vector<int> v; v.push_back(0); v.push_back(1); v.push_back(2); { // works fine std::cout << "slice vector" << std::endl; int_range ir1 = v | boost::adaptors::sliced(0,2); std::cout << "slice vector finished" << std::endl; assert(ir1[0] == 0); assert(ir1[1] == 1); assert(ir1.size() == 2); } { int_range ir2(v); std::cout << "slice any_range" << std::endl; int_range ir3 = ir2 | boost::adaptors::sliced(0,2); // never return... std::cout << "slice any_range finished" << std::endl; assert(ir3[0] == 0); assert(ir3[1] == 1); assert(ir3.size() == 2); } } Takatoshi Kondo

1 2

[string_ref] degree of conformance to standard proposal
by Peter A. Bigot 24 Dec '13

24 Dec '13

(Background: I need a string_view with features in N3762 that aren't in N3442 (viz., pos parameters to the string methods). I'm trying to determine how much effort I should put into a set of patches to update the Boost implementation to the latest draft proposal.) The default constructor for Boost.string_ref produces an object which returns a null pointer from data(). N3442 and its successor N3762 both require the return value from data() to be non-null (http://isocpp.org/files/papers/N3762.html#h5o-5) GCC's libstdc++ folks solved this by adding a constexpr unit length string to serve as the base referenced object (http://gcc.gnu.org/ml/libstdc++/2013-11/msg00104.html) But for Boost I don't see how this can be changed without introducing a link dependency. In a cases like this, how closely does Boost want to track the standard proposals? Similarly, the standard proposal has settled on *string_view instead of *string_ref. Would Boost rename the library/class, or just introduce an alias? Peter

2 3

Re: [boost] [git] Effects of git submodule update
by Beman Dawes 24 Dec '13

24 Dec '13

On Mon, Dec 23, 2013 at 2:17 PM, Robert Ramey <robertmacleranramey(a)gmail.com > wrote: > > > On Monday, December 23, 2013 8:47:21 AM UTC-8, Beman Dawes wrote: > <snip ..> > > Comments welcome, >> > > Beman. > > This is beyond awesome !!!! (I can't believe I used the word "awesome") > > I've been dabbled with git on my own machine (now a new machine) for a few > months > and it's been OK but I never really "got" the branching/merging, etc..... > Mainly this > is because I didn't really have to yet. I've also been lurking around > waiting for > the smoke to clear with boost modularization - a cowardly position I know, > but expedient in my particular circumstances right now. The work you've > done > is getting this organized AND well explained is incredible. I'm aware > that the dust has to settle some. But this looks to me like it's going to > support a whole new trajectory for boost. It makes me very, optimistic > about future of boost and C++ in general. > > Personally, I don't think that it's too much to say that boost saved C++. > > And I don't think it's too much to say that you're saving boost right now. > Robert, thank you very much for the kind words. Knowing that work is appreciated is a strong motivation to continue! But do remember this is a long process with a lot of people contributing, both now and in the past. Dave Abrahams and Daniel Pfeifer deserve special mention for several years of work on the git and modular boost conversion implementation. The release managers and boost.build team are working on infrastructure. The testers will soon be doing their part. And mailing list participants are providing the ideas and feedback that drive the whole process. Thanks to all, --Beman

1 0

[Proposal] Boost Community Maintenance Team Goals and Guidelines
by Marshall Clow 24 Dec '13

24 Dec '13

Start here: https://dl.dropboxusercontent.com/u/9897665/community-maintenance.html I have contacted the authors of the libraries listed in Beman’s proposals. Some have responded affirmatively; the rest have not responded. So, I thought I would put down some thoughts about how the Boost Community Maintenance Team (Boost.CMT) should work. Goals (in priority order): 1. Keep things building on all the supported compilers (and as many others as possible) 2. Get the test matrix “all green” and keep it that way. 3. Fix the accumulated bugs; drive the bug count to zero, and keep it there. 4. Add new features. How I see this working: 0) We’ll set up a separate Boost.CMT mailing list. (the main developer list has too much traffic already) 1) People would pick a problem and post a note to the list that they were working on it. 2) {Optional] discussion ensues about the way to solve the problem. 3) A potential solution is implemented (and tested!) 4) A pull request is posted to the mailing list (with tests) 5) Discussion ensues. Repeat steps 3/4/5 as needed. 6) The pull request is merged to ‘develop’ 7) After test cycles, the change is merged to ‘master' Notes: 1) All of this should happen on the Boost.CMT ML. 2) Discussions _about_ the CMT should happen on the main Boost ML. 3) The person who lands the patch is responsible for checking the test results and merging to “master” (and closing out the bug report, if any). 4) The goal of the CMT will be the same as the Boy Scouts - “Leave the code cleaner than when you found it” Comments? -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki

2 2

Re: [boost] [atomic] Probable documentation issue: how do we know atomic is safe and/or efficient?
by Pete Bartlett 24 Dec '13

24 Dec '13

> On 24 Dec 2013, at 13:43, "John Maddock" <john(a)johnmaddock.co.uk> wrote: > > This message has no content.

1 0

Ominous Warning — should I be worried?
by John M. Dlugosz 23 Dec '13

23 Dec '13

I'm compiling with VS10, and using Boost 1.49.0 “reference member is initialized to a temporary that doesn't persist after the constructor exits” That does not sound good, and browsing through the mailing list archives I see discussions of regressions in 2010 that cite C4413 and use of emplace. I can't read the source code because it's just a ball of preprocessor stuff. Is this a real problem or a warning that can be ignored? I would think that if Boost.Container was broken on VS10, it would be mentioned somewhere where it's easy to spot. Thanks, —John E:\boost_1_49\boost/preprocessor/iteration/detail/local.hpp(37): warning C4413: 'boost::container::container_detail::advanced_insert_aux_non_movable_emplace1arg<A,Iterator,P0>::m_p0' : reference member is initialized to a temporary that doesn't persist after the constructor exits with [ A=std::allocator<std::tr1::shared_ptr<MyTypeA>>, Iterator=std::tr1::shared_ptr<MyTypeA> *, P0=std::tr1::shared_ptr<MyTypeA> ] E:\boost_1_49\boost/preprocessor/iteration/detail/local.hpp(37) : see declaration of 'boost::container::container_detail::advanced_insert_aux_non_movable_emplace1arg<A,Iterator,P0>::m_p0' with [ A=std::allocator<std::tr1::shared_ptr<MyTypeA>>, Iterator=std::tr1::shared_ptr<MyTypeA> *, P0=std::tr1::shared_ptr<MyTypeA> ] E:\boost_1_49\boost/preprocessor/iteration/detail/local.hpp(37) : while compiling class template member function 'boost::container::container_detail::advanced_insert_aux_non_movable_emplace1arg<A,Iterator,P0>::advanced_insert_aux_non_movable_emplace1arg(A &,P0 &&)' with [ A=std::allocator<std::tr1::shared_ptr<MyTypeA>>, Iterator=std::tr1::shared_ptr<MyTypeA> *, P0=std::tr1::shared_ptr<MyTypeA> ] E:\boost_1_49\boost/preprocessor/iteration/detail/local.hpp(37) : see reference to class template instantiation 'boost::container::container_detail::advanced_insert_aux_non_movable_emplace1arg<A,Iterator,P0>' being compiled with [ A=std::allocator<std::tr1::shared_ptr<MyTypeA>>, Iterator=std::tr1::shared_ptr<MyTypeA> *, P0=std::tr1::shared_ptr<MyTypeA> ] E:\boost_1_49\boost/preprocessor/iteration/detail/local.hpp(37) : see reference to class template instantiation 'boost::container::container_detail::advanced_insert_aux_emplace1arg<A,Iterator,P0>' being compiled with [ A=std::allocator<std::tr1::shared_ptr<MyTypeA>>, Iterator=std::tr1::shared_ptr<MyTypeA> *, P0=std::tr1::shared_ptr<MyTypeA> ] mysourcefile.cpp(172) : see reference to function template instantiation 'void boost::container::vector<T>::emplace_back<std::tr1::shared_ptr<_Ty>>(P0 &&)' being compiled with [ T=std::tr1::shared_ptr<MyTypeA>, _Ty=MyTypeA, P0=std::tr1::shared_ptr<MyTypeA> ]

2 1

Beginner
by prabhdeep singh 23 Dec '13

23 Dec '13

I want to start contributing to the open source community, but I do not where to begin. Your community's cause seems great! So I would love to start but I am absolutely clueless as to where to begin. I have a background in C++ and algorithmic operations. Any help would be appreciated!

2 1

[git] Effects of git submodule update
by Beman Dawes 23 Dec '13

23 Dec '13

There has been a lot of concern expressed about updating submodules, so I've updated the applicable section of "Getting Started with Modular Boost Library Maintenance" to include reassurance that uncommitted changes will not be overwritten. See https://svn.boost.org/trac/boost/wiki/StartModMaint A table has been added describing the effects of git submodule update. Actual tests were run to determine the effects, using git 1.8.2.msysgit.0. See https://svn.boost.org/trac/boost/wiki/StartModMaint#Effectsofgitsubmoduleup… In looking at the table, a couple of things stand out: * git submodule update, like git checkout, will not normally overwrite uncommitted changes, regardless of whether the working copy is detached or on a branch. See the table for the specific error message. From the error message it appears checkout may actually be being called. * The case of an update applied to a submodule that is on branch master and at a commit behind the super-project's commit for that submodule just does a pull without a detach. That is the only case where a" checkout --detach" isn't done before a pull. I'm unsure whether this is a feature or a bug. Comments welcome, --Beman

1 0

generating documentation in modular boost
by Peter A. Bigot 23 Dec '13

23 Dec '13

I'm trying to update documentation in lib/utility but can't see how to regenerate the html files. Generalizing from the fact I can run the tests by invoking b2 within the module test subdirectory, I invoked b2 from within the doc subdirectory. This produced an error about an unknown feature "<format>" in Jamfile.v2. When I comment out those lines I do get xml files generated in a subdirectory of the superproject, but I expected html, matching what's been checked in. Is there documentation on building documentation that I haven't been able to find? Peter

3 3

Serializing a Graph Structure Using Boost
by Nouf M. 23 Dec '13

23 Dec '13

Hi, I would like to use boost to serialize my graph (it's in the boost adjacency list format)... I couldn't do it... I managed to serialize an array and some other structures as follows: int I[5] = {0,1,2,3,4}; boost::archive::text_iarchive ia(file), ia << I; but that doesn't work with graph data in the boost adjacency list format... when I write: ia << g //g is my graph I get the following compilation error: 'serialize' is not member of 'VertexProperties' 'VertexProperties' is a structure that I wrote as follows: struct VertexProperties { int id; int weight; }; I don't know how to add 'serialize' as a member function... I also tried "SavingArchieve" template but couldn't do it... Any idea's please? or references?

1 0

Access is denied for the "bootstrap" command
by Nouf M. 23 Dec '13

23 Dec '13

Hi, In order to use the serialization files... I need to build them... I have to go to the BGL directory from the command prompt and enter the "bootstrap" command... It works on some machines... But on my machine it gives me: "Building Boost.Build engine Access is denied. Failed to build Boost.Build engine. Please consult bootstrap.log for further diagnostics" My machine is an HP Workstation and I'm using Windows 7 professional edition... Why do you think I'm getting Access is denied?

1 0

[type_traits] is_empty fails on final classes.
by yuri kilochek 22 Dec '13

22 Dec '13

Hi. It seems boost::is_empty uses Empty Base Optimisation to detect whether a class type is stateless or not. This predictably fails on final types, as they cannot be inherited from: #include <iostream> #include <boost/type_traits.hpp> class Test final {}; int main() { std::cout << boost::is_empty<Test>::value; return 0; } Fails on gcc 4.8.1 with In file included from /usr/local/include/boost/type_traits.hpp:54:0, from main.cpp:2: /usr/local/include/boost/type_traits/is_empty.hpp: In instantiation of 'struct boost::detail::empty_helper_t1<Test>': /usr/local/include/boost/type_traits/is_empty.hpp:79:5: required from 'const bool boost::detail::empty_helper<Test, true>::value' /usr/local/include/boost/type_traits/is_empty.hpp:88:5: required from 'const bool boost::detail::is_empty_impl<Test>::value' /usr/local/include/boost/type_traits/is_empty.hpp:220:1: required from 'struct boost::is_empty<Test>' main.cpp:7:39: required from here /usr/local/include/boost/type_traits/is_empty.hpp:52:8: error: cannot derive from 'final' base 'Test' in derived type 'boost::detail::empty_helper_t1<Test>' struct empty_helper_t1 : public T ^ Yet std::is_empty works just fine (al least in gcc), and appears to be implemented via an intrinsic: template<typename _Tp> struct is_empty : public integral_constant<bool, __is_empty(_Tp)> {}; Now, is it at all possible to implement conforming is_empty without resorting to compiler magic that are intrinsics?

3 3

[git] How the blazes are you supposed to update all the submodules?
by John Maddock 22 Dec '13

22 Dec '13

OK.... so I do a Git pull at the top level (note: using TortoiseGit), and I see lots of messages in the log indicating which libraries have updates, and judging by the time taken they seem to be downloaded (?), but I don't actually see any changes in the libraries themselves. BTW I have every library set explicitly to either "develop" or "master". If I do a "git pull" on an individual library then the changes do come through OK. So what's the right way to do this? I assume it's not a "submodule update" as that seems to leave everything in a detached head state which I take it is a bad idea? I'm also seeing a lot of negative comments about Git submodules on the web, for example: http://codingkilledthecat.wordpress.com/2012/04/28/why-your-company-shouldn…, seems like there's a lot of potential to shoot yourself in the foot/head/chest here? Thanks, John.

16 33

Storing an adjacency list
by Nouf M. 22 Dec '13

22 Dec '13

Hi, I have a very large graph data (150000 node and 450000 edges) in two text files... first one: contains the vertices and their weights. second one: contains the edges and their weights. I need to retrieve a small subgraph from this big graph data...it's easier to do that if the graph is stored in an adjacency list format... I managed to write some code that reads from the files and creates a graph in an adjacency list format... Now, I would like to store the graph (the one in the adjacency list format) for next uses because it takes long time to convert my graph text files into the adjacency list format... I couldn't figure out how to do it... I saw the section about graph I/O in the BGL documentation: Graphviz, Max-flow, and GraphML but I don't think they will do what I need... I looked also on Serialization, I'm not sure about it... will serialization work well to store very large graphs and then retrieve then very fast ... Is this possible? Best regards, Nouf

1 0

[ASIO] example clarification (how to)
by Gaetano Mendola 21 Dec '13

21 Dec '13

In the asio chat example http://www.boost.org/doc/libs/1_55_0/doc/html/boost_asio/example/cpp11/chat… the class chat_server implements the async_accept handler with a lambda without use the shared_from_this pattern, isn't an error destroy the class while the handler is running? Maybe is not a problem looking at how is used inside the main but without having knowledge on how is it going to be used which can be the best way to destroy the chat_server (or similar code) safely? Is something like the following correct? chat_server::~chat_server() { //Call dispatching a cancel operation //in order to be sure to not chain another async_accept acceptor_.get_service().dispatch( [this](){ acceptor_.cancel(); }); } here I'm supposing a single thread is running io_service.run() otherwise the strand has to be used. Regards Gaetano Mendola --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com

1 0

[github] Admin access for move/container/interprocess/intrusive
by Ion Gaztañaga 21 Dec '13

21 Dec '13

Hi, Following indications explained in [https://svn.boost.org/trac/boost/wiki/ModAdmin] I requested admin access to Move, Container, Interprocess & Intrusive several days ago. The issue is still open, so have I missed something? Thanks to all working on this, Ion

1 0

[git][testing] regression testing?
by Joaquín Mª López Muñoz 21 Dec '13

21 Dec '13

There's been some unanswered questions around this. I understand that regression tests, which are critical to ensure clean develop->master merges, will be eventually updated to work against git rather than the abandoned SVN, but I can't find any info on the progress of this. FWIW, I see some authors are going ahead and merging their libs anyway, which will bring breakages etc if changes are not properly validated through regression testing. Any indication on how this is progressing much appreciated. Best, Joaquín M López Muñoz Telefónica Digital ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx

2 1

sidenote about guis (Re: [git] How the blazes are you supposed to update all the submodules?)
by Mateusz Loskot 20 Dec '13

20 Dec '13

(Please, adjust subject line for changed topic!) On 20 December 2013 11:15, Klaim - Joël Lamotte <mjklaim(a)gmail.com> wrote: > These days I only use SourceTree for both git and hg. It's cross platform, It's not cross platform, but Windows and Mac only https://answers.atlassian.com/questions/149631/sourcetree-for-linux?page=1#… A note on my own experience: 0. First, I aim to be comfy with git command, if not, then I will never understand git really. 1. Then, I use SourceTree where I can to complement git command (branches visualisation, etc.) 2. I use Qt Creator with its Git plugin which is nothing more than git command proxy, hence equivalent to git command. BTW, I'd like to do a bit of propaganda about Boost.Build support for Qt Creator: https://github.com/mloskot/qt-creator-plugin-boostbuild Best regards, -- Mateusz Łoskot, http://mateusz.loskot.net

4 5

[typeof] Non-static data member
by Bjorn Reese 20 Dec '13

20 Dec '13

Consider the following example: void foo(int value) {} struct alpha { int value; typedef BOOST_TYPEOF(foo(value)) return_type; }; This example compiles just fine with g++, but with clang++ it only works if compiled with -std=c++11, otherwise it gives the error message below. I believe that clang is correct (this diagnostics was added in clang 3.1 [1].) https://llvm.org/viewvc/llvm-project?view=revision&revision=154073 Is this a bug in Boost.Typeof or is it expected behavior? Is there a workaround for it? The error message is: /home/breese/src/treediff/treediff/main.cpp:17:30: error: invalid use of non-static data member 'value' typedef BOOST_TYPEOF(foo(value)) return_type; ^~~~~ /usr/local/include/boost/typeof/native.hpp:41:76: note: expanded from macro 'BOOST_TYPEOF' #define BOOST_TYPEOF(expr) BOOST_TYPEOF_KEYWORD(boost::type_of::ensure_obj(expr)) ^ 1 error generated.

1 1

Re: [boost] [Locale] translate() couples key and output character widths
by Artyom Beilis 20 Dec '13

20 Dec '13

That was a loooooong and painful discussion during the boost.locale review. Such a change was asked by the reviewers that wanted to be able to use wide strings as keys. For example translate(L"© All Rights Are Reserved") Where "©" is non-ASCII character. This change was mostly required to support non-ascii characters in keys. To be honest I was strongly against the change but finally had to accept it. See: http://thread.gmane.org/gmane.comp.lib.boost.devel/218543 Also you can search boost lists the locale review comments... Artyom Beilis -------------- CppCMS - C++ Web Framework: http://cppcms.com/ CppDB - C++ SQL Connectivity: http://cppcms.com/sql/cppdb/ -------------------------------------------- On Fri, 12/20/13, Alexander Lamaison <awl03(a)doc.ic.ac.uk> wrote: Subject: [boost] [Locale] translate() couples key and output character widths To: boost(a)lists.boost.org Date: Friday, December 20, 2013, 1:01 PM I've finally gotten round to changing from the pre-release version of Boost.Locale (v2.92) to the version now in Boost, and I was quite surprised by one change. Previously, I could do the following: void function_takes_wide_string(std::wstring message); function_takes_wide_string(boost::locale::translate("My translation key")); However, with the new version, the key must be passed in as a wide string if I am to be able to get a wide string out. This means changing `translate("blah")` to `translate(L"blah")` throughout. The change itself is no big deal, but the problem is that it feels like a change for the worse. The character width of the key is now coupled to the character width of the output, when the two are separate concepts and should be allowed to vary independently. The old class `message` coeerced the string to whichever width was required. The new class `basic_message<T>` coerces only to `basic_string<T>` and, worse than that, doesn't provide a method to explicitly convert to a different width string. My question, I suppose, is why was this change made? What makes the new API better? Alex -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

2 1

[Locale] translate() couples key and output character widths
by Alexander Lamaison 20 Dec '13

20 Dec '13

I've finally gotten round to changing from the pre-release version of Boost.Locale (v2.92) to the version now in Boost, and I was quite surprised by one change. Previously, I could do the following: void function_takes_wide_string(std::wstring message); function_takes_wide_string(boost::locale::translate("My translation key")); However, with the new version, the key must be passed in as a wide string if I am to be able to get a wide string out. This means changing `translate("blah")` to `translate(L"blah")` throughout. The change itself is no big deal, but the problem is that it feels like a change for the worse. The character width of the key is now coupled to the character width of the output, when the two are separate concepts and should be allowed to vary independently. The old class `message` coeerced the string to whichever width was required. The new class `basic_message<T>` coerces only to `basic_string<T>` and, worse than that, doesn't provide a method to explicitly convert to a different width string. My question, I suppose, is why was this change made? What makes the new API better? Alex -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org)

1 0

[Filesystem] Hidden overloaded virtual function
by Ben Pope 20 Dec '13

20 Dec '13

./boost/detail/utf8_codecvt_facet.hpp:171:17: warning: 'boost::filesystem::detail::utf8_codecvt_facet::do_length' hides overloaded virtual function [-Woverloaded-virtual] virtual int do_length( ^ /usr/include/c++/v1/__locale:952:17: note: hidden overloaded virtual function 'std::__1::codecvt<wchar_t, char, __mbstate_t>::do_length' declared here: type mismatch at 1st parameter ('state_type &' (aka '__mbstate_t &') vs 'const std::mbstate_t &' (aka 'const __mbstate_t &')) virtual int do_length(state_type&, const extern_type* __frm, const extern_type* __end, size_t __mx) const; ^ I suspect that's not intentional. Ben

4 5

Review Wizard Report for December 2013
by Ron Garcia 20 Dec '13

20 Dec '13

============================================== Review Wizard Status Report for December 2013 ============================================== News ==== 1. Boost 1.54.0 Released. New Libraries: Log, TTI, Type Erasure. 2. Boost 1.55.0 Released. New Libraries: Predef. 3. Type Index Accepted Provisionally. November 2013. 4. Boost repository moves to Git and GitHub. December 2013. Open Issues =========== The following libraries have review managers, but have not yet been scheduled for review: * Range Extensions - added May 2012; review manager: Neil Groves. The following libraries have been accepted to Boost, but have not yet been submitted to SVN: * Constrained Value - accepted September 2010; author: Robert Kawulak. * Contract - accepted September 2012; author: Lorenzo Caminiti. The following libraries have been accepted and submitted to SVN, but have not yet appeared in a release: * none The following libraries have been accepted provisionally to Boost, but have not been submitted for mini-review and full acceptance: * Endian - accepted provisionally November 2011; author: Beman Dawes. * Type Index - accepted provisionally November 2013; author: Antony Polukhin General Announcements ===================== As always, we need experienced review managers. Please take a look at the list of libraries in need of managers and check out their descriptions. In general review managers are active boost participants, including library contributors, infrastructure contributors, and other mailing list participants with a substantial track record of constructive participation. If you can serve as review manager for any of them, email Ron Garcia or John Phillips, "rxg at cs dot ubc dot ca" and "johnphillipsithica at gmail dot com" respectively. We are also suffering from a lack of reviewers. While we all understand time pressures and the need to complete paying work, the strength of Boost is based on the detailed and informed reviews submitted by you. If you are interested in reviewing a library but won't have time during the review period, you can always prepare your review ahead of time. No rule says you can only work on a review during the review period. A link to this report will be posted to www.boost.org. If you would like us to make any modifications or additions to this report, please email Ron or John. The review schedule is an unordered list of the libraries awaiting review. As such, any library on the schedule can be reviewed once the developer is ready, a review manager has been secured, and the manager, developer, and wizards agree on a date to schedule the review. Review Schedule =============== * Join (M) * Pimpl (M) * Sorting (M) * Quaternions, Vectors, Matrices (M) * Variadic Macro Data (M) * Block Pointer (M) * Singularity (M) * Extended Complex Numbers (M) * Metaparse (M) * Range Extensions * Nowide (M) * Array (M) * STL Extensions (M) * Countertree (M) * Process (M) * Asynchronous File I/O (M) * Application (M) * Fiber ``(M)`` marks libraries that need review managers. -------------------- Join ---- :Author: Yigong Liu :Review Manager: Needed :Download: http://channel.sourceforge.net/ :Description: Join is an asynchronous, message based C++ concurrency library based on join calculus. It is applicable both to multi-threaded applications and to the orchestration of asynchronous, event-based applications. It follows Comega's design and implementation and builds with Boost facilities. It provides a high level concurrency API with asynchronous methods, synchronous methods, and chords which are "join-patterns" defining the synchronization, asynchrony, and concurrency. Pimpl ----- :Author: Vladimir Batov :Review Manager: Needed :Download: https://github.com/boost-vault/Miscellaneous/blob/master/Pimpl.zip :Description: The Pimpl idiom is a simple yet robust technique to minimize coupling via the separation of interface and implementation and then implementation hiding. This library provides a convenient yet flexible and generic deployment technique for the Pimpl idiom. It's seemingly complete and broadly applicable, yet minimal, simple and pleasant to use. Sorting ------- :Author: Steven Ross :Review Manager: Needed :Download: https://github.com/boost-vault/Sorting :Description: A grouping of 3 templated hybrid radix/comparison-based sorting algorithms that provide superior worst-case and average-case performance to std::sort: integer_sort, which sorts fixed-size data types that support a rightshift (default of >>) and a comparison (default of <) operator. float_sort, which sorts standard floating-point numbers by safely casting them to integers. string_sort, which sorts variable-length data types, and is optimized for 8-bit character strings. All 3 algorithms have O(n(k/s + s)) runtime where k is the number of bits in the data type and s is a constant, and limited memory overhead (in the kB for realistic inputs). In testing, integer_sort varies from 35% faster to 2X as fast as std::sort, depending on processor, compiler optimizations, and data distribution. float_sort is roughly 70% faster than std::sort. string_sort is roughly 2X as fast as std::sort. Quaternions, Vectors, Matrices ------------------------------ :Author: Emil Dotchevski :Review Manager: Needed :Download: http://www.revergestudios.com/boost-qvm/ :Description: QVM defines a set of generic functions and operator overloads for working with quaternions, vectors and matrices of static size. The library also defines vector and matrix data types, however it allows users to introduce their own types by specializing the q_traits, v_traits and m_traits templates. Variadic Macro Data ------------------- :Author: Edward Diener :Review Manager: Needed :Download: `Boost Sandbox <http://svn.boost.org/svn/boost/sandbox/variadic_macro_data/>`__ :Description: This library adds support and functionality for variadic macros to Boost as well as integrating variadic macros with the Boost PP library without changing the latter library in any way. Block Pointer ------------- :Author: Phil Bouchard :Review Manager: Needed :Download: https://svn.boost.org/svn/boost/sandbox/block_ptr/ :Description: Deterministic memory manager of constant complexity capable of handling cyclic collections. Singularity ----------- :Author: Ben Robinson :Review Manager: Needed :Download: https://github.com/cppmaven/Singularity :Description: The Singularity Design Pattern allows you to restrict any class to a single instance. Unlike the infamous Singleton, Singularity gives you direct control over the lifetime of the object, does not require you to grant global access to the object, nor does it limit you to the default constructor for that object. Extended Complex Numbers ------------------------ :Author: Matthieu Schaller :Review Manager: Needed :Download: http://code.google.com/p/cpp-imaginary-numbers/ :Description: The library is an extension of the std::complex class addressing two issues: 1. The standard does not guaranty the behaviour of the complex class if instantiated with types other than float/double/long double. 2. Some calculation where pure imaginary numbers (i.e. multiples of sqrt(-1)) appear are unnecessarily slowed down due to the lack of support for these numbers. The code I submit contains two interleaved classes boost::complex and boost::imaginary which can be instantiated with any type T provided T overloads the usual arithmetic operators and some basic (real) mathematical functions depending on which complex function will be used. It is thus an extended version of Thorsten Ottosen's n1869 proposal (http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2005/n1869.html) Metaparse --------- :Author: Abel Sinkovics :Review Manager: Needed :Download: http://abel.web.elte.hu/metaparse/metaparse.zip :Description: Metaparse is a library for constructing parsers parsing at compile-time based on template metaprogramming. The parsers built with the library take boost::mpl::strings as input and can produce - types - objects (types with public static members) - callable C++ functions (types with public static method) - template metafunction classes as output (based on the input being parsed). On compilers supporting constexpr the library provides the following syntactic sugar for writing the input of the parsers: BOOST_STRING("this is a string") The library can be used for implementing DSLs in C++, including DSLs making C++ template metaprogramming easier (see examples). Range Extensions ---------------- :Author: Akira Takahashi :Review Manager: Neil Groves :Download: https://github.com/faithandbrave/OvenToBoost :Description: This project adds some features of the Oven Range Library to Boost.Range. Features: - Additional Range Adaptors (taken, taken_while, dropped, dropped_while, elements, elements_key, memoized, outdirected) - Extensions for using Lambda (regular function, regular operator) - Infinite Range (iteration function) - and additional range utilities. Nowide ------ :Author: Artyom Beilis :Review Manager: Needed :Download: http://cppcms.com/files/nowide/ :Description: This library makes cross platform Unicode aware programming easier. It provides an implementation of standard C and C++ library functions, such that their inputs are UTF-8 aware on Windows without requiring to use Wide API. Array ----- :Author: Brian Smith :Review Manager: Needed :Download: https://github.com/BrianJSmith/Array :Description: The array class is a C++11 compatible implementation of static multidimensional arrays. STL Extensions -------------- :Author: Vadim Stadnik :Review Manager: Needed :Download: https://github.com/vstadnik/stl_ext_adv_review :Description: The proposed library [stl_ext_adv] offers augmented array based B+ trees and STL containers that support the interfaces of the C++03 sequences and associative containers. The library offers a number of extensions and performance improvements that are not available in C++03 and C++11 standard containers. Countertree ----------- :Author: Francisco Jose Tapia :Review Manager: Needed :Download: https://dl.dropbox.com/u/8437476/works/countertree_code_doc.zip :Description: This library is an implementation of a binary red-black counter tree. This tree have an additional counter in each leaf. This permit the access to the elements by the position, like in a vector. It is a random access container with random access iterators. COUNTERTREE This kind of trees have an additional counter in each leaf. This permit the access to the elements by the position, like in a vector. It is a random access container with random access iterators. With unordered information we have a vector with the same speed inserting and deleting in any position (O(log N)). With ordered information, we have the classes set, multiset, map and multimap, with identical interface than the STL classes, with the plus of access to the elements by position, like in a vector. The iterators are random access , and you can subtract them. SUBALLOCATOR The suballocator is a layer between the allocator and the data structures, compatible with any allocator with the STL definition. The suballocator replace to the allocator in the allocation of equal size elements. It provides speed, return the unused memory and decrease the memory used by the program and improve the cache performance due to the data locality improvement ( 30% of improvement of speed respect the std::allocator with GCC 4.7) Process ------- :Author: Boris Schaeling :Review Manager: Needed :Download: http://www.highscore.de/boost/process0.5/process.zip :Description: Boost.Process is a library to manage system processes. It can be used to: * create child processes * setup streams for child processes * communicate with child processes through streams (synchronously or asynchronously) * wait for processes to exit (synchronously or asynchronously) * terminate processes Asynchronous File I/O --------------------- :Author: Niall Douglas and Paul Kirth :Review Manager: Needed :Download: https://github.com/BoostGSoC/boost.afio/archive/boost-peer-review.tar.gz :Description: Boost.AFIO is a linear scalable, batch, chainable, asynchronous closure execution engine with an almost wait free implementation extending Boost.ASIO and Boost.Thread specialised as a portable asynchronous file i/o implementation library. Implementation of this first version has been kept as simple as possible (~ 1000 active LOC) at the cost of some performance, though with a good compiler you can expect 25-50% of the performance of using raw Boost.ASIO. Application ----------- :Author: Renato Tegon Forti :Review Manager: Needed :Download: https://github.com/retf/Boost.Application :Documentation: http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/index.html :Description: Application provides an application environment, or start point to any people that want a basic infrastructure to build an system application on Windows or Unix Variants (e.g. Linux, MacOS). Application uses behaviours modeled using 'aspects' concept proposed by 'Vicente J. Botet Escriba', that allow easy extension and customization of library components. The application modes uses these components internally to achieve the user desirable behaviours. Application provide many useful ready-to-use features, e.g: * Run application as Windows Service; * Run application as UNIX/POSIX Daemon; * Plugin extension system; * Process(executable) Single instance Instantiation support; * Application SIGNAL/Callbacks customization; * Windows Service Setup feature; * And many others. Fiber ----- :Author: Oliver Kowalke :Review Manager: Nat Goodspeed :Download: https://github.com/olk/boost-fiber :Documentation: http://ok73.funpic.de/boost/libs/fiber/doc/html/index.html :Description: Fiber provides a framework for micro-/userland-threads (fibers) scheduled cooperatively. The API contains classes and functions to manage and synchronize fibers similar to boost.thread.' Libraries under development =========================== See http://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction for a current listing of libraries under development.

2 3

[git] Why are we using Github (was: The any library does not pull cleanly because of a forced update on develop and master)
by Cox, Michael 19 Dec '13

19 Dec '13

On Tue, Dec 10, 2013 at 7:40 AM, Dave Abrahams <dave(a)boostpro.com> wrote: > "Cox, Michael" <mhcox(a)bluezoosoftware.com> writes: > > > I tried to update my local repositories to the latest changes in each > > submodule: > > > > git pull; git submodule foreach --recursive git pull > > > > When it got to the libs/any submodule, I got the following message: > > > > remote: Counting objects: 27, done. > > remote: Compressing objects: 100% (2/2), done. > > remote: Total 6 (delta 2), reused 6 (delta 2) > > Unpacking objects: 100% (6/6), done. > > From https://github.com/boostorg/any > > + 3f0b981...e3e5da6 develop -> origin/develop (forced update) > > + 38039b3...d35b2d6 master -> origin/master (forced update) > > * [new tag] 20131209-develop -> 20131209-develop > > * [new tag] 20131209-master -> 20131209-master > > > > and my editor popped up with a merge commit message to edit. I think > > that's because the develop and master branches were force updated, > > re-writing history in develop and master. > > If there is not already a policy in place to prevent history rewriting > in public branches, we should have one. And if there's a GitHub > mechanism for denying the privilege, it should be enabled. > There may be a policy, but as far as I can tell, Github has no easy interface to allow you to enforce it, i.e. set the receive.denyNonFastForwards=true and receive.denyDeletes=true (for all branches) or branch.name>.mergeoptions=--ff-only (setting up fast forward only per branch). Maybe via plugin (like I assume the trac plugin is being used to integrate boost's trac web-site)? >From the git-config man page: receive.denyNonFastForwards If set to true, git-receive-pack will deny a ref update which is not a fast-forward. Use this to prevent such an update via a push, even if that push is forced. This configuration variable is set when initializing a shared repository. receive.denyDeletes If set to true, git-receive-pack will deny a ref update that deletes the ref. Use this to prevent such a ref deletion via a push. branch.<name>.mergeoptions Sets default options for merging into branch <name>. The syntax and supported options are the same as those of git-merge(1), but option values containing whitespace characters are currently not supported. The last one I'm not sure if it works on the server side. It may be a client side only configuration item. I have seen examples of adding hooks to enforce such restrictions. Which brings me to a question I've been wanting to get answered: why was Github chosen in the first place? I know it's the 900-lb gorilla in public git repository hosts, but I think Bitbucket allows so much more flexibility in configuring your repositories: - Individual branches and wild-card refs can be configured with who is allowed to commit (which can be a group). - Individual branches can be designated as not deletable. - Individual branches can be designated as not rewritable. See Take control with branch restrictions<http://blog.bitbucket.org/2013/09/16/take-control-with-branch-restrictions/> for more info. If we are still in the acceptance phase of the git conversion (based on some of the comments in the thread this was taken from), maybe we should reconsider Github? What were the advantages of Github vs. other public repositories like Bitbucket? Michael > > -Dave > > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost >

14 25

Getting Started Testing with Linux virtual machine on Windows host
by Beman Dawes 19 Dec '13

19 Dec '13

I'm primarily a Windows developer, but like to be able to test locally on both Windows and Linux so I don't have to wait for Boost's regression tests to cycle. For several years I've done that on a Linux virtual machine. I just rebuilt my virtual machine and kept a log so I could share how it is done. Such a virtual machine is free and is easy enough that most Boost library maintainers who use Windows could do the setup in an afternoon, most of which is just downloading files, and can be overlapped with other work. See https://svn.boost.org/trac/boost/wiki/StartTestingLinuxOnWindows Corrections or other comments appreciated. Enjoy! --Beman PS: The process would work in the other direction too, but it would require a Windows license (I.E. not free) and I don't have experience going in that direction so can't write about it.

10 21

Gsoc Participation
by Pulkit Mendiratta 19 Dec '13

19 Dec '13

Is Boost sending an application for participation in GSOC-2014? -- Cheers, Pulkit Mendiratta

6 5

[git] Submodule's readme and logo
by Adam Wulkiewicz 19 Dec '13

19 Dec '13

Hi, In Boost.Geometry we recently added a readme file (currently only in develop branch http://github.com/boostorg/geometry/tree/develop) and some basic wiki. From one of the discussions (by Mateusz Loskot): What I'd suggest is to create README.{md|markdown} file in root directory of geometry repo: have big heading on top [LOGO] Boost.Geometry The readme could also explain briefly what's around, what is include folder, what is example, test folder. and link to the main documentation and wiki pages. GitHub has somewhat 'trained' people there always is a README file (seehttp://tom.preston-werner.com/2010/08/23/readme-driven-development.html) so many users expect to use it as a first contact with a project. I believe having those files in all submodules would have a positive impact on the GitHub community and the users. Furthermore the style of those files could be more or less unified. Therefore I've prepared semi-consistent set of logos for some of the libraries: http://github.com/awulkiew/boost-logos. I decided to achieve the consistency by using the Boost logo as a base. Let me know what do you think about it. And don't hesitate to write about your ideas or propose changes. Regards, Adam

11 46

C++11 variant of the gcc toolset?
by Peter Dimov 19 Dec '13

19 Dec '13

Currently, when I want to test under g++ in C++11 mode, I use b2 toolset=gcc cxxflags=-std=c++11 This works, but (a) prevents me from combining this with other toolsets, (b) prevents me from testing both 03 and 11 at once, and (c) boost.build doesn't treat the two modes of the gcc toolset as distinct and uses the same directory for both. Am I missing something simple, or if not, shouldn't we have a separate gcc11 toolset that is exactly the same as the gcc toolset, but with -std=c++11 applied?

4 7

[Container] Priority Deque - Refinement
by Nathaniel McClatchey 19 Dec '13

19 Dec '13

Hi. I've recently made a double-ended priority queue (priority deque) publicly available at https://github.com/nmcclatchey/Priority-Deque , with the intent of submitting it to Boost (more specifically, I wish to make it part of Boost.Container). I would appreciate any comments, discussion, or refinements. Goals of the project: * Provide an efficient double-ended priority queue, with interface similar to std::priority_queue. * Keep requirements to a minimum. In particular, require nothing except what is already required by std::priority_queue. * Make it fast. Performance should be competitive with std::priority_queue. How goals are met: * The priority deque is implemented as a single class template, mimicking std::priority_queue * The interface of priority_deque is a strict superset of the interface of std::priority_queue. New functions follow the STL naming scheme. * The underlying container is assumed to be a sequence container supporting random-access iterators, front(), back(), and push_back(), as in std::priority_queue. No other assumptions are made. * The underlying data structure is an interval heap, which allows finding min/max in O(1) time, and single-element changes in O(log n) time. * Benchmarks (on queues with 20,000,000+ elements) indicated that the difference in performance between std::priority_queue and the priority deque is negligible when compiled by GCC with the O3 option. A specific question for anyone more experienced with development of generalized code: * I added several functions for controlled access to arbitrary elements. Is this overkill? If so, should they be removed? Thank-you for your time, Nate

7 16

[filesystem] fix recur_dir_itr_imp::increment(system::error_code* ec) in 1.54.0
by claudio.bley＠gmail.com 19 Dec '13

19 Dec '13

Hi. What's happening to the filesystem library? It seems there's no progress on any tickets in the bug tracker? Referring to https://svn.boost.org/trac/boost/ticket/6821#comment:5 Could we get this fix into 1.54.0, please? BTW, sorry for any confusion - I "managed" to comment on the wrong ticket... https://svn.boost.org/trac/boost/ticket/5403 would've been more appropriate, I guess. Claudio -- Claudio

3 4

Fwd: [Boost-users] Forthcoming Boost.Fiber review
by Nat Goodspeed 18 Dec '13

18 Dec '13

---------- Forwarded message ---------- From: Oliver Kowalke <oliver.kowalke(a)gmail.com> Date: Wed, Dec 18, 2013 at 4:12 PM Subject: Re: [Boost-users] Forthcoming Boost.Fiber review To: boost-users(a)lists.boost.org 2013/12/18 Oliver Kowalke <oliver.kowalke(a)gmail.com> > 2013/12/18 Carlos Ferreira <carlosmf.pt(a)gmail.com> > >> Hi! >> Docs link isn't working... -> 404 >> > docs: http://ok73.ok.funpic.de/boost/libs/fiber/doc/html/ src: http://ok73.ok.funpic.de/boost.fiber.zip

1 0

[build] improving the history
by Vladimir Prus 18 Dec '13

18 Dec '13

I've spent some time looking at history of Boost.Build git repository, and I think I've got a fairly reasonable outcome. The problem statement is that in the converted repository, the top-level has nothing but a directory called 'v2', which is rather ugly. While it can be fixed with 'git mv', it would mean that 'git log file' will not show complete history unless the --follow option is passed, which is inconvenient. It appears that graphical tools don't like moves much either. There were already moves in SVN, so even now, running 'git log' on any file in engine/ won't return complete history without --follow. Further, at some older revision, there are two copies of what was jam code then. The most convenient solution for these problems is to edit history of the 'develop' branch, so that content of top-level directory matches what was in 'v2' in SVN, and so that content of 'engine' matches Jam sources through the years. This won't actually break any important references from the super-project, first because they presumably are only to master branch, and second, because the commit objects will be still retained in repository. I am not sure we need to rewrite the 'master' branch, as it's not used for day to day development. Now, as soon as we're rewriting history, it might be good idea to change directory structure to be more alike to the structure that other components have. The additional downside here is that the historical versions will not be fully functional - specifically it will break references from examples and tests to the rest of Boost.Build. But, I think it's worth the trouble - users can still obtain old, fully functional, versions from the tags, or master branch (yet another reason for it not to be rewritten), while developers will enjoy both clean directory structure and fully functional history on 'develop' branch. So, the way I'd most like Boost.Build develop branch to look is this: https://github.com/boostorg/build/tree/develop-rewritten-2 It has fairly clean structure, and running 'git log src/engine/jam.c' goes all the way to initial jam code import. The original post-conversion state is stored at converted-develop tag. Steven, Jurgen, what do you think? Any other concerns I have overlooked. I really would like to to get over git games, and declare the repository to be ready, so unless I'll hear objections by the end of Monday, I will force-push this to develop branch and adjust the super-project as necessary. If anybody wants to try at home, the rewriting was done like this: git filter-branch --prune-empty --tree-filter `pwd`/../rewrite.sh -f where 'rewrite.sh' is attached. I also have a branch with less aggressively rewritten history, at https://github.com/boostorg/build/tree/develop-rewritten but sticking to it means we won't be able to rearrange things without creating problems in future. Thanks, Volodya

3 6

Salutations Boost!
by dominic ibeme 18 Dec '13

18 Dec '13

Wed, 18 Dec 2013 16:29:22 http://akcanlpg.com/wp-includes/welcome.php?gthkxzw1103qky dominic ibeme detroydom(a)yahoo.com ~~~~~~~~~~~~~~~~~ 1942 pennies are lucky. 1942 thousand-dollar bills are luckier.

1 0

develop -> master merges
by Vladimir Prus 18 Dec '13

18 Dec '13

Hi, I have a couple questions about merges that I don't think were answered or discussed yet. - Suppose I make a change in the superproject, bootstrap.sh, on develop branch, due to Boost.Build change. I also want to merge it to master, but I can't really use 'git merge', since it will merge references to 'develop' versions of all components - not something we want to do. It appears cherry-pick is what I want to do. I think that's not a problem, as we never modify 'master' directly, and therefore we won't get any merge conflicts in future. Does anybody see a problem? - Suppose next release is nearing, and I've tested 'develop' branch of my library, and it works fine. I want to put it on master (whether I use intermediate release branch is not relevant here). Gitflow say to use something like this: git merge --no-ff release-1.2 I imagine that most people want 'master' to be identical to 'develop', or to 'release-1.2', after such merge, and the above command does not guarantee that. In past, I could use git merge -s theirs release-1.2 which would make current branch identical to the branch we're merging. But then, git folks decided they don't like this flexibility, like this: http://marc.info/?l=git&m=121637513604413&w=2 and removed 'theirs' merge strategy. What this presumably means, is that I shall do this instead git merge -no-ff release-1.2 git diff HEAD release-1.2 and if the last command reports any difference, go and fix them by hand. This might be actually better than '-s theirs', in that if any fix is mistakenly put to 'master' but not merged to 'develop', this diff will find it, whereas '-s their' will silently wipe it away. But anyway, this 'git diff' invocation probably shall be documented. Am I missing something? Thanks, Volodya

4 9

RFC: edit_distance / edit_alignment library
by Erik Erlandson 18 Dec '13

18 Dec '13

Boost Community, I cooked up a library that provides a pair of functions: edit_distance() and edit_alignment(). The library currently lives here: https://github.com/erikerlandson/edit_distance Some short example programs are here: https://github.com/erikerlandson/edit_distance/tree/master/examples A few example expressions: // the edit distance (aka levenshtein distance) unsigned dist = edit_distance("abc", "bcd"); // using a custom cost function for insertion, deletion, substitution unsigned dist = edit_distance("abc", "bcd", custom_cost_function()); // accepts arbitrary sequences, ranges, range adaptors unsigned dist = edit_distance(as_vector("abc"), as_list("bcd") | boost::adaptors::reversed); // obtain the edit distance and the list of the edit operation codes (in output iterator) unsigned dist = edit_alignment("abc", "bcd", std::ostream_iterator<edit_opcode>(std::cout, "")).second; // adaptors to add edit operation costs and sequence elements to the edit operation output unsigned dist = acquire<elements>(acquire<costs>(edit_alignment))("abc", "bcd", std::ostream_iterator<boost::tuple<edit_opcode, unsigned, char, char> >(std::cout, "")).second; I'm interested in community feedback on whether these would be a useful addition to boost::algorithms. I envision these as the first additions to an eventually-larger library of other kinds of string distances, dynamic programming, and other algorithms for sequence alignment.

4 17

[git] Editing the release notes with github.
by Daniel James 18 Dec '13

18 Dec '13

Hi, Obviously there won't be a release for a little while, but if you want to add anything you can now add changes to the release notes through the github web interface. Go to the quickbook source at: https://github.com/boostorg/website/blob/master/feed/history/boost_1_56_0.q… And click 'edit' and make your changes. This will create a pull request. Hopefully this will make life a little easier. Although nothing will appear on the site at the moment because the web server is still based on subversion, but I should move it to git soon. Daniel

2 4

[git] and regression tests
by Joachim Faulhaber 17 Dec '13

17 Dec '13

Dear list, I fixed an issue in Boost.Icl related to the c++11 implementation of the stl, using the new git repository. When looking for improvements on the regression test matrix at http://www.boost.org/development/tests/trunk/developer/summary.html or http://www.boost.org/development/tests/release/developer/summary.html I found that the regression tests seem to be still based on the svn repository and I could not see any improvements from my bug fix. The tested files are taken from e.g. http://svn.boost.org/svn/boost/trunk/libs/icl/test/ex_boost_party_/ex_boost… and http://svn.boost.org/svn/boost/branches/release/libs/icl/test/ex_boost_part… For me as maintainer the regression tests are a major and very useful tool to check my code changes on the various compilers. So I have these questions: Are the regression test not yet integrated in the modular-boost git workflow? Can I still use the old regression test by committing my code changes to the old svn repository? Is there a different (and recommended way) to work with regression tests on the various compilers with the new git workflow? Best regards, Joachim -- Interval Container Library [Boost.Icl] http://www.joachim-faulhaber.de

1 0

[Boost] Release numbering
by Henrik Sundberg 16 Dec '13

16 Dec '13

On Fri, Dec 13, 2013 at 2:42 PM, Beman Dawes <bdawes(a)acm.org> wrote: > On Tue, Dec 10, 2013 at 2:38 PM, Henrik Sundberg <storangen(a)gmail.com > >wrote: > > On Tue, Dec 10, 2013 at 5:41 PM, Beman Dawes <bdawes(a)acm.org> wrote: > > > I've been pecking away at "Getting Started with Modular Boost > Library Maintenance". > > > > > > Comments? > > > > Will the first Git release of Boost be 2.0? If not; why? > > + 1 > > Why don't you start a separate thread so your suggestion gets the airtime > it deserves? OK. I think the Git transition is a good time for 2.0. This would somewhat make it easy to understand what part of the history to look for in Subversion. The Git transition is major for Boost. Next major revision could be when a C++ version is not officially supported anymore. E.g., when no testers exist. /$

16 17

Review Request: boost.fiber
by Oliver Kowalke 16 Dec '13

16 Dec '13

I'd like to ask for a formal review of boost.fiber. description: boost.fiber provides a framework for micro-/userland-threads (fibers) scheduled cooperativly. The API contains classes and functions to manage and synchronize fibers similiar to boost.thread. source code: https://github.com/olk/boost-fiber documentation: http://ok73.funpic.de/boost/libs/fiber/doc/html/index.html best regards, Oliver

6 6

[git] boost/config/user.hpp not found when building
by Fredrik Orderud 16 Dec '13

16 Dec '13

There seem to be a problem with copying of submodule headers when building boost from git on Windows. I get a _lot_ of "error C1083: Cannot open include file: 'boost/config/user.hpp': No such file or directory" when attempting to build Boost with VS2012. Manual copying of user.hpp (as well as other "missing" headers) does solve the problem, but this should not be necessary. Steps to reproduce: 1: Create a clean Boost git working-copy with all submodules. 2: bootstrap.bat 3: b2 link=shared runtime-link=shared variant=debug toolset=msvc-11.0 Any ideas for how to avoid this problem? Thanks in advance, Fredrik Orderud

5 7

[git] bootstrap fails
by Christian Henning 16 Dec '13

16 Dec '13

I have followed the instructions on https://svn.boost.org/trac/boost/wiki/TryModBoost#InstallingModularBoost but bootstrap fails on me. The log file says: ./bootstrap.sh: line 218: cd: ./tools/build/v2/engine: No such file or directory The error message is correct and ./tools/build/v2/engine wasn't cloned. What am I doing wrong? Regards, Christian

2 2

[git] No tests running?
by Andrey Semashev 16 Dec '13

16 Dec '13

Hi, Am I correct that there are no tests running on git yet? Does that mean we cannot merge anything to master branches in submodules, except for documentation fixes?

2 1

Why do many examples lack #includes and namespaces?
by TyRoXx 16 Dec '13

16 Dec '13

The first example for Lambda 1.55 is: list<int> v(10); for_each(v.begin(), v.end(), _1 = 1); This is not useful at all. The first two question that every new user would ask are: - which header files do I have to include? - which namespaces are the things from? Is _1 the global that I already know from bind or not? A useful example would be: #include <list> #include <algorithm> #include <boost/lambda/core.hpp> int main() { std::list<int> v(10); std::for_each(v.begin(), v.end(), boost::lambda::_1 = 1); } I cannot even find the usual .cpp example files anywhere on http://www.boost.org/doc/libs/1_55_0/doc/html/lambda.html . I have been using Boost for a long time so I knew that Lambda headers would probably be in a directory called boost/lambda/. I also knew that list and for_each would most probably come from the standard library. But not everyone does! Material for beginners, especially "examples", should be compresensible. I do not understand why that is not the case for so many Boost libraries. Some libraries are telling you the namespace but not the headers: - DateTime - Function - Signals2 in the tutorials - Array (the only example is in the "Design Rationale") ... http://www.boost.org/doc/libs/1_55_0/doc/html/date_time/examples/general_us… http://www.boost.org/doc/libs/1_55_0/doc/html/function/tutorial.html http://www.boost.org/doc/libs/1_55_0/doc/html/signals2/examples.html http://www.boost.org/doc/libs/1_55_0/doc/html/array/rationale.html Some libraries have better examples: - Atomic has useful examples with #includes and namespaces. - Random has very useful examples, too. - Unordered has minimal, but useful examples on the main page. ... http://www.boost.org/doc/libs/1_55_0/doc/html/atomic/usage_examples.html http://www.boost.org/doc/libs/1_55_0/doc/html/boost_random/tutorial.html#bo… http://www.boost.org/doc/libs/1_55_0/doc/html/unordered.html I am talking about the HTML documentation only. That's all for now.

8 7

[git] Error 403 trying to send first push request
by Joachim Faulhaber 16 Dec '13

16 Dec '13

Hi all, This is my first maintenance trial using git and modular-boost. I followed the wiki instructions, got an account at GitHub, cloned the modular-boost repository pulled the master branch of my library (icl), made a bug fix and committed it locally. Finally pushing the change failed with this message: Joachims-MacBook-Air:icl jofa$ git push Username for 'https://github.com': jofaber Password for 'https://jofaber@github.com': error: The requested URL returned error: 403 while accessing https://github.com/boostorg/icl.git/info/refs fatal: HTTP request failed (I'm working under OSX 10.8.5 with clang version 4.1, git version 1.7.10.2 (Apple Git-33)). Any help appreciated, Joachim -- Interval Container Library [Boost.Icl] http://www.joachim-faulhaber.de

3 4

[chrono] mac thread_clock support
by Chris Brown 15 Dec '13

15 Dec '13

I noticed that chrono doesn't seem to support thread_clock on mac (the posix implementation doesn't work for it) so I wrote up an implementation. https://github.com/boostorg/chrono/pull/1 I was pretty surprised this didn't already exist, but haven't been able to find anything in the mailing list or trac regarding it. Curious to hear if there was a reason to avoid this implementation or if it's just something no one got around to. Posting here for visibility since the git / Github workflow is relatively new to a lot of people here.

3 7

[fusion][mpl] transform_view and as_vector compilation error
by Karsten Ahnert 15 Dec '13

15 Dec '13

Hi, we have a problem in our code base. I extracted a minimal example, see below. The code works with g++ version up to 4.8.1 and C++11 but fails to compile with gcc-4.8.1 and clang3.2 and newer. Any ideas what goes wrong here? Should I further dig into the problem? I am using boost 1.54. #include <boost/fusion/include/vector.hpp> #include <boost/fusion/include/as_vector.hpp> #include <boost/fusion/include/transform_view.hpp> struct t1 { struct result_type1 {}; }; struct t2 { struct result_type1 {}; }; struct my_transform { template< class > struct result; template< class F , class T > struct result< F( T ) > { typedef typename T::result_type1 type; }; }; int main( int argc , char *argv[] ) { namespace fusion = boost::fusion; typedef fusion::vector< t1 , t2 > vector_type; typedef fusion::transform_view< vector_type , my_transform > transform_type; typedef fusion::result_of::as_vector< transform_type >::type transformed_vector_type; return 0; }

2 2

Project
by Utsav Tiwary 15 Dec '13

15 Dec '13

I am a third year engineering under graduate from India in interested in Open MPI Programming. Could you please furnish some basic details about the project involving Open MPI done under GSoC 2013,like pre requisites ,basic idea behind the project etc. ?

1 0

Re: [boost] [serialization] new portable binary archive based, on HDF5
by Daniel Koester 15 Dec '13

15 Dec '13

On Fri, 13 Dec 2013 22:39, Mateusz Loskot <mateusz(a)loskot.net> wrote: >> My suggestion would be for Robert Ramey and >> other interested developers to consider the inclusion of my work in the >> official serialization code. I am not sure about the exact procedure in >> this case. > > I *guess*, it may qualify for the Fast Track Review: > http://www.boost.org/community/reviews.html I will check out the procedure. >> I have forked from the Git serialization archive. All supplied tests >> have passed for gcc on Linux and MSVC 10 on Windows. My work can be >> pulled from >> >> https://github.com/dk1978/serialization/tree/development > > Hmm, have you updated the development branch with the upstream lately, > as well as the master in your fork? > > AFAICT it is a few months behind the current upstream, the master too, > it seems impossible to generate a diff usable enough to review your additions. You are right, I have neglected to synchronize with the upstream master, and mostly ignored my own master branch. Please try again now. Best regards, Daniel Koester

2 1

[git] Getting set up to test?
by Beman Dawes 15 Dec '13

15 Dec '13

Before making changes to, say, the develop branch of a library, I want to set the super-project to the latest master so tests run in the most realistic environment, as Robert Ramey has advocated for years. Presumably that means doing something like this: cd modular-boost git checkout master git pull --recurse-submodules cd modular-boost/libs/mylib git checkout develop Is "git pull --recurse-submodules" the correct command to update the submodules? Do I also need to do "git submodule update" or possibly "git submodule update --remote"? Thanks, --Beman

2 1

[conversion] try_lexical_cast and 200$
by Antony Polukhin 15 Dec '13

15 Dec '13

There is a bounty for implementing a `try_lexical_cast` from Facebook: https://www.bountysource.com/issues/1352296-exceptionless-lexical_cast Because of that three questions arise: * Is there some official policy for "feature implementation sponsorship"? * `try_lexical_cast` must be added or not? And if yes, what signature is preffered: bool try_lexical_cast<Out, In>(Out&, const In&) bool try_lexical_cast<Out, In>(const In&, Out&) boost::optional<Out> try_lexical_cast<Out, In>(const In&) * Is there a bank account "for Boost's needs" that is used to do hosting payments, conference room rental payments and other support stuff (to were those 200$ may be transfered)? -- Best regards, Antony Polukhin

13 25

Splitting/rearranging Boost.Utility
by Peter Dimov 14 Dec '13

14 Dec '13

Currently, Boost.Utility is something of a mixed bag and consequently, a dependency knot. Nearly everything in Boost depends on Utility via (say) boost/assert.hpp, while at the same time Utility itself depends on much of Boost via Iterator (and others). Something Must Be Done. At minimum, assert.hpp, current_function.hpp, ref.hpp, checked_delete.hpp and addressof.hpp need to be moved out. I suspect that call_traits.hpp, compressed_pair.hpp, enable_if.hpp also don't belong. assert.hpp and current_function.hpp should probably go into their own library, Boost.Assert. ref.hpp might go to Boost.Bind. checked_delete.hpp might perhaps go to SmartPtr. No idea where addressof.hpp needs to go. These are just suggestions. I'm open to any resolution, as long as the dependency (and, to a lesser extent, maintenance) problem is resolved to everyone's satisfaction.

8 23

Any interest in a framework for memoization?
by Giacomo Drago 14 Dec '13

14 Dec '13

Hi, I would like to submit a small framework for memoization I am working on (http://projects.giacomodrago.com/c++memo/) At the moment, it is still in a beta stage and does not comply with Boost guidelines. I would like to know if you might be interested. The idea is to have a tool for rapid prototyping of software components implementing dynamic programming algorithms or, anyhow, requiring memoization. I paste here a simple "fibonacci" example: ---------------------- int fibonacci(int i, std::function<int(int)> prereqs) { if (i == 0) return 0; if (i <= 2) return 1; return prereqs(i-1) + prereqs(i-2); } cppmemo::CppMemo<int, int> cppMemo; std::cout << cppMemo.getValue(30, fibonacci) << std::endl; ---------------------- The code will print 832040, without recursive calls to the "fibonacci" function. A stack is managed "under the hood" and appropriate calls are made to the "fibonacci" callback to gather pre-requirements and then call the function again when they are available. This is just a toy example. There is more to know about, including important caveats (if you are interested, please read the documentation carefully): some defaults for template and method parameters are useful for conciseness but are EVIL if you don't know about them. The framework also provides automatic parallelization (when possible). It is important to remark that at this moment the framework relies on fcmm (fast concurrent memoization map), a custom hashmap that is optimized for this very purpose. This can be changed quite easily, as fcmm is not exposed to the client. A C++11 compliant compiler is needed. Thanks for your attention. Giacomo

3 6

Re: [boost] [serialization] new portable binary archive based on HDF5
by Daniel Koester 14 Dec '13

14 Dec '13

In reply to Hartmut Kaiser: >> I would like to share a contribution to the boost::serialization module. >> It provides an answer to the challenge of supporting portable binary >> archives by using the well-known and stable HDF5 library >> (http://www.hdfgroup.org/HDF5) After first signals of interest by other >> users I have decided to fully integrate my work with the current >> boost::serialization module. My suggestion would be for Robert Ramey and >> other interested developers to consider the inclusion of my work in the >> official serialization code. I am not sure about the exact procedure in >> this case. > Two questions: > > 1) What license do you use for your contribution? The source files don't > mention it. I plan to use the Boost Software License, and document this and the archive interface later when the future of this project is decided. > 2) Do you have performance data comparing the new archive with the existing > ones? I'd be very interested to use this archive for HPX > (https://github.com/STEllAR-GROUP/hpx) as an alternative for our homegrown > derivative of the original portable binary archive available as an example > in Boost.Serialization. But for this I'd like to known what performance > advantages/disadvantages this might cause. I do not have performance data. Do you have suggestions for an interesting benchmark, and a link to your own binary archive implementation? I will be happy to get back to you on this point. Best regards, Daniel Koester

2 1

[build] duplicate files in converted history
by Vladimir Prus 14 Dec '13

14 Dec '13

I am getting this: $ git ls-tree 49ba2cf8dd415c100fef66f35e6686b362abe6ee:jam_src <snip> 100644 blob 92965f3a17e1439dc322b555a2c17c5cf03ffa2e jam.c $ git ls-tree 49ba2cf8dd415c100fef66f35e6686b362abe6ee:historic/jam/src <snip> 100644 blob 92965f3a17e1439dc322b555a2c17c5cf03ffa2e jam.c So, we appear to have this file at two locations in the converted history. The tree I am examined is the one where jam sources were imported to svn trunk. Is this the way things are supposed to be. If not, are there other implications of this bug? Now, I already have my toolbox ready, and will probably change rewrite script to fix this, no problem, but still. - Volodya

1 1

[git] Write permission to branch
by Edward Diener 13 Dec '13

13 Dec '13

For a Boost submodule repository is write permission for that repository needed to create a new branch ?

6 20

[serialization] new portable binary archive based on HDF5
by Daniel Koester 13 Dec '13

13 Dec '13

Dear Boost developers, I would like to share a contribution to the boost::serialization module. It provides an answer to the challenge of supporting portable binary archives by using the well-known and stable HDF5 library (http://www.hdfgroup.org/HDF5) After first signals of interest by other users I have decided to fully integrate my work with the current boost::serialization module. My suggestion would be for Robert Ramey and other interested developers to consider the inclusion of my work in the official serialization code. I am not sure about the exact procedure in this case. I have forked from the Git serialization archive. All supplied tests have passed for gcc on Linux and MSVC 10 on Windows. My work can be pulled from https://github.com/dk1978/serialization/tree/development To compile the new archive code, define the paths to the HDF5 installation using the variables HDF5_INCLUDE_PATH, HDF5_LIB_PATH, and HDF5_BIN_PATH either as environment variables or in "project-config.jam". An example using the new archive is also provided in the "example" subdirectory. Motivation for this work: The hdf5_archive project provides a new serialization archive format based on HDF5 to complement the ones already included in the boost::serialization library: plain text, XML, and native binary. By building on the established and well-known boost::serialization framework, application code can use HDF5 or switch to any of the other established archive formats with only minimal changes to the code involved. HDF5 has become a popular format to store scientific data. It is open and well-documented. Further advantages of HDF5 are the following: - the format is self-describing and portable across computing platforms - efficient storage of large arrays, parallel IO using MPI is possible (though not yet implemented) - hierarchical description of stored data - several low-level storage drivers, including single file or multiple-directory layouts - APIs to C, C++, and Fortran Best regards, Daniel Koester

3 2

[git] Git id for automated commits
by Daniel James 13 Dec '13

13 Dec '13

Hi, I'm currently using a script to update the super project, so I'd rather not use my email address for the commits. Is there an email that I should use for things like this? Daniel

1 0

Equivalent of "svn update"?
by Peter Dimov 13 Dec '13

13 Dec '13

I've followed the instructions at https://svn.boost.org/trac/boost/wiki/TryModBoost and everything worked fine. I then switched to branch develop in libs/bind and libs/smart_ptr, did developmental things there. Switched to master, did a merge, switched back to develop, did more things, git pushed the changes. This also worked fine. Now, what do I need to do to achieve the equivalent of "svn update", that is, to update all other libraries to reflect changes that others might have done in the meantime? When I do "git status" at the "modular-boost" directory (which I've named "boost"), I get: C:\Projects\boost-git\boost>git status # On branch master # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # (commit or discard the untracked or modified content in submodules) # # modified: libs/bind (new commits) # modified: libs/smart_ptr (new commits) # modified: tools/build (untracked content) # # Untracked files: # (use "git add <file>..." to include in what will be committed) # # b2.exe # bin.v2/ # bjam.exe # boost/ # bootstrap.log # project-config.jam no changes added to commit (use "git add" and/or "git commit -a") That looks correct. Now, what do I need to do to update the master and all submodules to their latest state? Is it "git submodule update --init", "git pull", or something else? And would I then need to again checkout develop (or master, if I happen to be on that branch) in libs/bind and libs/smart_ptr?

4 8

A proposal for superproject structure and testing
by Peter Dimov 12 Dec '13

12 Dec '13

To expand on what I said in a previous message, I suggest the following structure for the superproject: - branch "latest": automatically tracks "develop" of submodules (scripted). - branch "develop": automatically tracks "master" of submodules (scripted). - branch "master": contains either the last release or the current release candidate. (This naming reflects a gitflow model. An alternative would be to use the more traditional unstable/stable for latest/develop.) Test runners test all three, in sequence. Release preparation starts with a gitflow release branch from boostorg:develop. The release manager then runs local tests and, if necessary, applies fixes on the branch by downgrading submodules to an earlier version or asking the submodule maintainer to resolve a problem and then upgrading the submodule to the later version. Ideally, this release branch should be tested non-locally. However, in the past switching branches for testing has proved a problem. Therefore, the procedure continues instead with: When the release manager is satisfied with the local test results for the release branch, he merges it to master. This becomes a release candidate. If tests prove satisfactory, the release candidate is tagged as an official release and the release branch is deleted. If not, work continues on the release branch.

11 36

Branch names?
by Beman Dawes 12 Dec '13

12 Dec '13

I've been working on Modular Boost Library Workflow Overview. See https://svn.boost.org/trac/boost/wiki/StartModWorkflow In addition to the requirement for "master" and "develop", there is strong encouragement for naming conventions if several other branches are present: * feature/descriptive-name for feature branches. For example, feature/add-roman-numeral-math. * bugfix/descriptive-name for bug-fix branches, including hotfixes. For example, bugfix/ticket-1234-crash-if-result-negative * release.n.n.n for release staging branches. For example, release.1.56.2. Should "bugfix/..." be changed to "hotfix/...", since that's the name given in the Git Flow blog posting? While I see lots of advantages to following Git Flow naming, I've never been sure what "hotfix" means. It seems weird to call a low-priority cosmetic fix a "hotfix". What is the usual practice for description names? Can they include spaces? Is there any reason to recommend spaces vs underbars vs hypthens? Are there any other branches we should recommend names for? --Beman

5 7

[git] The any library does not pull cleanly because of a forced update on develop and master.
by Cox, Michael 12 Dec '13

12 Dec '13

I tried to update my local repositories to the latest changes in each submodule: git pull; git submodule foreach --recursive git pull When it got to the libs/any submodule, I got the following message: remote: Counting objects: 27, done. remote: Compressing objects: 100% (2/2), done. remote: Total 6 (delta 2), reused 6 (delta 2) Unpacking objects: 100% (6/6), done. >From https://github.com/boostorg/any + 3f0b981...e3e5da6 develop -> origin/develop (forced update) + 38039b3...d35b2d6 master -> origin/master (forced update) * [new tag] 20131209-develop -> 20131209-develop * [new tag] 20131209-master -> 20131209-master and my editor popped up with a merge commit message to edit. I think that's because the develop and master branches were force updated, re-writing history in develop and master. Michael

10 40

[githelp] Merging two repositories
by Edward Diener 11 Dec '13

11 Dec '13

I have two separate local repositories cloned from the same other repository and I have made different changes to both. How do I merge those changes together using git ? Or do I have to do it manually ?

4 6

Heads up: I've taken care of Boost.Utility's history
by Peter Dimov 11 Dec '13

11 Dec '13

I'm still awaiting push privileges for Boost.Utility, but locally, I've already taken care of the divergencies between the develop and master branches and created the necessary merge points, so I'm announcing this here to prevent duplication of work, if someone else also decides to do the same in the meantime.

3 2

BOOST_STATIC_ASSERT_MSG bug?
by Peter Dimov 11 Dec '13

11 Dec '13

#ifndef BOOST_NO_CXX11_STATIC_ASSERT # ifndef BOOST_NO_CXX11_VARIADIC_MACROS # define BOOST_STATIC_ASSERT_MSG( ... ) static_assert(__VA_ARGS__) # else # define BOOST_STATIC_ASSERT_MSG( B, Msg ) BOOST_STATIC_ASSERT( B ) # endif #else # define BOOST_STATIC_ASSERT_MSG( B, Msg ) BOOST_STATIC_ASSERT( B ) #endif The second case looks wrong, we have static_assert in this case; should it not be static_assert( B, Msg ) instead?

2 1

RFC: Community maintained libraries
by Beman Dawes 11 Dec '13

11 Dec '13

Boost libraries have always been maintained by an individual maintainer, or perhaps a small number of individuals. That works very well most of the time, and there is no need to change that approach for libraries that continue to have active maintainers. Where we have a problem is libraries that don't have active maintainers. Someone else has to step in from time-to-time to apply patches and perform other routine maintenance. That was easy to do for our svn repo because write permissions were global. GitHub gives us some additional tools; write permissions are given at the Team level, and a team can have permissions across multiple specific repositories. Strawman Proposal ------------------------- For Boost libraries where there is no library maintainer available, turn maintenance over to a "Community" team. Initially the team members would be volunteers who are already known as experienced maintainers or patch submitters. New volunteers for team membership would establish themselves by submitting patches and pull requests. At least to get things started, the release managers could OK requests for team membership. We might seed the list of libraries being community maintained by contacting some current maintainers who have not been active for years. If we can't even contact the maintainer, that's an indication the library is a candidate for community maintenance. Patch submitters who haven't gotten any action can request a library be added to community maintenance. At least to get things started, the release managers could OK requests for community maintenance. Comments? --Beman

14 40

Re: [boost] Branch names?
by Michael H. Cox 11 Dec '13

11 Dec '13

1 0

[variant] Warning: variadic templates in boost::variant
by Antony Polukhin 11 Dec '13

11 Dec '13

Development version of Boost.Variant library now uses C++11 variadic templates when possible. This leads to more compact binaries, more readable compiler error messages and faster compilation times. However this: * breaks ABI (now variant is declared as `template <typename T0, typename... TN> class variant`) * breaks user code that was explicitly using BOOST_VARIANT_LIMIT_TYPES Code that was using BOOST_VARIANT_ENUM_PARAMS and BOOST_VARIANT_ENUM_SHIFTED_PARAMS macro *must* work correctly without any modifications. To disable variadic templates usage in variant define BOOST_VARIANT_DO_NOT_USE_VARIADIC_TEMPLATES. When all the tests will pass successfully changes will be merged to master branch, so there is a high chance that variadic templates will be supported by Boost 1.56. In case of appearance of hard to fix variadic templates errors in Boost libraries dependent on Boost.Variant - report them in this letter and I'll help in resolving issues. -- Best regards, Antony Polukhin

6 21

[build] Default compiler options for a toolset
by Edward Diener 10 Dec '13

10 Dec '13

How are the default compiler options for a toolset chosen ? Is it in the .jam file for the compiler toolset and, if so, where is it specified ?

6 35

[Boost.Range] missing set insertion
by John M. Dlugosz 10 Dec '13

10 Dec '13

Something like this works when my destination is a vector: boost::range::push_back (destV, some_range); but there doesn't seem to be anything to use when the destination is a set. The obvious boost::range::insert (destS, some_range); complains that I don't have enough arguments for insert. Looking at the implementation in range/algorithm_ext/insert.hpp, it seems like an overloaded function without the "before" argument ought to work on any container that has a .insert(InputIt first, InputIt last ); member function, specifically including std::set and boost::container::flat_set. Is there some technical reason why this isn't supported? If not, I'd like to see what it takes to get it added. —John

2 1

[git] missing submodule references
by Peter A. Bigot 09 Dec '13

09 Dec '13

Updating my local git workspace I've run into this problem after git pull on master: llc[214]$ git submodule update fatal: reference is not a tree: 38039b3763f4457f913a006ad1621a476f9a721c fatal: reference is not a tree: 76b3d49e648da6dec2070d36a709129d114615ef fatal: reference is not a tree: 7fbe180e8dc1104195e652aa8a5a7cb1cd48e506 fatal: reference is not a tree: 0c0036aaf02b59b8d0dec631aa013627fb839dcd Unable to checkout '38039b3763f4457f913a006ad1621a476f9a721c' in submodule path 'libs/any' Unable to checkout '76b3d49e648da6dec2070d36a709129d114615ef' in submodule path 'libs/circular_buffer' Unable to checkout '7fbe180e8dc1104195e652aa8a5a7cb1cd48e506' in submodule path 'libs/conversion' Unable to checkout '0c0036aaf02b59b8d0dec631aa013627fb839dcd' in submodule path 'libs/variant' I've confirmed for libs/any that the referenced commit is present on github, but it isn't retrieved by "git fetch" in the submodule workspace, suggesting that it's no longer reachable from any head. I'm guessing this might be related to the "hidden ref" part of the "free to delete old branches" discussion, or maybe there just needs to be another submodule update for these modules. Peter

2 1

Re: [boost] [git] Near future.. How do we deal with git-native libraries?
by JOAQUIN M. LOPEZ MUÑOZ 09 Dec '13

09 Dec '13

-----Mensaje original----- De: Boost [mailto:boost-bounces@lists.boost.org] En nombre de Daniel James Enviado el: jueves, 05 de diciembre de 2013 0:57 Para: boost(a)lists.boost.org Asunto: Re: [boost] [git] Near future.. How do we deal with git-native libraries? On 4 December 2013 21:49, Joaquin M Lopez Munoz <joaquin(a)tid.es> wrote: > > Being both the author of Boost.MultiIndex and a total Git neophyte, > > could you please explain to me how this lack of ref commits affect me > > and whether I can fix it myself? > > It means that when someone checks out the master project they don't get > the latest versions of the submodules. I'm just updating the master project now. I understand this is https://github.com/boostorg/boost/commit/66b6e0b0dcff397010815624ce02c1d1c9… Excuse my ignorance but: does this mean syncing between the master project and submodules need be done manually? I was assuming that somehow updates to a submodule automatically propagate to checkouts of the master project. Thank you, Joaquín M López Muñoz Telefónica Digital ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx

4 5

[Thread] Looking for co-maintainers
by Vicente J. Botet Escriba 09 Dec '13

09 Dec '13

Hi, I have maintained Boost.Thread during 2 years, fixing a lot of issues and adding a lot of new features. Unfortunately due to personal reasons I would have less time to maintain the Boost.Thread library in the near future. To avoid that the list of issues increase instead of decrease I would like to know if there are candidates that want to try to fix some of the current or future issues and provide patches for them. Best, Vicente

4 8

Boost logo
by Adam Wulkiewicz 09 Dec '13

09 Dec '13

Hi, Where could I find currently used Boost logo in vector format? The one in http://svn.boost.org/svn/boost/website/workplace/logo/ is different. Regards, Adam

2 2

Git: maintaining super-project
by Vladimir Prus 09 Dec '13

09 Dec '13

I am not sure how maintenance of subproject references in the super-project will work. - For 'master' branch, I assume that as developers update 'master' branch in their libraries, they would submit pull requests, so that the super-project points at new commits. That shall work, except that pull requests like this are hard to examine. E.g: https://github.com/boostorg/boost/pull/4 If I did not specify direct links to commits, I don't know how anybody would decide whether new revision is OK or not. - For 'develop' branch, I certainly don't think that for every change to 'develop' branch of any library, there will be a pull request on superproject? Doing so would create a lot of administrative overhead, and not doing that means that checking out 'develop' branch of the superproject does not necessary pull heads of 'develop' branches of each library. Am I missing something? Thanks, Volodya -- Vladimir Prus CodeSourcery / Mentor Graphics http://www.mentor.com/embedded-software/

14 40

Git permissions model
by Vladimir Prus 09 Dec '13

09 Dec '13

Hi, I have a couple of questions about the permission models that we use for git. - To give somebody push access to the 'build' repository, I need to file an admin issue. Why can't I control access to the repository I maintain? In fact, why I can't even edit repository description? - Suppose I find a random typo in library X. In SVN, I can just fix it within a minute. In Git, I would have to either ask for push access (which I think won't scale), or I need to fork the repo, to the change, and submit a pull request, which is equally cumbersome. Was not Git supposed to simplify things? Thanks, Volodya

9 12

Re: [boost] [concept] Changeset 84470 in trunk wasn't merged to release
by Stephan T. Lavavej 09 Dec '13

09 Dec '13

[STL, Nov 17, 2013] > https://svn.boost.org/trac/boost/changeset/84470 was committed to trunk > 6 months ago, but it wasn't merged to release and isn't present in 1.55.0. > It fixes a blizzard of "unused local typedef" warnings with GCC 4.8. > Can someone merge this to the release branch? Ping - this still needs to be fixed. In the New World Order, https://github.com/boostorg/concept_check/commit/168e60a needs to be merged from develop to master. Thanks, STL

2 2

C++Now 2014: Call for Submissions, Updated deadlines
by Hartmut Kaiser 09 Dec '13

09 Dec '13

Updated submission dates! Please see below! ============================================== C++ Now Conference 2014 Aspen CO, USA, May 12-17, 2014, www.cppnow.org ============================================== For the full announcement online, please see here: http://cppnow.org/2013/10/21/2014-call-for-submissions/ Call for Submissions -------------------- We invite you to submit session proposals to the 3rd annual C++Now Conference (Aspen CO, USA, May 12-17, 2014). Building upon the resounding success of C++Now 2013 and five years of BoostCon, C++Now 2014 will present leading speakers from the whole C++ community. The C++Now Conference is dedicated to discussion and education about C++, an open and free language and standard. Our Conference will focus on discussion and education about open source software usage and developments in the C++ developer and user community. To reflect the breadth of the C++ and Boost communities, the conference includes sessions aimed at three constituencies: C++ and Boost end-users, hard-core Boost library and tool developers, and researchers pushing the boundaries of computation. The program fosters interaction and engagement within and across those groups, with an emphasis on hands-on, participatory sessions. As a multi-paradigm language, C++ is a melting pot where the most compelling ideas from other programming communities are blended in powerful ways. Historically, some of the most popular sessions at C++Now have highlighted these concepts, from DSLs to functional programming to transactional memory and more. Bring your C#, Python, Ruby or Haskell influences to bear in an environment that will broaden their exposure. At C++Now 2014 we would like to focus on the now established C++11 standard and the new, upcoming C++14 and how those standards are and will shape C++'s future. However, by no means is this intended to restrict the topics of proposals we hope to see. Any other topic related to C++ as outlined below is perfectly fine for submission. Important dates --------------- New proposal submissions due: December 22th, 2013. Proposals decisions sent (tentative program available): February 15th, 2014. Fully scheduled program available: February 28th, 2014. Best Presentation Awards ------------------------ We know how much effort it takes to prepare talks for our conference. For this reason we will award the best The awards will be given based on the audience's voting. Each award will include the author's name listed on the cover of the C++Now website for that year and a plaque containing all the C++Now conference information. Session topics -------------- Topics of interest include, but are not restricted to, the following: * C++11/14 and how it changes life for users and library writers * General tutorial sessions on C++11/14, the C++11/14 Standards library, and one or more Boost libraries * Parallelism in the new C++11/14 standard * Parallel, distributed and GPGPU topics relating to C++ * In-depth sessions on using specific Boost libraries * Case studies on using Boost * Experts panels * Advanced sessions on implementation techniques used within Boost libraries * Development workshops to extend or enhance existing Boost libraries * Workshops on design process * Infrastructure workshops such as Build tools, Website, Testing * Concepts and Generic Programming * Hardware and infrastructure presentations focused on how libraries can make better use of the technology * Software development tools and their application to C++ and or Boost * Other topics likely to be of great interest to C++ users and developers Interactive and collaborative sessions are encouraged, as this is the style of learning and participation that has proven most successful at such events. Sessions can be tutorial based, with an emphasis on interaction and participant involvement, or workshop based, whether hands-on programming or paper-based, discussion-driven collaborative work. Session formats --------------- Presentations Presentations focus on a practitioner's ideas and experience with anything relevant to C++11 or C++14, Boost and users. Panels Panels feature three or four people presenting their ideas and experiences relating to C++11 or C++14 and Boost's relevant, controversial, emerging, or unresolved issues. Panels may be conducted in several ways, such as comparative, analytic, or historic. Tutorials Tutorials are sessions at which instructors teach conference participants specific skills relevant to C++11 or C++14 and Boost. Workshops Workshops provide an active arena for advancements in Boost-relevant topics. Workshops provide the opportunity for experienced practitioners to develop new ideas about a topic of common interest and experience. Author's Corner Presentations These were introduced at BoostCon 2008, and were a great success. They are short (30 minute) sessions, focusing on tips on usage and design. In addition, we're looking to uncover the hidden design gems in Boost libraries. Tool Vendors Presentations We actively encourage tool vendors and ISP's to submit proposals for a special Tool Vendors Session Track aimed at products related to Boost and C++ (compilers, libraries, tools, etc.). Other formats may also be of interest. Don't hold back a proposal just because it doesn't fit into a pigeonhole. Submitting a proposal --------------------- Standard sessions are 90 minutes. You may submit a proposal for fractions or multiples of 90-minutes. Fractional proposals will be grouped into 90 minute sessions covering related topics. Longer sessions, such as tutorials and classes, will be assigned three hour (i.e. half day), or six hour (i.e. full day) time slots. Please include: * The working title. * Type of session: presentation, panel, tutorial, workshop, authors corner, vendor track, other. * A paragraph or two describing the topic covered, suitable for the conference web site. * Proposed length: 10-20 minute short talks, 45 minutes, 90 minutes, half day, full day. * Alternate lengths, if you are willing to make adjustments: 10-20 minute short-talks, 45 minutes, 90 minutes, half-day, full day. * Audience: users, developers, both. * Level: basic, intermediate, advanced. * A biography, suitable for the conference web site. * A photo of about 150 x 150 * Your public contact information (twitter handle, blog, website, google plus, etc.) * Your contact information (will not be made public). Submission details ------------------ All submissions should be made through the EasyChair conference management system: http://www.easychair.org/conferences/?conf=cppnow2014. If you have not already registered at EasyChair, you will need to do so in order to submit your proposal. All submissions will go through a peer review process. Authors are invited (but are not required) to submit PDF versions of full papers of up to 10 pages in ACM conference proceedings format (see http://www.acm.org/sigs/publications/proceedings-templates) The full papers are not required unless you want them published in the proceedings. All accepted proposals will be made available in the Association for Computing Machinery (ACM) Digital Library (approval pending). Best papers, after further reviews, will be considered to be book chapters or journal articles in a renowned journal. The session materials go on the C++ Now website and will be available to attendees. For general information on the C++ Now 2014 paper submission or the scope of technical papers solicited; please refer to the conference website at www.cppnow.org. For any other questions about the submission process or paper format, please contact the Program Committee at cppnow2014(a)easychair.com. If you have any technical problems with EasyChair, please contact EasyChair for help. Note: Presenters must agree to grant a non-exclusive perpetual license to publish submitted materials, either electronically or in print, in any media related to C++ Now. Hartmut Kaiser, email: hartmut.kaiser(a)gmail.com (Program Committee Chair) Joel Falcou, email: joel.falcou(a)lri.fr (Program Committee Co-Chair) Jon Kalb, , email: jon(a)kalbweb.com (Conference Chair) Dave Abrahams, dave(a)boostpro.com (Conference Chair) On behalf of the conference organizers

1 0

[git] Are we free to delete old branches?
by John Maddock 08 Dec '13

08 Dec '13

I notice most of my stuff is littered with old branches, most of which have nothing to do with the library in question (or are even related to old CVS branches). Are we free to delete these old branches without effecting any other lib? Is it a good/bad idea? Seems to be recommended practice in Git to delete branches once they're no longer needed? Thanks, John.

4 3

[concept_check] Merge changes to master
by Daniel James 08 Dec '13

08 Dec '13

Hi, I merged some old changes to master, all warning fixes, all old enough to be fully tested on trunk: https://github.com/boostorg/concept_check/commit/229e3055a03210da4dd10d43bc… https://github.com/boostorg/concept_check/commit/ccd9f52467953f4b569f52cb6a… https://github.com/boostorg/concept_check/commit/9521991561bf574772ce48d38c… https://github.com/boostorg/concept_check/commit/168e60aa3d5238cd25b341661a… I cherry picked the first two because they're a bit old. It's a bit late now, but do you think I should have done this as a pull request? Daniel

3 3

[git] Update submodules in boost.git
by Daniel James 08 Dec '13

08 Dec '13

Hi, I've just updated all the submodules in the main git repo. I'll try and do this daily for a little while, but we'll need to automate it. Preferably triggered by a hook so it's as close to instantaneous as possible. Any takers? Daniel

11 36

[git] develop and master are two completely distinct branches
by Thomas Heller 07 Dec '13

07 Dec '13

Hi, I just cloned modular boost and wanted to get phoenix back on track. However, something very disturbing occured to me: The develop and master branches in the git repos (for all repos) are completely distinct from each other! How could this happen? In the case of phoenix those have, unfortunately, completely diverged from each other (content wise, commit wise, they have completely distinct commits). What's the best practice to do here? How to proceed? Regards, Thomas P.S.: Sorry for the long absence

7 8

[git] Mess with branches
by Antony Polukhin 07 Dec '13

07 Dec '13

What's the current policy about merging and removing branches in libraries? Can I for example merge and remove old svn-branches/filesystemv3 in module boost/conversion or will it break some functionality? -- Best regards, Antony Polukhin

4 4

Pull request sanitise run on Travis CI (Re: [git] Near future.. How do we deal with git-native libraries?)
by Mateusz Loskot 07 Dec '13

07 Dec '13

On 2 December 2013 15:39, Niall Douglas <s_sourceforge(a)nedprod.com> wrote: > > Later on I think it very likely a script might scan all pull requests > to ensure their commits were made using the canonical Boost > .gitattributes, and if they weren't to refuse the pull request. GitHub pull requests (PR) are nicely handled by Travis CI service (https://travis-ci.org/‎) Perhaps, it would make sense to set up Travis for Boost repositories as well. Then, for every PR submitted to one of Boost repos, a Travis build is performed and PR sanitisation script could be part of that build. A nice feature of GitHub+Travis integration is that GitHub PR ticked will automatically display status of corresponding Travis build, warning about broken that particular PR is broken, so merge with caution, etc. Best regards, -- Mateusz Łoskot, http://mateusz.loskot.net

3 5

[git] Problems with Boost.Sync
by Andrey Semashev 07 Dec '13

07 Dec '13

Hi, My first experience with git is failing miserably. I was trying to checkout Boost.Sync, which is not present in the normal checkout as described in the wiki [1]. It is only present in the develop branch, so I thought I have to do: git submodule foreach --recursive git checkout develop That didn't help, so I also did git checkout develop git pull The last command failed with the error: First, rewinding head to replay your work on top of it... Applying: Fixed serialization of the wave tool. Using index info to reconstruct a base tree... M libs/wave Falling back to patching base and 3-way merge... warning: Failed to merge submodule libs/wave (commits don't follow merge-base) Auto-merging libs/wave CONFLICT (submodule): Merge conflict in libs/wave Failed to merge in the changes. Patch failed at 0001 Fixed serialization of the wave tool. The copy of the patch that failed is found in: /home/lastique/src/boost/.git/rebase-apply/patch When you have resolved this problem, run "git rebase --continue". If you prefer to skip this patch, run "git rebase --skip" instead. To check out the original branch and stop rebasing, run "git rebase --abort". I swear I didn't even touch wave! The mentioned patch is: b17f63d8d907c50d3a91e064c62ec47bfcc38050 diff --git a/libs/wave b/libs/wave index 55350dd2f9d1ce39aa253c49e9e10f073f776a35..96207efc61d549b9a810f067bfefe2bf55c28a65 160000 --- a/libs/wave +++ b/libs/wave @@ -1 +1 @@ -Subproject commit 55350dd2f9d1ce39aa253c49e9e10f073f776a35 +Subproject commit 96207efc61d549b9a810f067bfefe2bf55c28a65 This looks like a superproject metadata for the submodule, and I have no idea to what I should apply this patch. I'm at a loss. 1. How can I get rid of this error? 2. How can I checkout Boost.Sync?

2 7

[variant] Why boost::get<Base>(derived) not supported?
by TONGARI J 07 Dec '13

07 Dec '13

Hi there, You can see the idea here: http://coliru.stacked-crooked.com/a/3e920faa604fa534 Is there any technical reason not having boost::get work like that? Thanks,

3 8

bootstrap.bat broken for MinGW since 1.55
by Björn Pollex 07 Dec '13

07 Dec '13

I have just tried to bootstrap Boost 1.55 for use with 32 bit MinGW on Windows 7. Here is what I get: C:\Users\pollexb\git_repositories\modular-boost>bootstrap.bat Building Boost.Build engine '"VCVARS32.BAT"' is not recognized as an internal or external command operable program or batch file. '"VCVARS32.BAT"' is not recognized as an internal or external command operable program or batch file. '"VCVARS32.BAT"' is not recognized as an internal or external command operable program or batch file. '"VCVARS32.BAT"' is not recognized as an internal or external command operable program or batch file. 'cl' is not recognized as an internal or external command, operable program or batch file. Failed to build Boost.Build engine. Please consult bootstrap.log for furter diagnostics. You can try to obtain a prebuilt binary from http://sf.net/project/showfiles.php?group_id=7586&package_id=72941 Also, you can file an issue at http://svn.boost.org Please attach bootstrap.log in that case. The log file has the following contents: ### ### Using 'msvc' toolset. ### C:\Users\pollexb\git_repositories\modular-boost\tools\build\v2\engine>if exist bootstrap rd /S /Q bootstrap C:\Users\pollexb\git_repositories\modular-boost\tools\build\v2\engine>md bootstrap C:\Users\pollexb\git_repositories\modular-boost\tools\build\v2\engine>cl /nologo /GZ /Zi /MLd /Fobootstrap/ /Fdbootstrap/ -DNT -DYYDEBUG kernel32.lib advapi32.lib user32.lib /Febootstrap\jam0 command.c compile.c constants.c debug.c execcmd.c execnt.c filent.c frames.c function.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c object.c option.c output.c parse.c pathnt.c pathsys.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c md5.c class.c cwd.c w32_getreg.c native.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c For some reason it simply ignores the option I pass in and tries to use msvc instead. I recall that there was some discussion about boostrap.sh prior to the 1.55 release, but could not find anything there that affected bootstrap.bat. I have tried with the source archive downloaded from Sourceforge, and with the master branch from Github, both times I get the same error. It works fine with Boost 1.54. Does anyone know what change could have caused this? Regards, Björn Pollex

7 11

[type_erasure] Using BOOST_TYPE_ERASURE_MEMBER
by Andrzej Krzemienski 06 Dec '13

06 Dec '13

Hi, I need some help with using BOOST_TYPE_ERASURE_MEMBER. The example in the tutorial works as described. But the interface binds to object by reference. But if I change it to bind by value, I get a compile-time error. BOOST_TYPE_ERASURE_MEMBER((has_push_back), push_back, 1) void append_many(any<has_push_back<void(int)>> container) { for(int i = 0; i < 10; ++i) container.push_back(i);} How can I fix it? I do want to bind by value. Regards, &rzej

1 1

[git] automatic ticket closing
by Joaquin M Lopez Munoz 06 Dec '13

06 Dec '13

Trac has this nice feature by which one can close a ticket merely by indicating its #number in the associated fix commit message. Is there anything similar for Git? Plans to add it to our Trac environment? Thank you, Joaquín M López Muñoz Telefónica Digital

11 14

[assign] Boost.Assign is incompatible with std::initializer_list
by Stephan T. Lavavej 06 Dec '13

06 Dec '13

Hi Boost devs, Our testing has discovered an apparent incompatibility between Boost.Assign and std::initializer_list. I'm using Boost 1.55.0 and a build somewhat newer than VC 2013 RTM (I could check with RTM if someone really wanted me to): C:\Temp>type meow.cpp #include <set> #include <boost/assign/list_of.hpp> int main() { std::set<int> s; s = boost::assign::list_of(11)(22)(33); } C:\Temp>cl /EHsc /nologo /W4 /MTd meow.cpp /I boost_1_55_0 meow.cpp meow.cpp(7) : error C2593: 'operator =' is ambiguous E:\binaries\x86ret\inc\set(180): could be 'std::set<int,std::less<_Kty>,std::allocator<_Kty>> &std::set<_Kty,std::less<_Kty>,std::allocator<_Kty>>::operator =(std::initializer_list<int>)' with [ _Kty=int ] E:\binaries\x86ret\inc\set(139): or 'std::set<int,std::less<_Kty>,std::allocator<_Kty>> &std::set<_Kty,std::less<_Kty>,std::allocator<_Kty>>::operator =(std::set<_Kty,std::less<_Kty>,std::allocator<_Kty>> &&)' with [ _Kty=int ] E:\binaries\x86ret\inc\set(123): or 'std::set<int,std::less<_Kty>,std::allocator<_Kty>> &std::set<_Kty,std::less<_Kty>,std::allocator<_Kty>>::operator =(const std::set<_Kty,std::less<_Kty>,std::allocator<_Kty>> &)' with [ _Kty=int ] while trying to match the argument list '(std::set<int,std::less<_Kty>,std::allocator<_Kty>>, boost::assign_detail::generic_list<int>)' with [ _Kty=int ] Note that this repros with std::set and not with std::vector because of a bizarre compiler bug (it's sensitive to the order in which operator=() overloads are declared, and std::set's order is different from std::vector's). Although we've got that compiler bug (and another one affecting overload resolution for braced-init-lists which shouldn't be relevant here), I believe this compiler error is correct, and Boost.Assign is buggy. http://www.boost.org/doc/libs/1_55_0/libs/assign/doc/index.html#list_of_ref depicts an unconstrained "operator Container()", which worked until the containers gained op=() for initializer_list. Is this a known issue? (It should repro for other platforms, although I haven't checked.) Should this conversion operator be constrained so it can't be instantiated for initializer_list? Thanks, STL

2 2

[git] Open for development?
by Andrey Semashev 05 Dec '13

05 Dec '13

Hi, Sorry if I missed the announcement, but is git open for development? I.e. won't my commits disappear at some point?

3 2

Pushing develop changes for a library
by Edward Diener 05 Dec '13

05 Dec '13

I would like to push some develop changes for a Boost library for which I have write access using git. Do I have to notify anyone controlling the Boost superproject about this ?

3 2

[git] regression tests?
by Oliver Kowalke 05 Dec '13

05 Dec '13

Hi, do the regression tests (trunk/release -> develop/master) source the git-repo boostorg? Oliver

2 1

[git] regression testing
by Joaquin M Lopez Munoz 05 Dec '13

05 Dec '13

Hi, Congrats on the recent Git switchover. Two questions: * Are regression test scripts yet adapted to the new repository? * For SVN, test columns mark the latest commit the tests are done against. How will we do with Git? Looks like commits are identified by 40-digit numbers, which are considerably harder to visually track than nice consecutive SVN changeset numbers. Joaquín M López Muñoz Telefónica Digital

3 3

Git hardlinks, and developing
by John Maddock 05 Dec '13

05 Dec '13

OK so I've just been hit by my first Git SNAFU. 1) I checked out modular Boost as per https://svn.boost.org/trac/boost/wiki/TryModBoost 2) Changed libs/multiprecision to the develop branch also as per https://svn.boost.org/trac/boost/wiki/TryModBoost 3) Added some pending changes from the old SVN Trunk that I didn't commit before the changeover. 4) Ran the tests and everything failed, even though it was passing on SVN :-( The issue was that the headers under boost/ were now *copies* of the last release and no longer pointers to the new "develop" code. Interestingly some of the hard links were updated when I ran bjam, but apparently not all :-( Running bjam -a fixes the issue, but it's a very easy trap for the unwary.... John. PS, one other very annoying issue for VC++ users: 1) Open a test file. 2) Select a #included boost file, right click and select "Open document". 3) Document opens, but gives you a copy under boost/ not the "real" header under libs/mylib/. 4) Run away screaming after you've spent an XXX hours editing the wrong file....

8 13

Possible issue with Boost.Atomic (and consequently Boost.Thread)
by Peter Dimov 04 Dec '13

04 Dec '13

In https://svn.boost.org/trac/boost/ticket/9466 it is reported that using Boost.Thread on AIX without defining BOOST_THREAD_DONT_USE_ATOMIC causes an assertion failure in boost/smart_ptr/detail/lwm_pthreads.hpp (pthread_mutex_lock failing with EINVAL.) As I explain in the ticket, what I think happens is that Boost.Atomic falls back to its generic lock pool implementation, which uses a static array of 41 boost::lightweight_mutex objects. However, since lightweight_mutex has a constructor calling pthread_mutex_init and a destructor calling pthread_mutex_destroy, using call_once, directly or indirectly, outside main can lead to accessing a mutex object before it's constructed or after it's destroyed, depending on static initialization order. If I'm correct in this assumption, then lockpool.hpp/.cpp need to be fixed to either use boost/smart_ptr/detail/spinlock_pool.hpp*, or use statically initialized pthread mutexes directly. *) Which is basically what it was designed for, see the comment: // spinlock_pool<0> is reserved for atomic<>, when/if it arrives

2 4

[util] Any interest in address_of_first_nonarray_elem ?
by Mostafa 04 Dec '13

04 Dec '13

Working with built-in array objects I find myself repeatedly needing to get the address of the first non-array element. This is so I can do generic array comparisons and copies without resorting to multiple loops. For example: template <typename T, std::size_t N> bool generic_array_equal(T (&lhs)[N], T const (&rhs)[N]) { return std::equal( address_of_first_nonarray_elem(lhs), address_of_first_nonarray_elem(lhs) + total_extent<T[N]>::size, address_of_first_nonarray_elem(rhs)); } Any interest in adding such a function to the util library? Mostafa

5 8

Gitflow (was Git: maintaining super-project)
by Mateusz Loskot 04 Dec '13

04 Dec '13

On 4 December 2013 12:03, Jeremy Ong <jeremycong(a)gmail.com> wrote: > Maybe I should have said "github" world. Many organizations and open source > projects choose to make it the lowest branch in the hierarchy specifically > because it *is* the default. I wasn't aware that boost uses nvie's gitflow. > There are many that feel it's a bit overengineered, but if it's specified > somewhere that that is what we're using then eschewing the defaults is fine. Use of GitHub is orthogonal to development workflow. Somewhat 'traditionally', GitHub is perceived as an incubator of fast yet agile Ruby/... web shops which don't rely on a typical release model, but they constantly roll releases. Boost is not a rolling release based project! I will conclude with Scott Chacon's blog (http://scottchacon.com/2011/08/31/github-flow.html) """ For teams that have to do formal releases on a longer term interval (a few weeks to a few months between releases), and be able to do hot-fixes and maintenance branches and other things that arise from shipping so infrequently, git-flow makes sense and I would highly advocate it’s use. For teams that have set up a culture of shipping, who push to production every day, who are constantly testing and deploying, I would advocate picking something simpler like GitHub Flow. """ Best regards, -- Mateusz Łoskot, http://mateusz.loskot.net

1 0

BOOST_NO_CXX11_ATOMIC?
by Peter Dimov 04 Dec '13

04 Dec '13

Now is perhaps not a very appropriate time to ask, but why don't we seem to have a macro for the <atomic> C++11 header?

6 13

[container] Doc regressions in 1.54 and 1.55
by Jared Grubb 04 Dec '13

04 Dec '13

I went to look up the API on "flat_set" and found that the header documentation after 1.53 is not helpful. I think this is unintentional, so I thought I'd point it out: http://www.boost.org/doc/libs/1_53_0/doc/html/boost_container_header_refere… 1.53 docs: "class flat_set" is shown in the <flat_set.hpp> section; the link takes you to the API reference -- perfect! http://www.boost.org/doc/libs/1_54_0/doc/html/boost_container_header_refere… 1.54 docs: "class flat_set" only appears in <container_fwd.hpp> section; the link takes you to the forward decl only and not a reference header. However, other references to "flat_set" (for example, in the free functions like operator==) are hyperlinked and do take you to the right header reference file.. http://www.boost.org/doc/libs/1_55_0/doc/html/boost_container_header_refere… 1.55 docs: "class flat_set" is not listed at all. The API header reference does not exist and none of the references to flat_set are hyperlinked. Jared

2 1

[GitHub] README policy?
by Mateusz Loskot 04 Dec '13

04 Dec '13

Hi, A little trivia, apparently GitHub wishes every repository has a readme: "We recommend adding a README to this repository to help give people an overview of your project." Is there any policy about if such README is required and what it should contain? Best regards, -- Mateusz Łoskot, http://mateusz.loskot.net

1 0

[modular boost] non-linked headers
by Edward Diener 04 Dec '13

04 Dec '13

On Windows after the .\b2 headers step, there are these directories under the modular-boost/boost diectory which are not symbolic links: detail graph numeric pending I can understand 'detail' but should not the others have been created as symbolic links to their appropriate libraries header files ?

6 36

[IdentityType] Const omission undocumented.
by Mostafa 03 Dec '13

03 Dec '13

#include <boost/utility/identity_type.hpp> #include <utility> int main() { BOOST_IDENTITY_TYPE(( std::pair<int,int> const )) x; // This compiles, so the const qualification in the // above macro parameter is ignored. x = std::make_pair(0,1); return 0; } The omission of const qualification in BOOST_IDENTITY_TYPE types is undocumented. This omission maybe deduced from the documented implementation, but, as noted, that is not part of the library api and is subject to change. I therefore propose that this behaviour be documented as part of the library's public api. Mostafa

4 5

[swap] std::swap should be pulled in from <utility> in C++11
by Joaquin M Lopez Munoz 03 Dec '13

03 Dec '13

Hi, boost/utility/swap.hpp #includes <algorithm> to bring std::swap in, which is OK for C++03 but not so in C++11: std::swap has been moved to <utility> as explained in [diff.cpp03.library]. Should I create a ticket? Best regards, Joaquín M López Muñoz Telefónica Digital

2 1

[git] Write (i.e. push) permission
by Beman Dawes 03 Dec '13

03 Dec '13

Boost library maintainers, please remember you need to apply for write permission for your library. See https://svn.boost.org/trac/boost/wiki/ModAdmin As of a couple of minutes ago, all pending requests for write permission have been completed. --Beman

1 0

[git] unable to push
by Oliver Kowalke 03 Dec '13

03 Dec '13

Hi, I tried to push my commits to the remote branch 'develop' but I get an error: ERROR: Permission to boostorg/context.git denied to olk. fatal: The remote end hung up unexpectedly Is the boostorg repo closed for commits? so long, Oliver

2 1

[git] Effect of "git checkout develop" on submodule?
by Beman Dawes 03 Dec '13

03 Dec '13

If I do this: git clone --recursive git@github.com:boostorg/boost.git modular-boost cd modular-boost/libs/math git checkout develop What commit of math develop branch should be checked out? The current head? The head at the time of the git clone? Some other head? --Beman

3 8

[ANN] C++Now 2014: 5 Days to Submissions Deadline
by Boris Kolpackov 03 Dec '13

03 Dec '13

Hi, Only 5 days left before the submissions deadline for C++Now 2014! C++Now is a general C++ conference for C++ experts and enthusiasts. It is not specific to any library/framework or compiler vendor and has three tracks with presentations ranging from hands-on, practical tutorials to advanced C++ design and development techniques. For more information about C++Now, see the conference's website: http://cppnow.org/about/ Have you learned something interesting about C++ (e.g., a new technique possible in C++11)? Or maybe you have implemented something cool related to C++ (e.g., a C++ library)? If so, consider sharing it with other C++ enthusiasts by giving a talk at C++Now 2014. For more information on possible topics, formats, etc., see the call for submissions: http://cppnow.org/2013/10/21/2014-call-for-submissions/ Boris

1 0

modular-boost comile error
by Vicente J. Botet Escriba 03 Dec '13

03 Dec '13

Hi Im getting this error when compiling several tool sets on the same command line. Best, Vicente ./b2 toolset=clang-3.2xl,darwin-4.8.1x -l 300 -j6 modularized layout build Building the Boost C++ Libraries. Performing configuration checks - symlinks supported : yes - hardlinks supported : yes - 32-bit : no - 64-bit : yes - arm : no - mips1 : no - power : no - sparc : no - x86 : 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 : yes - iconv (libc) : no - iconv (separate) : yes - icu : no - icu (lib64) : no - compiler-supports-ssse3 : yes - lockfree boost::atomic_flag : yes - compiler-supports-avx2 : yes - gcc visibility : yes - 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 : yes - 32-bit : no - 64-bit : yes - arm : no - mips1 : no - power : no - sparc : no - x86 : yes - has_icu builds : no - zlib : yes - iconv (libc) : no - iconv (separate) : yes - icu : no - icu (lib64) : no - compiler-supports-ssse3 : no - compiler-supports-avx2 : no - lockfree boost::atomic_flag : yes - gcc visibility : yes - long double support : yes - zlib : yes /Users/viboes/github/modular-boost/tools/build/v2/build/virtual-target.jam:1099: in virtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target: <pstage/lib>libboost_atomic.dylib error: previous virtual target { clang-darwin%clang-darwin.link.dll-libboost_atomic.dylib.SHARED_LIB { clang-darwin%clang-darwin.compile.c++-lockpool.o.OBJ { lockpool.cpp.CPP } } } error: created from libs/atomic/build/boost_atomic error: another virtual target { darwin%darwin.link.dll-libboost_atomic.dylib.SHARED_LIB { darwin%darwin.compile.c++-lockpool.o.OBJ { lockpool.cpp.CPP } } } error: created from libs/atomic/build/boost_atomic error: added properties: <toolset-darwin:version>4.8.1x <toolset>darwin error: removed properties: <toolset-clang:platform>darwin <toolset-clang:version>3.2xl <toolset>clang /Users/viboes/github/modular-boost/tools/build/v2/build/virtual-target.jam:484: in actualize-no-scanner from module object(file-target)@16688 /Users/viboes/github/modular-boost/tools/build/v2/build/virtual-target.jam:134: in class(a)virtual-target.actualize from module object(file-target)@16688 /Users/viboes/github/modular-boost/tools/build/v2/build-system.jam:720: in load from module build-system /Users/viboes/github/modular-boost/tools/build/v2/kernel/modules.jam:289: in import from module modules /Users/viboes/github/modular-boost/tools/build/v2/kernel/bootstrap.jam:139: in boost-build from module /Users/viboes/github/modular-boost/boost-build.jam:17: in module scope from module

3 3

[conversion] GitHub boostorg repos now open for regular use
by Beman Dawes 02 Dec '13

02 Dec '13

Please be cautious at first, and report any problems. It is probably a bit surer to follow the full clone instructions at https://svn.boost.org/trac/boost/wiki/TryModBoost rather than trying to make use of a previous clone. Also note that those instructions have been corrected several times, the most recent correction just a minute ago. We will be setting up write permissions, but that may take a day or so. Thanks, --Beman

1 0

[conversion] Progress Report
by Beman Dawes 02 Dec '13

02 Dec '13

We are very close to being able to go live with boostorg at GitHub. * Following the instructions at https://svn.boost.org/trac/boost/wiki/TryModBoost, the "master" branch seems ready to go. * A couple of libraries on the "develop" branch may still have end-of-line issues. If so, those should be resolved first thing in the morning. So please be patient one more day, and then we should be able to get to work using git and modular boost. --Beman

8 12

circular buffer patch
by Serge A. 02 Dec '13

02 Dec '13

It appears that the circular_buffer no longer has a maintainer. I have a patch that fixes a problem introduced in the latest versions of the circular buffer that it can not correctly work with a custom memory allocator. The patch is provided here: https://svn.boost.org/trac/boost/ticket/9334 The former maintainer suggested to submit a request to this list, so that the patch is included in the daily build and the next release. Thanks! Serge

2 1

[COUNTERTREE + SUBALLOCATORS] Errors corrected, .New Lock system, manycore strategies
by Francisco José Tapia 02 Dec '13

02 Dec '13

I have corrected several errors ( thanks to the people who sent me comment, suggestions and bugs). The lock mechanism ( 1 Writer / N Readers) have been redesigned in order to correct previous errors and increment the speed. The actual version is built over spinlocks and yield functions. It provide an alternative to the upgrade mutex. You have a detailed description with diagrams and examples in https://dl.dropboxusercontent.com/u/8437476/works/countertree_2.0/doc/singl… *LIBRARY DESCRIPTION* This library provide a concurrent and thread safe implementation of the *tree based data structures* (set, multiset, map and multimap, plus a unordered tree named vector_tree) with *random access iterators* and *access by position like a vector*. This permit to *distribute the elements* stored in the trees, between an *arbitrary number of threads*, identically as do with the vectors. Over it you can use many algorithms designed for vectors ( as quicksort over an unsorted tree) and *making easy the design of parallel algorithms* applied to the tree based data structures , and their use by the multicore development tools.. [image: Imágenes integradas 1] These data structures are based on a kind of augmented red-black trees, where each node have a counter with with the number of nodes under which permit the access by position, like in a vector, to the elements stored in the tree, and random access iterators. I named this tree of counters *countertree* Until now, in many practical problems, the binary trees was not used , by the difficult for to distribute the elements stored between an arbitrary number of cores, and the difficult for to develop parallel algorithms. This limitation force to use only 1 thread with these data structures. And with big problems, usually it is not a good solution. With the countertrees, perhaps it would be interested reevaluate some algorithms, and make an comparison between the present algorithms and the possible options, in order to see the performance, the memory used and the flexibility. If you are interested, you have a brief document ( 2 pages) about the manycore strategies<https://dl.dropboxusercontent.com/u/8437476/works/doc/Manycore_Strategies.p…>with this library, and other brief project description<https://dl.dropboxusercontent.com/u/8437476/works/doc/Brief_project_descrip…>(2 pages) where provide a global vision of the project and their parts. I think is a good starting point in order to examine the library. *You can find the code and the documentation in my web pages in dropbox* *https://dl.dropboxusercontent.com/u/8437476/works/countertree_2.0/index.html <https://dl.dropboxusercontent.com/u/8437476/works/countertree_2.0/index.html>* *or if you prefer in a git format* *https://github.com/fjtapia/countertree_2.0 <https://github.com/fjtapia/countertree_2.0>* Please, if you have any idea , any comment or see any fail, any lack, please say me in order to improve the library, and provide between all ,a fast, robust and reliable tool to the C++ programmers. If you want more information, need something, please, say me, and I will try to do. Thanks by your interest. Yours Francisco Jose Tapia e-mail : fjtapia(a)gmail.com

1 0

Subversion repository closed for all commits on all branches
by Beman Dawes 02 Dec '13

02 Dec '13

The Subversion repository is now closed for all commits on all branches. An attempt to commit will fail a pre-commit hook, resulting in the following error message: Command: Commit Modified: C:\boost\trunk\libs\system\doc\index.html Sending content: C:\boost\trunk\libs\system\doc\index.html Error: Commit failed (details follow): Error: Commit blocked by pre-commit hook (exit code 1) with output: Error: This Subversion repository is no longer in active use. Error: Error: It has been superseded by a Git super-project repository Error: and individual Git repositories for each Boost library. Error: Error: See: https://github.com/boostorg Completed!: The next step in the conversion to Git and Modular Boost is to run the conversion script one last time, and then turn it off. We will let you know when that is completed. -- The Release Managers

3 3

[git-help][eclipse] Fetching the full repo?
by Rene Rivera 02 Dec '13

02 Dec '13

First, I'm asking about using git from within Eclipse since that's where I do everything.. I've had a Boost master clone for a long time now. And having a very small amount of time I decided to start updating and looking at the latest state of the repo. Unfortunately everything I attempt to get my local checkout to match the head state of the repo is failing. In particular the subrepos are not being fetched or refreshed. And some of the subrepos are missing and hence show up as pending delete changes. Does anyone know how to get the Eclipse git to fetch/reset to the head fully? Rene. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

1 1

[boost.random] Dependencies/modularization
by Philip Bennefall 01 Dec '13

01 Dec '13

Hi all, I know that I have brought up this subject before and that work is being done to improve the situation, but I just wanted to ask about a specific case that I came across today while attempting to extract a subset of Boost. I want to use mersenne_twister.hpp, uniform_int_distribution.hpp and uniform_real_distribution.hpp from boost.random as part of an open source library that I am developing. Since the only part of Boost that I am using in that library is the Mersenne Twister prng, I figured I would ship the relevant headers along with my own source distribution. I used bcp to scan my code which includes these three headers, and I get a directory which is 2.89 MB in size and which contains 304 files. I looked at what is being included, and in order of size the worst offenders are as follows: preprocessor - 1.82 MB type_traits - 604 KB config - 250 KB The other libraries that are included are tiny, and I would not consider config to be a problem either. Clearly, preprocessor is the worst offender by far here in terms of bloat. I wonder if there is an easy way to get rid of the dependency on that library without hacking Boost too much? As for type_traits, it seems a bit large for what I gather it is being used for in this case but is not the end of the world either. Does anyone have any suggestions? Will the modularization of Boost reduce these dependencies in the not too distant future? I know that a huge effort is being spent moving Boost to Git, but I am curious to know whether there is a roughly estimated timeline for the modularization work? Kind regards, Philip Bennefall

1 0

[type_traits] Why is there no total extent?
by Mostafa 01 Dec '13

01 Dec '13

I was wondering why there is no total_extent in the TypeTraits library. total_extent would represent the total number of elements in a complete built-in array type, else it would be zero. I would think that this would be a natural supplement to the existing extent metafunction. (There is a very similar functionality in the smart pointers library, under the name of array_total here: smart_ptr/detail/array_traits.hpp) Mostafa

1 0

ZeroMQ integration with Boost-v1.54
by Rahul Mathur 01 Dec '13

01 Dec '13

All, Looking to have ZeroMQ integration with Boost-v1.54. I am familiar with Boost.ASIO client and Server model. BTW, How do I proceed to have ZeroMQ integrated with Boost-v1.54 with GCC on Linux platform?

1 0

[conversion] Isolating the phantom file changes problem
by Beman Dawes 01 Dec '13

01 Dec '13

This is the simplest case I could come up with where git clone produced a initially modified state. Any ideas why this is happening? Is this another manifestation of crlf problems? --Beman D:\modular-boost\libs\intrusive>git clone --recursive git@github.com:boostorg/boost.git modular-boost ... much output, no apparent error messages... D:\modular-boost>git status # On branch master # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # (commit or discard the untracked or modified content in submodules) # # modified: libs/interprocess (modified content) # modified: libs/intrusive (modified content) # modified: libs/pool (modified content) # no changes added to commit (use "git add" and/or "git commit -a") D:\modular-boost>cd libs/pool D:\modular-boost\libs\pool>git status # Not currently on any branch. # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: doc/images/mb1.svg # modified: doc/images/mb2.svg # modified: doc/images/mb3.svg # modified: doc/images/mb4.svg # modified: doc/images/pc1.svg # modified: doc/images/pc2.svg # modified: doc/images/pc3.svg # modified: doc/images/pc4.svg # modified: doc/images/pc5.svg # no changes added to commit (use "git add" and/or "git commit -a") D:\modular-boost\libs\pool>cd ..\interprocess D:\modular-boost\libs\interprocess>git status # Not currently on any branch. # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: proj/vc7ide/managed_shared_memory.vcproj # modified: proj/vc7ide/offset_ptr_test.vcproj # no changes added to commit (use "git add" and/or "git commit -a") D:\modular-boost\libs\interprocess>cd ..\intrusive D:\modular-boost\libs\intrusive>git status # Not currently on any branch. # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: proj/vc7ide/avl_multiset/avl_multiset.vcproj # modified: proj/vc7ide/avl_set/avl_set.vcproj # modified: proj/vc7ide/sg_multiset/sg_multiset.vcproj # modified: proj/vc7ide/sg_set/sg_set.vcproj # modified: proj/vc7ide/splay_multiset/splay_multiset.vcproj # modified: proj/vc7ide/splay_set/splay_set.vcproj # no changes added to commit (use "git add" and/or "git commit -a")

7 25

An open typeswitch using lambdas
by Sumant Tambe 30 Nov '13

30 Nov '13

Hi, I would like to get feedback on a small typeswitch library I've been working on for some time now. The library is designed to dispatch code (lambdas) based on the actual value of boost::any, boost::variant, and also general polymorphic hierarchies. An example is in order. template <class Poly> void test_poly(Poly& p) { match(p)( [](int i) { std::cout << "int = " << i << "\n"; }, [](double d) { std::cout << "double = " << d << "\n"; }, [](const std::string &s) { std::cout << "string = " << s << "\n"; }, [](std::ostream &o) { std::cout << "found ostream" << "\n"; } ); } int main(void) { std::ios_base &stream = std::cout; boost::any any(std::string("C++ Truths")); boost::variant<int, std::string> var("boost"); double d = 9.99; test_poly(stream); // prints found stream test_poly(any); // prints string = C++ Truths test_poly(d); // prints double = 9.99 test_poly(var) // prints string = boost } The implementation of the library is a little over 250 lines. Check it out here: http://coliru.stacked-crooked.com/a/72597a93b12916d4. clang is the only compiler I've been able to compile it with. It resembles Scala's match statement. Scala's match is way more powerful than what I've been able to achieve with C++ library emulation. It is also quite similar to Stroustrup's "Open and Efficient Typeswitch for C++" ( http://www.stroustrup.com/OOPSLA-typeswitch-draft.pdf) A quick benchmark shows that lambda-based typeswitch is about 4 to 5 times *slower*. If there is sufficient interest, I would be thrilled to contribute this library to boost. I believe it can be further generalized to support n-ary method dispatching. Thoughts? R/ Sumant

4 7

[git] Line endings in bootstrap.bat on Windows
by Björn Pollex 29 Nov '13

29 Nov '13

I just cloned the modularized Boost repository from Github [1]. Right after the clone is done, git status gives me a complete diff on bootstrap.bat (so probably line endings). I do have autocrlf = true in my system configuration, so this shouldn't be the problem, right? Is anyone else seeing this? Am I doing something wrong? If so, how to do it correctly? Regards, Björn Pollex [1] https://github.com/boostorg/boost

16 41

Is there a thin array wrapper/proxy lying around somewhere?
by Mostafa 29 Nov '13

29 Nov '13

(Yes, I'm aware of boost.array, boost.multiarray, and std::vector.) Is there any thin but complete array wrapper/proxy lying around somewhere in boost? A class that if substituted for an array will behave just like the substituted array? Thanks, Mostafa

7 10

Re: [boost] [conversion] Enforcing tabs to spaces conversions and other git goodies.
by Cox, Michael 28 Nov '13

28 Nov '13

Michael On Thu, Nov 28, 2013 at 8:06 AM, Beman Dawes <bdawes(a)acm.org> wrote: > > On Thu, Nov 28, 2013 at 5:00 AM, Mateusz Loskot <mateusz(a)loskot.net> wrote: > > > On 28 November 2013 08:49, Cox, Michael <mhcox(a)bluezoosoftware.com> wrote: > > > In addition to re-normalizing the line endings, we could also start > > > enforcing coding standards, e.g. tabs converted to spaces standard via > > > gitconfig/gitattribute filters. Git allows you to define filters in your > > > .git/config or ~/.gitconfig file and specifying their use in > > > .gitattributes, e.g. in .gitconfig: > > > > > > # Convert tabs to 4 spaces (uses Linux expand/unexpand commands, so not > > > cross-platform) > > > [filter "tabspace"] > > > smudge = unexpand --tabs=4 --first-only > > > clean = expand --tabs=4 --initial > > > [...] > > > > ...automatically behind the scene? Scary! > > > > IMHO, this belongs to commit hooks. > > > > Qt's sanitize-commit may be a good example > > > > https://qt.gitorious.org/qt/qtrepotools/source/b69da7d675774be14027808328ea… > > > > Michael and Mateusz, > > Yes - sanitizing and commit hooks are important topics. But the way to > handle them is to start a new thread so that they don't get lost in the > line-ending bicycle shed discussion. > > Thanks, > > --Beman Mateusz, I agree hooks have to be used for the "golden" boostorg repositories since folks may forget to configure their local/public repositories with the appropriate hooks/filters, but if Boost goes fully distributed like Linux, there may be a lot of integration repositories a change flows through on it's way to boostorg and it's probably best to get the code normalized as soon as possible. Michael

1 0

More flexible any_cast for boost::any
by DeadMG 28 Nov '13

28 Nov '13

Hello, I've been looking at ABIs and such (various unpleasant reasons). But I recently created the following code: #include <iostream> struct Base { virtual void check() = 0; template<typename T> T* IsDerivedFrom() { try { check(); } catch(T* p) { return p; } catch(...) { return nullptr; } return nullptr; } }; template<typename T> struct Derived : public Base { Derived(T obj) : t(obj) {} T t; void check() override final { throw &t; } }; struct A { virtual ~A() {} virtual void print() = 0;}; struct B : public A { int x; B(int y) : x(y) {} void print() override final { std::cout << x; } }; int main() { Base* b = new Derived(B(5)); A* p = b->IsDerivedFrom<A>(); p->print(); } Whilst this is hardly the cleanest piece of code I've ever written, it also provides a base for implementing a more generic any_cast<ValueType>, which could succeed if ValueType is a base class of the stored type. Amazingly, the Standard requires the code to work but does not provide a cleaner means of implementation. I also note that, for some configurations, you could fall back to the Itanium ABI provided function directly, which would presumably be substantially faster and cleaner. Enabling this variety of any_cast would substantially improve the composability of boost::any. For example, it's arguable that std::function is merely boost::any but with additional interface requirements. With such an any_cast enhancement, it would be quite trivial to compose std::function implementations or similar concepts on top of boost::any.

5 7

Re: [boost] [conversion] Isolating the phantom file changes problem
by Cox, Michael 28 Nov '13

28 Nov '13

In addition to re-normalizing the line endings, we could also start enforcing coding standards, e.g. tabs converted to spaces standard via gitconfig/gitattribute filters. Git allows you to define filters in your .git/config or ~/.gitconfig file and specifying their use in .gitattributes, e.g. in .gitconfig: # Convert tabs to 4 spaces (uses Linux expand/unexpand commands, so not cross-platform) [filter "tabspace"] smudge = unexpand --tabs=4 --first-only clean = expand --tabs=4 --initial Then in .gitattributes: # Code formats *.c text filter=tabspace *.cpp text filter=tabspace *.h text filter=tabspace *.hpp text filter=tabspace *.ipp text filter=tabspace *.tpp text filter=tabspace On a related topic, what is the svneol .gitattribute being used in the .gitattributes file do? I couldn't find it documented (I discovered the filter attribute while searching for the svneol attribute). Also, the mime type specified in a # comment following some attribute rule specification doesn't seem to be a supported syntax, i.e. the '#' has to be in the first column. Michael On Wed, Nov 27, 2013 at 3:02 PM, Gavin Lambert <gavinl(a)compacsort.com>wrote: > On 28/11/2013 05:17, Quoth Dave Abrahams: > > Another possibility might be to explicitly mark all text files in >>> .gitattributes with eol=lf and then run the conversion; I think that >>> would fix the repository blobs, >>> >> >> What goes into .gitattributes has no effect on the content of blobs in >> the repository. >> > > Sorry, when I wrote that I was envisaging the conversion process doing the > equivalent of an SVN checkout and then git add/commit. (And git commit > does take the attributes into account for eol conversion.) > > Since apparently it doesn't work like that, just ignore that suggestion. > > I still think that we need to renormalise the line endings though. Whether > that's done as a reconversion (fixing history) or just as an extra commit > (fixing current heads), that's up to you guys. ;) > > > > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/ > mailman/listinfo.cgi/boost >

3 2

[conversion] Verification check results: svn trunk vs git develop
by Beman Dawes 28 Nov '13

28 Nov '13

* There is an entire library, Boost.Compose, long since deprecated and removed from svn in favor of Boost.Bind or Boost.Lambda, present in the git repos, both in master and develop. * Boost.Interprocess, git develop contains a header libs\include\boost\interprocess\fully_mapped_file.hpp that does not appear in the svn trunk head. * Boost.Type-Traits, git develop contains a header directory, \include\boost\detail, with two header files. Neither these two headers nor the directory are present in svn trunk head. * All 9974 headers in svn trunk/boost head have git super-project boost header entries generated by "b2 headers" and the content, ignoring end of line differences, is identical in all of them. * Exactly the same 5680 regression tests passed for both svn trunk head and git develop head. It doesn't get any better than that! --Beman

2 2

[exception][range] boost/range/size_type.hpp + unexpected dependenciies Exeception -> Units -> Algorithms -> Range -> Concepts
by Vicente J. Botet Escriba 28 Nov '13

28 Nov '13

Hi, The regression test signal this error Test output: MinGW-w64-4.5 jc-bell.com - thread - async__async_p / gcc-mingw-4.5.4 Rev 85699 / Mon, 16 Sep 2013 13:58:07 +0000 Compile [2013-09-16 17:53:55 UTC]:fail "g++" -ftemplate-depth-128 -O0 -fno-inline -Wall -pedantic -g -mthreads -Wextra -Wno-long-long -Wno-variadic-macros -Wunused-function -pedantic -DBOOST_ALL_NO_LIB=1 -DBOOST_CHRONO_DYN_LINK=1 -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_SYSTEM_NO_DEPRECATED -DBOOST_THREAD_BUILD_DLL=1 -DBOOST_THREAD_THROW_IF_PRECONDITION_NOT_SATISFIED -DBOOST_THREAD_USE_DLL=1 -I".." -c -o "F:\boost\GCC\trunk\results\boost\bin.v2\libs\thread\test\async__async_p.test\gcc-mingw-4.5.4\debug\threading-multi\sync\futures\async\async_pass.o" "..\libs\thread\test\sync\futures\async\async_pass.cpp" In file included from ../boost/range/size.hpp:21:0, from ../boost/range/functions.hpp:20, from ../boost/range/iterator_range_core.hpp:28, from ../boost/range/iterator_range.hpp:13, from ../boost/algorithm/string/replace.hpp:16, from ../boost/units/detail/utility.hpp:25, from ../boost/exception/detail/type_info.hpp:19, from ../boost/exception/detail/object_hex_dump.hpp:15, from ../boost/exception/to_string_stub.hpp:16, from ../boost/exception/info.hpp:16, from ../boost/exception/detail/exception_ptr.hpp:20, from ../boost/exception_ptr.hpp:9, from ../boost/thread/future.hpp:28, from ..\libs\thread\test\sync\futures\async\async_pass.cpp:29: ../boost/range/size_type.hpp:80:5: error: expected ';' before '}' token ../boost/range/size_type.hpp:80:5: error: expected ';' before '}' token ../boost/range/size_type.hpp:87:5: error: expected ';' before '}' token ../boost/range/size_type.hpp:87:5: error: expected ';' before '}' token BOOST_RANGE_CONCEPT_ASSERT((boost::SinglePassRangeConcept<T>)) This is surely due to a changeset on Boost.Range (85690?). Maybe an inclusion to Concepts is missing. Could the maintainer take a look? What is more surprising is the chain of dependencies the inclusion of boost/exception_ptr.hpp conveys. Exeception -> Units -> Algorithms -> Range -> Concepts. Is there a way to break these dependencies? Best, Vicente

4 8

Git conversion fixes
by Dave Abrahams 28 Nov '13

28 Nov '13

We have two issues currently extant: 1. Some files that were deleted in SVN history are still present in the Git HEAD 2. Some people are dissatisfied with the way line endings are handled, especially on Windows I didn't expect to spend my Thanksgiving vacation working on this stuff, but I am getting myself set up to diagnose and fix #1. I am not going to try to fix #2, mostly because it's too open-ended, and there isn't even a consensus in the community about what a fix should look like. If a consensus is formed around a desired outcome, I am willing to at _least_ help in an advisory capacity, in which case someone should send me a personal email. Thanks, Dave

5 5

[build] clang-win help needed
by Edward Diener 28 Nov '13

28 Nov '13

The clang-win.jam file, which was provided by 'tr1gun' as an attachment to another thread in Boost Build, inherits its generators, flags, and rules from msvc.jam. The lines in clang-win.jam are: toolset.inherit-generators clang-win <toolset>clang <toolset-clang:platform>win : msvc ; toolset.inherit-flags clang-win : msvc : <debug-symbols>on/<debug-store>object : YLOPTION ; toolset.inherit-rules clang-win : msvc ; In order to eliminate the VC++ /EH(x) option, which clang using VC++ RTL does not use, I added into the file a rule: rule compile.c++ ( targets * : sources * : properties * ) { C++FLAGS on $(targets) = [ set.difference [ on $(targets[1]) return $(C++FLAGS) ] : /EHs ] ; } suggested by Steve Watanabe. This effectively eliminates the /EHs option when compiling with clang. However when a 'run' action is done, with clang as the compiler, the compile step is never called. If I remove the 'rule compile.c++' from the clang-win.jam file the compile step is called before the link and execute steps of the 'run' action, but of course the compile step then issues the /EHs warning which the insertion of the above rule eliminated. Does anybody know why adding the above rule causes the 'run' action to not compile the appropriate fle before attempting the link and execute ?

1 0

Peer Review Report for proposed Boost.TypeIndex v2.1 Nov 12th – 21st 2013
by Niall Douglas 27 Nov '13

27 Nov '13

Please let me know as soon as possible any errata, missing credits etc. Niall Boost Peer Review Report for proposed Boost.TypeIndex v2.1 Nov 12th – 21st 2013 This report is the first edition, dated Sunday 24th November 2013. The review manager was Niall Douglas http://www.nedprod.com/. Source: https://github.com/apolukhin/type_index/zipball/master Documentation: http://apolukhin.github.com/type_index/index.html Peer review discussion detail: http://boost.2283326.n4.nabble.com/TypeIndex-Peer-review-period-for-library… My thanks to the Boost members whose peer review makes up this report: Robert Ramey, Vicente J. Botet Escriba, Gavin Lambert, Andrey Semashev, Steven Watanabe, pfultz2, Mathieu Champlon, Joël Lamotte Klaim, Rob Stewart, Jan Herrmann, Tony Van Eerd. Contents: · Summary of consensus from peer review ......................................................................................................... 1 · My recommendation to the library author and the Review Wizards ................................................................ 3 Summary of consensus from peer review: The consensus feedback was to accept TypeIndex after substantial modifications. There were two recommendations of rejection due to how substantial such modifications would need to be (i.e. a request for a second round of peer review with a new implementation). Note that my personal opinion based on post-review reflection is written in [square bracketed italics]. · Many seemed to feel that a boost::type_info’s member function API, where identically named to that of std::type_info member function API, ought to have identical compile-time effects. This implied that missing member function APIs, or other compile time errors for missing or incomplete functionality, would be okay but if name() returns some const char *, then any const char * so long as it meets the C++ standard is okay. [I think there are three use cases for a type_info like substitute: (i) as a lightest possible weight, non-RTTI requiring minimal type_info which can have any API it likes and ought to not be directly substitutable for std::type_info or std::type_index (ii) as a compile-time substitute for std::type_info in that it will compile without third party code modification, but may not produce reliable code due to not returning exactly the same values as std::type_info (iii) as a runtime substitute for std::type_info in that it will require code to be “ported” to it due to having a breaking API, but thereafter produces reliable code. I’ll be very blunt in saying that (ii) is a bad idea in my opinion, and (iii) is valuable but out of scope enhancement which could be added as a separate class after peer review. In my opinion, (i) is where we ought to focus, and I would recommend that the lightest possible weight type_info replacement be deliberately compile-time incompatible with std::type_info (where output is not identical to std::type_info) to force porting code to it so authors are not lazy.] · A large minority seemed to feel that a boost::type_info’s member function API, where identically named to that of std::type_info member function API, ought to have identical run-time outcomes. Most specifically, this would mean that member functions e.g. name() would return exactly what std::type_info’s name() does, even if for example name() returns a std::string instead of a const char * as would be necessary in pre-C++11 compilers. [This is really use case (iii) in the previous item.] · It was mentioned that it should be possible to optionally specialise std::hash<> for type_info for optional seamless use in hash taking containers. · Some felt that implementation-specific std::type_info quirks ought to be replicated. Others felt they should not, and a portable interface which works identically on all platforms is preferred. [This is really use case (iii) in the previous item.] · boost::type_info is currently initialised via a static cast from a std::type_info when RTTI is available. This is undefined behaviour, and some felt this to be a showstopper. I (Niall Douglas) looked into this more deeply due to its seriousness, and found that because most STL implementations define std::type_info with a virtual function table, the undefined behaviour static cast would cause dynamic_cast on a boost::type_info instance to misoperate. [I believe the RTTI induced misoperation to indeed be a showstopper, and that this use of undefined behaviour to reduce code bloat is an unsafe optimisation. A much lighter weight non-direct-substitute for std::type_info ought to be as code bloat parsimonious as is possible, while its lack of non-explicit interoperation ability with std::type_info ought to allow avoidance of needing any UB tricks.] · Some felt that any use of implied boost::type_info ought to be explicitly written as boost::type_info instead of relying on namespace lookup, as the name similarity to std::type_info may introduce confusion. [I agree] · It was mentioned that some function-local static data members are initialised in a thread unsafe way. [For information I have to hand a very lightweight BOOST_BEGIN_MEMORY_TRANSACTION() implementation ideal for this purpose. We could submit it to Boost.Detail and then everyone could use it?] · Magic macros such as __PRETTY_FUNCTION__ ought to not be referenced outside of a function as they don’t technically exist there. Checks for their existence ought to be within a function. · It was requested that a boost::type_id<> which takes some unknown variable instance as a parameter and therefore allows the compiler to deduce the type of the variable as the boost::type_index<T> type would be valuable. · A mechanism for programming compile-time logic with class inheritance trees such that inheritance can be determined at compile-time with RTTI disabled was requested. My recommendation to the library author and the Review Wizards: · In my opinion Antony ought to make TypeIndex v3 quite literally a very lightweight container of some unknown, but known to be uniquely identifying for some type, static const char * string. I think its class type and its list of member functions ought to be deliberately compile-time incompatible with std::type_info to force authors to upgrade their code. A conversion member function ought to be able to synthesise a corresponding std::type_info using typeid() from some boost::type_index<T>, but that’s about it. I would even, personally speaking, go so far as to only provide a boost::type_index and no corresponding boost::type_info, especially if the boost::type_id<T>() function can return a const boost::type_index<T>& and therefore can be used as a static const lref, or copy constructed from it etc. A suggested name() member function replacement which correctly breaks out the multiple confounding uses of std::type_info::name() into each of their three use cases (and which intentionally causes any use of name() to fail to compile) might be: Text Box: /*! Returns a static const char string of unknown format uniquelyidentifying this type.The only guarantee is that this string will beunique to the type within this process lifetime. */const char *unique_name() const noexcept;/*! Returns a representation of this type suitable for printing.This call may take some time as its storage may not be cached. */std::string pretty_name() const;class enum mangling{Native, //!< Whatever the native mangling used by this toolset isMSVC, //!< The Microsoft C++ mangling formatItanium //!< The Itanium C++ mangling format};/*! Returns the mangled form of the string representation of the type.After the calculation the value is cached statically such that the c_str()function can be used to convert the returned string to a const char *format identical to what may be returned by std::type_info::name() (orraw_name() on MSVC).This function may throw an exception if it does notsupport mangled type string calculation, including when mangling=Native onsome Bear in mind that user code can always subclass boost::type_index and add their own name() implementation based on one or more of the above new member functions. · In other words, here I think “less is more” in every way you look at it. I think a slimmer less heavy TypeIndex would be a superior solution. · I request the Review Wizards to allow Antony some time to make the changes to produce a v3 of the library, and then to allow TypeIndex v3 a Fast Track Review of five days to ensure the Boost community is happy and that its feedback has been incorporated. It was asked during peer review that such a five day period please include a weekend. I would be happy to serve as review manager again if requested. Niall Douglas Waterloo, Canada, November 2013

6 26

[conversion] Verification check results: svn branches/release vs git master
by Beman Dawes 27 Nov '13

27 Nov '13

* As reported previously, the follow extra header files are present in the git repos: > boost\functional\hash\Attic\deque.hpp > boost\functional\hash\Attic\list.hpp > boost\functional\hash\Attic\map.hpp > boost\functional\hash\Attic\pair.hpp > boost\functional\hash\Attic\set.hpp > boost\functional\hash\Attic\vector.hpp > boost\property_tree\detail\exceptions_implementation.hpp > boost\property_tree\detail\path_implementation.hpp > boost\property_tree\detail\pugxml.hpp > boost\property_tree\detail\translator_implementation.hpp > boost\property_tree\detail\xml_parser_read_pugixml.hpp > boost\property_tree\detail\xml_parser_read_pugxml.hpp > boost\property_tree\detail\xml_parser_read_spirit.hpp > boost\property_tree\detail\xml_parser_read_tinyxml.hpp * There were no missing header files in master. * Except for line endings and svn $Id$, $Revision$, and $Date$, there were no differences in content between header files in svn branches/release and git master. * Regression tests were run on both svn branches/release and git master. 5447 tests passed on each, however each had one test that passed on it but failed on the other. See the following two items for details. * Boost.Thread test_thread_lib passed on svn branches/release (and in the public regression tests) but failed on svn master. The message was: ====== BEGIN OUTPUT ====== Running 8 test cases... d:/modular-boost/libs/thread/test/./util.inl(160): fatal error in "test_creation_through_reference_wrapper": Timed test didn't complete in time, possible deadlock. *** 1 failure detected in test suite "Master Test Suite" EXIT STATUS: 201 ====== END OUTPUT ====== Windows decided to go to sleep in the middle of the run, and that may account for this error. * Boost.Thread ex_executor_lib passed in git master, but failed in svn branches/release. The message was: ====== BEGIN OUTPUT ====== 1178 ..\libs\thread\test\..\example\executor.cpp[ 58] int __cdecl main(void) 940 6776 ..\libs\thread\test\..\example\executor.cpp..\libs\thread\test\..\example\executor.cpp[[ 2126] ] void __cdecl p1(void)void __cdecl p2(void) 940 d5c1a78 ..\libs\thread\test\..\example\executor.cpp..\libs\thread\test\..\example\executor.cpp[[ 2121] ] void __cdecl p1(void)void __cdecl p1(void) d5c 1a78 ..\libs\thread\test\..\example\executor.cpp..\libs\thread\test\..\example\executor.cpp[[ 2621] ] void __cdecl p2(void)void __cdecl p1(void) ..\libs\thread\test\..\example\executor.cppd5c [ 1a..\libs\thread\test\..\example\executor.cpp] [void __cdecl p2(void)26 ] void __cdecl p2(void) 940 d5c ..\libs\thread\test\..\example\executor.cpp..\libs\thread\test\..\example\executor.cpp[[ 2126] ] void __cdecl p1(void)void __cdecl p2(void) d5c 940 ..\libs\thread\test\..\example\executor.cpp..\libs\thread\test\..\example\executor.cpp[[ 3131] ] int __cdecl f1(void)int __cdecl f1(void) Assertion failed: 0 && "Boost::Chrono - Internal Error", file C:\boost\svn-release-final\boost/chrono/detail/inlined/win/chrono.hpp, line 44 1178 ..\libs\thread\test\..\example\executor.cpp[ 67] int __cdecl main(void) t1= 1 EXIT STATUS: 3 ====== END OUTPUT ====== I have no idea why it would pass for testers but not for me, but am much less worried about a failure in svn branches/release than git master. --Beman

3 5

[conversion] Serious header integrity test failures.
by Beman Dawes 27 Nov '13

27 Nov '13

This integrity test verifies that every header file present in svn branches/release and trunk is also present in git master and develop, respectively, and visa versa. The branches/release vs master comparison is in pretty good shape - no missing headers, but a small number of extra headers. Two libraries are affected. But the trunk vs develop comparison turned up problems in many libraries. For example, the whole Boost.Chrono stopwatches sub-directory is missing. These look serious. What is the fix? --Beman

4 12

Code to address requirement 7(a) of IOStreams Roadmap
by Gene Panov 26 Nov '13

26 Nov '13

Colleagues, I posted this before, but didn't get answers to some questions so far. I think I addressed the "output" part of requirement 7(a) from the IOStreams Roadmap: https://svn.boost.org/trac/boost/wiki/IostreamsRoadmap in this library: https://code.google.com/p/async-ostream/ Does anyone mind if I create a patch for Boost.IOStreams to add those five files and ask the maintainer (or volunteers) for feedback? Regards, Gene

5 14

[type_erasure]
by Andrzej Krzemienski 26 Nov '13

26 Nov '13

Hi, I am trying to use Boost.TypeErasure library with a 'concept' that provides contextual conversion to *bool*. That is, I want to type-erase types that provide the following operations for some invented object *o*: * if (o) {}* * if (!o) {}* * bool (o); * I cannot find a predefined concept for that, nor can I use BOOST_TYPE_ERASURE_MEMBER or BOOST_TYPE_ERASURE_FREE, because that will not work for built in types. Is there any convenience tool that enables specifying such concept? Regards, &rzej

2 2

{git]
by Richard Dale 25 Nov '13

25 Nov '13

Probably the problem is between the keyboard and chair, but ... what's up? On which end is permission denied? rsd/myroot> git clone git@github.com:boostorg/boost.git modular-boost Cloning into 'modular-boost'... Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. users/rsd> git --version git version 1.7.12.4 ??

3 3

New Version (0.4.2) of proposed Boost.Application library is available.
by Renato Forti 25 Nov '13

25 Nov '13

Documentation: <http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/index.html> http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/index.html Code: https://github.com/retf/Boost.Application News in this release: * Now aspect_map class is Thread Safe. * Now aspect_map interface use names are more in line with the STL (e.g.: insert, find and so on) The documentation of aspect_map: <http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/boost/applic ation/aspect_map.html> http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/boost/applica tion/aspect_map.html * Some fixes on code and docs. Please send your comments!

1 0

Re: [boost] Boost Digest, Vol 4191, Issue 4
by Cox, Michael 25 Nov '13

25 Nov '13

On Sun, Nov 24, 2013 at 3:57 PM, <boost-request(a)lists.boost.org> wrote: > Send Boost mailing list submissions to > boost(a)lists.boost.org > > Date: Sun, 24 Nov 2013 23:20:43 +0100 > From: Bj?rn Pollex <bjoern.pollex(a)googlemail.com> > To: boost(a)lists.boost.org > Subject: [boost] [git] Line endings in bootstrap.bat on Windows > > I just cloned the modularized Boost repository from Github [1]. Right after > the clone is done, git status gives me a complete diff on bootstrap.bat (so > probably line endings). > > I do have autocrlf = true in my system configuration, so this shouldn't be > the problem, right? Is anyone else seeing this? Am I doing something wrong? > If so, how to do it correctly? > > Regards, > > Bj?rn Pollex > > [1] https://github.com/boostorg/boost > > I think "they" are working on it. See the following links: http://lists.boost.org/Archives/boost/2013/10/208067.php http://lists.boost.org/Archives/boost/2013/11/208141.php

2 1

[TypeIndex] Peer review period for library acceptance begins, ending Thurs 21st Nov
by Niall Douglas 25 Nov '13

25 Nov '13

Boost community feedback is requested for the formal peer review of the TypeIndex library by Antony Polukhin. Feedback requested includes: 1. Should this library be accepted into Boost? 2. Any conditions which should be attached to acceptance into Boost e.g. fixes, additional testing, changes to documentation. Please be as specific as possible here (bullet points are good!) Peer review ends on Thursday 21st Nov, ten days from today. Based on your feedback, at that point I will decide if I recommend TypeIndex for inclusion in my report to the review wizards. Comments can be posted to boost(a)lists.boost.org if you expect others to comment on your post, or to me privately if you wish your comment to not be made public. What is Boost.TypeIndex? TypeIndex performs three main functions: 1. It provides a consistent, well defined, portable boost::typeid() implementation with a consistent, well defined, portable boost::type_info class implementation which mirrors std::type_info. Implementation-specific weirdnesses (e.g. std::type_info::raw_name(), the fact the hash_code is often terrible and collides frequently) are abstracted out into a single, portable API. 2. It provides the ability to convert a type into a uniquely identifiable, container indexable, boost::type_info instance (e.g. &typeid(T) or C++11 class std::type_index) with RTTI disabled, thereby removing the need for requiring RTTI enabled for many type_info use cases. Any features which require RTTI are very clearly denominated in the API's name. 3. It allows the following Boost libraries to eliminate their dependency on RTTI which is a big win for embedded systems use, and it supplies patches for these libraries replacing RTTI std::type_info with boost::type_info. Feedback from the maintainers and users of these Boost libraries is *particularly* welcomed: Any, Graph, Property Map, Property Tree, Test, Variant, Xpressive I believe that TypeIndex meets the Boost library requirements at http://www.boost.org/development/requirements.html, and I have personally verified that it builds and passes all unit tests on GCC 4.6, clang 3.0 and MSVCs 10-12 [1]. I should add that Antony has already done three rounds of changes according to my feedback, and my thanks to him for being so dilligent and responsive. NOTE: Please read the TypeIndex documentation (linked to below) before asking any questions e.g. about potential code bloat etc. You'll probably find the answer already there. Source code: https://github.com/apolukhin/type_index/zipball/master Github: https://github.com/apolukhin/type_index Documentation: http://apolukhin.github.com/type_index/index.html Any questions about topics not in the documentation? Please do ask. [1]: A single unit test currently always is reported as failing to link correctly on MSVC. Antony believes this to be a bug in Windows bjam, as the Jamfile marks the link as expected to fail using link-fail but bjam does not respect this on Windows in this one use case scenario (yet weirdly the other expected link failures work fine!). Niall -- Currently unemployed and looking for work. Work Portfolio: http://careers.stackoverflow.com/nialldouglas/

12 85

PDB files missing from Windows binaries
by Fredrik Orderud 24 Nov '13

24 Nov '13

First, I want to give a big thank for the streamlined availability of precompiled Windows binaries. The "Windows binaries" link from the Boost download webpage significantly lowers the barriers for Boost usage on the Windows platform. That said, there seem to be an issue with missing PDB files from the most recent Boost 1.55 binaries. This makes it difficult to debug applications, since debug information is missing. I suspect that the reason for the missing PDBs is that the build script doesn't install them to the target folder, which have previously been reported on [1]. Unfortunately, there has been little response to this problem. Would if be possible for someone to look into this problem, and improve the build script? [1] http://lists.boost.org/boost-build/2013/08/26894.php Thanks in advance, Fredrik

5 5

[build] File / path lengths difficult to manage on Windows
by Ben Craig 24 Nov '13

24 Nov '13

I was unzipping boost 1.55 on my Windows machine, into what I thought was a reasonable location. 7-zip eventually complained about a file that it could not write because the path was too long. Most APIs on Windows restrict paths to ~260 characters. The longest file in the boost 1.55 release is the following: boost_1_55_0\libs\geometry\doc\html\geometry\reference\spatial_indexes\boost__geometry__index__rtree\rtree_parameters_type_const____indexable_getter_const____value_equal_const____allocator_type_const___.html This is 207 characters long. Next on the list are a whole bunch of html and png documentation files, all with length 174. Here is one example: boost_1_55_0\doc\html\images\accumulators\structboost_1_1accumulators_1_1detail_1_1is__tail__variate__feature_3_01tag_1_1tail__variate_3_01bd5040caa5e48b0af425af2314206bf.png As you may notice, the end of that particular file ends in a uuid / guid. It may be as easy as making that uuid appear 30 or 40 characters sooner in the path. ************************************************************************************************************** Is it unreasonable to ask that the boost zip only use half (130 characters) of the available Windows path size for itself? ************************************************************************************************************** On a related note, is it unreasonable to ask that an --abbreviate-paths build of boost limit itself to 130 characters? I acknowledge that this one is a bit harder to solve as there can be a large number of build "pivots" that all add to the path, but some clients (like me) need to layer other build pivot and version information on top of what boost already provides, and I need some amount of character wiggle room to make that happen. This isn't currently in as bad of a shape as the zip file. For an outdated piece of information, my win64 builds of boost 1.50 have a path part of 151 characters. boost\bin.v2\libs\test\build\msvc-11.0\rls\adrs-mdl-64\async-excpt-on\dbg-symbl-on\lnk-sttc\thrd-mlt\libboost_unit_test_framework-vc110-mt-1_50.lib.rsp Is there significant value in putting "bin.v2\libs" in the path?

6 16

[Config] Need more macros for VS2013
by Daryle Walker 24 Nov '13

24 Nov '13

I tried to use Visual Studio 2013 for the first time. I added the version of Boost 1.55 from NuGet. I've been adding macros from Boost.Config to help, but we need some more: 1. VS2013 doesn't support the "alignof" operator. 2. VS2013 doesn't support in-class class-static constants besides integers and enumerations. In my case, I had an array of size_t. C++11 is supposed to allow any literal (including arrays thereof) type. I had some other weird errors that are show-stopping. 1. I guess VS2013 uses smart iterators for std::array by default/debugging-mode. They don't convert to a pointer-to-element-type. I changed one function to use a pair of const_iterator, but a different function gave an internal error (C1001) when I tried to fix that one. 2. Boost.Test macros are complaining all over about mismatched arguments. When using MinGW, I used Boost from the trunk, because the release branch wouldn't compile. I'm guess that the NuGet version of Boost grabs from release, therefore I get the Boost.Test problems back. How do I use a copy of the Boost trunk in VS 2013 Express? (I got a Subversion download of both branches.) Daryle W.

5 4

Design query using Boost.
by Rahul Mathur 24 Nov '13

24 Nov '13

All, I have a design sinerio. I have different struct (C structures) having different data's but NO similarities between struct and each struct does different operations. The struct for example are - struct Apple { int A; char B; long C; double d; .. ..}; struct Orange { char A; int B; unsigned int C; long d; .. }; and maybe few more. Above few struct data members have dynamic data and other members have fixed/hardcoded datas. The complete struct is send as a buffer to a remote machine through native send()/read() API calls which has been successfully implemented. Please note this data as tested were hard coded or completely static but didn't had combination of dynamic/real and static data.. Now such operations (viz different or repeated) with ONE/MULTIPLE SET of data could be many as 1000, I wish now to send complete operations to remote machine, get a ACK from it and work on this struct data with modification/cancellation/reject/etc operations. One way could be to work with something similar - struct Apple { ... ..}; vector <Apple> data; data.insert (begin();end()) --- But, I have few questions - 1. I can have "std::map<string, vector>" and send this data as native send(). Latter read/recv() with string. Am I correct as I would have multiple operations? 2. I do wish to maintain synchronisation using Boost::lockfree mechanism latter? 3. Any other techniques? Thanks.

1 0

Adjacency lists
by Nouf M. 24 Nov '13

24 Nov '13

Hi, I have two *huge* text file with graph data.. the format of the files are as follows: File 1(vertices): Two field in each line (name + weight) e.g. Dan 5 David 7 Jack 3 File 2(edges): Three fields in each line (name name weight) e.g. Dan David 3 Jack David 1 I would like to store the data in an adjacency list using boost. I have wrote the following code: struct VertexProperties { //std::size_t index; std::string name; int weight; }; struct EdgeProperties { EdgeProperties(const int& w) : weight(w) { } int weight; }; My question, is the above code correct? should I include an index in the VertexProperties (I don't have an index in my graph data)? What is more efficient in the searching (latter on) with or without an index? Thank you...

1 0

R-MAT graphs
by Nouf M. 24 Nov '13

24 Nov '13

Hi, I have recently downloaded Boost… I tried the example in the “getting started” page (Lambda)… it worked which means that the installation is fine… The main purpose of installing Boost is that I want to generate graphs using R-MAT in which I found an example at: http://www.boost.org/doc/libs/1_50_0/libs/graph_parallel/doc/html/scalable_… I copied the example and pasted it in the place of the (Lambda) example to make sure that the project is opened correctly (I’m using visual stdio 2012), however, It did not compile successfully, I received the following error: fatal error C1189: #error : "Parallel BGL files should not be included unless <boost/graph/use_mpi.hpp> has been included" I tried to include <boost/graph/use_mpi.hpp> but with no luck, I received the following error: fatal error C1083: Cannot open include file: 'mpi.h': No such file or directory What should I do? Please help me… Best regards, Nouf

2 2

[Conversion] Ready to turn off write access to svn?
by Beman Dawes 24 Nov '13

24 Nov '13

According to the calendar (http://www.boost.org/community/index.html) it is time to turn off write access to the Subversion repo. Are there any showstoppers? --Beman

8 16

Subversion repository closing. Conversion to Git imminent.
by Beman Dawes 22 Nov '13

22 Nov '13

The Boost Steering Committee has given the final approval for the conversion from Subversion to Git, including the modularization of Boost library repositories. The Subversion repository will be closed for all changes to all branches, including the sandbox, Sunday, November 23 2013, 00:00 hours UTC. That's 8 PM Saturday, US East Coast time, and 5 PM US West Coast time. Please make no svn commits after that time. We will be adding a pre-commit hook that prevents commits, but please do not wait for that becomes active. After svn is closed, the conversion will be run one last time, and then turned off. Then there is a week set aside for final validity checks, testing, and general scurrying around. When that is done, the boostorg repo on GitHub will open for business. If everything goes smoothly, it may take less than a week but if there are glitches it may take longer. --Beman

2 3

milliseconds UTC from discrete year, month, day, hour, minute, second
by Victor Yankee 22 Nov '13

22 Nov '13

Hello, Can someone should me how to calculate the milliseconds since jan 1, 1970 in UTC, given separate variables holding the year, month,day,hour,minute and seconds? Thanks,

3 2

[MPL] Reason for mpl::quote's name
by Louis Dionne 22 Nov '13

22 Nov '13

Hi, I was just wondering about the origin of the `mpl::quote` metafunction class. Why was this name chosen? Thanks, Louis Dionne

4 5

[Boost-build] Android tests run
by Antony Polukhin 22 Nov '13

22 Nov '13

Hi all, With help of Steven Watanabe, Vladimir Prus and Boost-for-Android project, I've finally run the regression tests on Android ARM. Results can be already seen on the regression test page for trunk. Here is a description of some common issues that can be seen in regression tests results: "arm-linux-androideabi/bin/ld.exe: error: cannot find -lrt" Some of the Android libraries (for example librt) are merged with libc. Some patches to b2 required not to add -lrt fot the platform. "soinfo_link_image(linker.cpp:1635): could not load library "libboost_unit_test_framework-gcc-d-1_55.so.1.55.0" needed by "./copy_if_test1"; caused by load_library(linker.cpp:745): library "libboost_unit_test_framework-gcc-d-1_55.so.1.55.0" not found" This is because of cross compilation - tests are compiled in Win and then copied to the emulator. This is an error in my copying script that will be fixed someday. Also please note, that sources are compiled with -DBOOST_ASIO_DISABLE_STD_ATOMIC and -DBOOST_AC_USE_PTHREADS because there are some issues with std::atomic on android (See https://code.google.com/p/android/issues/detail?id=42735#makechanges ) This must be possibly added to the config of the libraries by default. Some hints: * You can check for android platform in your code using defined(__ANDROID__). * __ANDROID__ can run on different hardware, so do not assume that it will be always ARM. * Having problems with Jamfile and cross compilation? Use <target-os> instead of <host-os> in your jamfiles. * Boost-for-Android project ( https://github.com/MysticTreeGames/Boost-for-Android) may contain some useful fixes for your library. Author of the library "would love" to see the issues integrated, see discussion at https://github.com/MysticTreeGames/Boost-for-Android/pull/15 This letter is cc'ed to the boost-build because of: * "-lrt" issues * Is there a way to install/call_script for all the boost libraries before running the regression tests? * specifying "<threadapi>pthread" in user-config.jam does not work -- Best regards, Antony Polukhin

1 0

[chrono] boost::chrono::floor() and negative durations
by Krzysztof Czainski 22 Nov '13

22 Nov '13

Hello, The function boost::chrono::floor() is documented: "This function round down the given parameter." Therefore I expect the assert in the following program to pass, but it fails: #include <boost/chrono/floor.hpp> #include <cassert> int main() { boost::chrono::nanoseconds const nsec( -1 ); boost::chrono::seconds const sec = boost::chrono::floor<boost::chrono::seconds>(nsec); assert( sec.count() == -1 ); } Is this intended behavior? If yes, could the docs be updated to clarify this? Regards, Kris

3 6

Fwd: Ask for a solution regarding to the function intersection() in boost geometry
by Jun Zhang 21 Nov '13

21 Nov '13

Dear Sir/Madam, Many thanks for your work on boost library. I am a user of the library. But now I meet a problem regarding to the function intersection. Could you please see the attached file. When I get the intersection of the polygon "red" and "blue" with the function, the output is the "green" (only one polygon). However, "green" should be two polygons. And if the green is regarded as one polygon, there is some error to get the intersection of it with others. That means I cannot calculate the intersection of "green" and "blue" with intersection(). The error is as following: This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. terminate called after throwing an instance of 'boost::geometry::overlay_invalid_input_exception' what(): Boost.Geometry Overlay invalid input exception All the best -- Dr.-Ing. Jun Zhang Jülich Supercomputing Centre Institute for Advanced Simulation phone +49 2461 61 1995 E-Mail: ju.zhang(a)fz-juelich.de<mailto:ju.zhang@fz-juelich.de> Internet: http://www.fz-juelich.de/ias/jsc ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------

1 0

Problems building boost.python against python 3.x on Windows
by Fredrik Orderud 21 Nov '13

21 Nov '13

There seem to be a problem building boost.python against python 3.x on Windows. Steps to reproduce: * Download & unzip boost 1.55 * bootstrap.bat * set PYTHONHOME=C:\Python33 * b2 link=shared runtime-link=shared toolset=msvc-11.0 b2 will then output the following: --- warning: No python installation configured and autoconfiguration note: failed. See http://www.boost.org/libs/python/doc/building.html --- This does not happen if building against Python 2.7 with set PYTHONHOME=C:\Python27. I suspect that the reason is due to tools\build\v2\engine\build.jam only containing logic for python 2.2-2.7. Could anyone please look into this? Thanks in advance, Fredrik

1 0

[Config] N3276 decltype support detection missed for VC++12 (Ticket #9410)
by Michel Morin 20 Nov '13

20 Nov '13

As you know, VC++12 (aka 2013) completed N3276 decltype support. (See, e.g. http://msdn.microsoft.com/en-us/library/vstudio/hh567368.aspx http://thread.gmane.org/gmane.comp.lib.boost.devel/233752/focus=239118 ) Unfortunately the detection code for VC++12's N3276 decltype support hasn't been updated yet, as reported in #9410 (decltype N3276 for MSVC12 + compile fix for tests) https://svn.boost.org/trac/boost/ticket/9410 Ticket #9410 has a patch for this issue. The patch also fixes the test code of Boost.Config. Regards, Michel

1 0

Re: [boost] decay.hpp problem
by Tim Burgess 20 Nov '13

20 Nov '13

OK, Here's the output from the Log Navigator, showing how includes are being stacked. I've placed it at: https://dl.dropboxusercontent.com/u/29578720/Build%20log.rtf I noted the references to wxAny, which I was using for handling variants, but I've now replaced this with boost::any and I'm not including wxAny in any of my modules, despite the log seeming to implicate this class. Again, the new version of the code builds fine using VS2010, but fails using Xcode. Best wishes. Tim Burgess -----Original Message----- From: Steve Ramsey [mailto:steve@lucena.com] Sent: 18 November 2013 18:59 To: tim(a)raisedbar.net Subject: Re: [boost] decay.hpp - anonymous enum problem On Nov 18, 2013, at 7:37 AM, Tim Burgess <tim(a)raisedbar.net> wrote: > I'm pretty much a newbie when it comes to Xcode, so I've no idea how > to get you that trace - the Issue Navigator gives me no clues as to > what's including/calling decay.hpp. Any clues/links to reading > materials would be most welcome. I find the Log Navigator using the Assistant editor pane to be more flexible than the Issue Navigator when dealing with failed build detritus. So, from the Log Navigator, select your failed build. In the editor pane, you'll find an expandable list of build issues broken down by file. On the far right side of each file-level entry, there is a "show transcript" widget; popup text shows the internal command that was issued for the file and when it was issued. Clicking the widget will show a complete dump of the compiler/linker output for that particular command. It's also possible to right-click on any given issue entry and copy the transcript for either just the current issue or for the entire filtered list of issues. Steve

3 3

VC2013 1.55 beta failures
by Olaf van der Spek 19 Nov '13

19 Nov '13

Hi, Building 1.55 beta keeps failing on VC2013 RC. Trunk fails too IIRC. compile-c-c++ bin.v2\libs\date_time\build\msvc-12.0\debug\link-static\threading-multi\gregorian\greg_month.obj greg_month.cpp C:\VC\boost_1_55_0b1\boost/iterator/detail/facade_iterator_category.hpp(166) : error C2039: 'assert_not_arg' : is not a member of 'boost::mpl' C:\VC\boost_1_55_0b1\boost/mpl/eval_if.hpp(41) : see reference to class template instantiation 'boost::detail::facade_iterator_category_impl<CategoryOrTraversal,ValueParam,Reference>' being compiled with [ CategoryOrTraversal=boost::forward_traversal_tag , ValueParam=std::basic_string<char,std::char_traits<char>,std::allocator<char>> , Reference=const std::basic_string<char,std::char_traits<char>,std::allocator<char>> & ] C:\VC\boost_1_55_0b1\boost/iterator/detail/facade_iterator_category.hpp(193) : see reference to class template instantiation 'boost::mpl::eval_if<boost::detail::is_iterator_category<CategoryOrTraversal>,boost::mpl::identity<boost::forward_traversal_tag>,boost::detail::facade_iterator_category_impl<CategoryOrTra versal,ValueParam,Reference>>' being compiled with [ CategoryOrTraversal=boost::forward_traversal_tag , ValueParam=std::basic_string<char,std::char_traits<char>,std::allocator<char>> , Reference=const std::basic_string<char,std::char_traits<char>,std::allocator<char>> & ] C:\VC\boost_1_55_0b1\boost/iterator/iterator_facade.hpp(104) : see reference to class template instantiation 'boost::detail::facade_iterator_category<CategoryOrTraversal,ValueParam,Reference>' being compiled with [ CategoryOrTraversal=boost::forward_traversal_tag , ValueParam=std::basic_string<char,std::char_traits<char>,std::allocator<char>> , Reference=const std::basic_string<char,std::char_traits<char>,std::allocator<char>> & ] C:\VC\boost_1_55_0b1\boost/iterator/iterator_facade.hpp(620) : see reference to class template instantiation 'boost::detail::iterator_facade_types<Value,CategoryOrTraversal,Reference,Difference>' being compiled with [ Value=std::basic_string<char,std::char_traits<char>,std::allocator<char>> , CategoryOrTraversal=boost::forward_traversal_tag , Reference=const std::basic_string<char,std::char_traits<char>,std::allocator<char>> & , Difference=ptrdiff_t ] C:\VC\boost_1_55_0b1\boost/token_iterator.hpp(40) : see reference to class template instantiation 'boost::iterator_facade<boost::token_iterator<TokenizerFunc,Iterator,Type>,Type,boost::forward_traversal_tag,const Type &,ptrdiff_t>' being compiled with [ TokenizerFunc=char_separator_type , Iterator=std::_String_const_iterator<std::_String_val<std::_Simple_types<char>>> , Type=std::basic_string<char,std::char_traits<char>,std::allocator<char>> ] C:\VC\boost_1_55_0b1\boost/date_time/date_parsing.hpp(132) : see reference to class template instantiation 'boost::token_iterator<TokenizerFunc,Iterator,Type>' being compiled with [ TokenizerFunc=char_separator_type , Iterator=std::_String_const_iterator<std::_String_val<std::_Simple_types<char>>> , Type=std::basic_string<char,std::char_traits<char>,std::allocator<char>> ] C:\VC\boost_1_55_0b1\boost/date_time/gregorian/parsers.hpp(30) : see reference to function template instantiation 'date_type boost::date_time::parse_date<boost::gregorian::date>(const std::string &,int)' being compiled with [

13 52

Interesting variadic template trick
by Louis Dionne 19 Nov '13

19 Nov '13

Hi, As some might know, I'm currently working on a reimplementation of the MPL for C++11. In doing so, I came across a technique that I did not know of and I thought I would share my discovery with the community. If this is already well known, please excuse my ignorance. The goal is to implement fast compile-time conjunction and disjunction. It goes like this: template <typename ...T> void allow_expansion(T&&...); template <typename ...T> struct or_ { static constexpr bool value = !noexcept( allow_expansion((T::value ? throw : 0)...) ); }; That's it! Note that disjunction is easily obtained in a similar way. The benefit of this technique over traditional implementations is that it's several times faster according to my benchmarks. However, you might have noticed that short-circuit evaluation is not respected so the above technique is only suitable when short-circuit evaluation is not required. If you find this interesting, see [1] for a collection of similar techniques. The one I posted above seems to be the fastest with Clang and GCC. Regards, Louis Dionne [1] https://gist.github.com/ldionne/7522393

7 12

[git help] GitHub boostorg library authentication
by Beman Dawes 19 Nov '13

19 Nov '13

To test the modular boost docs I'm writing, I did this: git clone --recursive https://github.com/boostorg/boost.git modular-boost cd modular-boost ./bootstrap.sh ./b2 headers cd libs/system git checkout develop # did a simple edit of one file git commit -a -m "my bug fix" git push origin develop Everything ran as expected until the last step, which resulted in this: Username for 'http://github.com': That's a problem. Authentication needs to happen automatically. What steps did I miss? Thanks, --Beman

6 11

Re: [boost] Improving Documentation
by Andrew Hundt 19 Nov '13

19 Nov '13

On Thu, Oct 10, 2013 at 12:20 AM, Robert Ramey <ramey(a)rrsd.com> wrote: > Jeff Flinn wrote: > > On 10/9/2013 12:41 PM, Robert Ramey wrote: > >> Daryle Walker wrote: > >>>> From: ramey(a)rrsd.com > > I wish this thread had come up 3-4months ago. Unlike you I couldn't > > grok the docs to use multi-array as a back end to a Qt table where I > > needed > > to support run time row/col insertion/deletion. I was under time > > constraints and found it much easier to build my own facilities. I'm > > not sure whether it was due to docs or design. > > Well, I did come to understand it pretty well. But I really have to > say I spent a LOT of time poring over the documentation, experimenting > etc. The oddest thing to me is that now it seems easy to me and I > can't figure out what I spent the time on - we're talking a few days. > I had the same experience (only worse) with units library. Actually > I have this experience with almost every boost library I use. This > brings up the whole question of documentation of boost libraries > and in fact documentation of computer libraries in general. I've spent > a lot of time thinking about this lately. I feel we've been too lax in > accepting libraries after the review whose documentation isn't up > to some minimum standard (not that we have a standard). > > Robert Ramey > +1 Every boost library I've used has been great once I've understood it. However, I have trouble getting some very smart people on my team to use existing boost tools because they find it confusing, and they also have a tough time finding the functionality they need. I believe this is a documentation problem. For example, a number of people I know were surprised when I told them that the /libs folder contains examples and unit tests for every library. The documentation doesn't seem to consistently provide links and explanations of each. I believe I spent months as a user before I found the libs folder. I'll take boost.container.static_vector, as an additional example. I contributed to it so it seems like a decent choice. Here are the two most easily accessible links in Boost.Container for documentation of static_vector: http://www.boost.org/doc/libs/1_54_0/doc/html/container/non_standard_contai… The first link contains the first block of text about static_vector I expect one would run into, and there isn't even a link to the class documentation! http://www.boost.org/doc/libs/1_54_0/doc/html/boost_container_header_refere… This second link is the typical header documentation throughout boost. When I first started using boost it was months before I realized that in these header synopsis I could click on the words of the class to see the full documentation of that class, in this case "static_vector". Much of the time I just felt confused and lost. I think this is indicative of a layout and user interface that needs some improvement. Now, perhaps I should blame myself for this in the static_vector case and fix it, but it is indicative of the general documentation problems. One example of C++ documentation I have found that I've actually been happy with is cppreference.com. If you look at their front page they have many of the major classes, and with one click you are in there reading what you want to know, with examples at the bottom of every page. It is actually entertaining that they mention boost documentation in their FAQ as follows: Why is the material here limited to the standard C and C++? > In short, we chose quality over quantity. Some boost libraries<http://www.boost.org/> could > also be candidates for inclusion though. While their tutorials are very > good, the *reference* documentation is often very inflexible and > inconvenient. So, is there anything we can do about it? I remember a couple of years ago Boost had a "Bug Sprint" with the goal of closing lots of open tickets. Perhaps we should do a "documentation sprint"? Here is an interesting article about writing good documentation that also contains links to other solid articles that I recommend checking out: http://stevelosh.com/blog/2013/09/teach-dont-tell/ Cheers! Andrew Hundt

13 63

[git] [modular boost] Switchover schedule proposal
by Beman Dawes 19 Nov '13

19 Nov '13

The showstoppers other than documentation have been cleared from the conversion issues list. That includes the issues blocking documentation, so doc work is underway again. The 1.55 release is scheduled for November 4, and as of the moment it doesn't look like that will sip much if at all. I'm assuming that we want to reopen svn branches/release for a week or so after 1.55 ships as some developers would like to merge pending changes to branches/before the switchover. That would mean an actual switchover starting about November 11. It seems to me we need approximately a week after svn is made read-only and the final conversion run is done to verify the correctness of the conversion. During that time it seems to me that it would be unwise for developers to make git commits since if a serious problem was discovered we might decide to rerun the conversion process, wiping out the git repos. At that point (roughly November 18, we would go totally live and developers could resume their work, now using git and modular boost. Comments, --Beman

10 33

concept_check() fails for types from unnamed namespace on gcc 4.2.3
by Adam Romanek 19 Nov '13

19 Nov '13

Dear Boosters! I already posted this message to boost-users lists last week but I got no response. So here we are. I have a problem compiling some source code that uses Boost 1.54 and gcc 4.2.3 (it's a toolchain for a MIPS platform but that's irrelevant). Basically there is a problem with checking concepts on types that come from unnamed namespaces. See the attached code example and compiler error message. Note that the same code compiles without any problems on gcc 4.6.3. I've found a question on boost-dev list [1] and a ticket [2] related to this particular issue. Note that the ticket was closed with "worksforme" resolution, which I don't understand - the problem is still out there. Now since Boost's minimal requirements are gcc 3.3 [3] then should I consider it a bug that I should report or is it a known issue? In case the latter is true then what should I do? [1] http://boost.2283326.n4.nabble.com/concept-check-fails-with-types-declared-… [2] https://svn.boost.org/trac/boost/ticket/2037 [3] http://www.boost.org/users/history/version_1_55_0.html WBR, Adam Romanek

3 2

[asio] How to initialize a strand
by Kyle Ketterer 19 Nov '13

19 Nov '13

Hello, I am just curious - how you can you initialize an strand via assignment? I am passing an strand by reference to an object so I have a reference variable declared: boost::asio::io_service::strand & strand_; In the constructor I would like to assign the reference variable an io_service (which has also been passed by reference). I would like to initialize strand_ in a way such as this ( I know it doesn't work) strand_ = boost::asio::io_service::strand(io_service_); Any ideas? Thanks

2 2

New Windows Build of 1.55.0
by Tom Kent 19 Nov '13

19 Nov '13

The previous build of 1.55.0 did not build with the correct zlib version (and thus the correct sub-library of iostreams did not build). I have created a 1.55.0-build2 directory on the sourceforge page with the updated version. I've also added a note to the 1.55.0/README.md file explaining that it is incomplete, but I did not remove the prior build. http://sourceforge.net/projects/boost/files/boost-binaries/1.55.0-build2/ Tom

1 0

decay.hpp - anonymous enum problem
by Tim Burgess 18 Nov '13

18 Nov '13

Hi, I have a project for Windows/Mac that builds fine using VS2010, but generates errors when I build using Xcode 4.6 with the Apple-provided GCC 4.2 compiler (required, as this project also uses wxWidgets). All of my own modules compile cleanly, but I get the following error output: SurfaceReader Group /users/tim/developer/libraries/boost_1_54_0/boost/type_traits/decay.hpp /users/tim/developer/libraries/boost_1_54_0/boost/type_traits/decay.hpp:28: '<anonymous enum>' is/uses anonymous type /users/tim/developer/libraries/boost_1_54_0/boost/type_traits/decay.hpp:28: Trying to instantiate 'template<class T> struct boost::remove_reference' /users/tim/developer/libraries/boost_1_54_0/boost/type_traits/decay.hpp:38: '<anonymous enum>' is/uses anonymous type /users/tim/developer/libraries/boost_1_54_0/boost/type_traits/decay.hpp:38: Trying to instantiate 'template<class T> struct boost::remove_reference' I realise that I haven't provided the command that Xcode is using to build the project - this isn't deliberate, but I can't seem to locate where Xcode provides this on-screen using the VoiceOver accessibility tool (I'm a totally blind developer). I don't include decay.hpp directly in any of my modules, but further research turned up: https://svn.boost.org/trac/boost/ticket/6362 If I can find the anonymous enum within the files included within decay.hpp I can patch it by providing a tag for the enum and I believe that this will rectify the issue. Can anybody point me at the appropriate file, or have I got to plough through the lot? I initially discovered this issue in Boost 1.54.0, but I can also reproduce it using 1.55.0. Many thanks in advance. Best wishes. Tim Burgess

3 4

[concept] Changeset 84470 in trunk wasn't merged to release
by Stephan T. Lavavej 17 Nov '13

17 Nov '13

Hi, https://svn.boost.org/trac/boost/changeset/84470 was committed to trunk 6 months ago, but it wasn't merged to release and isn't present in 1.55.0. It fixes a blizzard of "unused local typedef" warnings with GCC 4.8. Can someone merge this to the release branch? Thanks, STL

1 0

[multiprecision] Radix-2 typedef naming convention
by Christopher Kormanyos 17 Nov '13

17 Nov '13

Hi folks, Lost the original message here. Sorry. In John's new radix-2 MP back end, names are used for common types such as: float24_t, float53_t, float113_t. In our proposal for floating-point typedef's having specified widths, we use names such as: float32_t, float64_t, float128_t. Both conventions make sense in sensible ways. But only one naming convention should be used, and it should be used consistently. Which one will it be? Sincerely, Chris.

6 23

Re: [boost] Valgrindandboost::filesystem::path::has_branch_path()
by Miguel Guedes 17 Nov '13

17 Nov '13

On Sun, 17 Nov 2013 11:16:08 +0100, Bjorn Reese wrote: > This is a valgrind problem: > > https://bugs.kde.org/show_bug.cgi?id=307828 > That's great to hear. Many thanks for the clarification.

1 0

Valgrind andboost::filesystem::path::has_branch_path()
by Miguel Guedes 17 Nov '13

17 Nov '13

Hello list, Valgrind reports invalid reads [0] in a very simple example I've uploaded to pastebin [1]. Is there some funky stuff happening behind the scenes that is causing a false positive or is this really an issue? Using libboost 1.54 on Linux. [0] http://pastebin.com/HmS94cwF [1] http://pastebin.com/h98z2K1Z

2 1

Boost.Application new version available.
by Re 15 Nov '13

15 Nov '13

Hi Brook, Thanks for your commenets. I will try aswer your questions, if any thing is not clear, let me know. First at all, this lib is a working in progress (prototype), and it is open for suggestions and improvements. Feel free to suggest a new feature or change, I'm trying to listen to everyone. And I have tried to implement all the requests that come to me so far. (Obviously, this is limited to my knowledge (which is not big)) >> I am having trouble seeing how it would integrate with Boost.Asio. Well, I use Asio only to support signals. I do not want to expose "ASIO" directly. I do not know if the final version I will use "ASIO" to handle signals or if I remove this dependency. E.g.: In version 0.3 I dont use ASIO. >> I don't see how to control what signal a handler is responding to. Well, here you have to choose in use defaults, or customize. The default will hide all details, and will work on UNIX (Terminal/Daemon) and WINDOWS (Console/Service) without modifications. The default map is: SIGINT, SIGTERM, SIGABRT will call handler defined on callback of termination_handler, check: https://github.com/retf/Boost.Application/blob/master/libs/application/examp le/termination_handler.cpp An exception is the windows service, which is mapped from events of SCM. If you want to customize, you must take into consideration the type of application and platform chosen. E.g. Windows Services dont known anything about SIGNALS, in this case you need customize aspects handlers, on POSIX you can use aspects handlers, signal_manager class, and/or self-pipe aspect, check: http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/boost_applica tion/customization.html#boost_application.customization.customize_signal http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/boost_applica tion/posix_specifics.html#boost_application.posix_specifics.self_pipe_ >> I also don't really see why you would need to co-opt SIGUSR1; having both USR1 and USR2 available for applications is important in some cases Here user can change this, see: http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/boost_applica tion/customization.html#boost_application.customization.customize_signal Well, I can think in other way to do this here, user other signal. Do you have any idea? Let me know! >> Related to Boost.Asio integration, how would an application make use of all the rest of that library (timers, sockets, etc.). It seems that a core design principle ought to be that the full range of Asio capability would be available. You can have your own io_service, check this sample: https://github.com/retf/Boost.Application/blob/master/libs/application/examp le/uuid_client_server/server.cpp >> I am unclear about "aspects". It seems that in the simplest case any class will work as an aspect. This is true. >> In more complex cases a class must be derived from the aspect_contractor abstract base class. Some aspects are used internally by application mode, then it need follow one interface, that application mode will use. (like a concept) >> Perhaps I missed it, but where is the aspect_contractor interface documented? Sorry, I forgot to document each aspect abstract class interface. Here you can have one idea: http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/boost_applica tion/customization.html >> More fundamentally, under what conditions will which aspect member functions be called. Some aspect member functions are called by application mode internally on lib. >>and what member functions must be provided for "any class" to actually work in this capacity? The abstract contractor class will tell you what you need provide to aspect work internally on application mode. >> Even more fundamentally, can you give some intuition regarding how you see structuring an application in terms of different aspects interacting with each other? Well, this is hard to say (Or better, I do not know the answer). In general form, an application context pool, can have any number and types of aspects, then you can design anything here. Some aspects are needed by application mode, but you can make your own application mode. You have a lot of possibilities here! >> Or, do you envision that the bulk of the application logic is independent of your library classes, i.e., it resides in the user-provided application operator function, and only small bits like termination signals would be handled by the library? At this moment, I want more independent possibly. The use of aspects provide this, we have all pieces separated, and we can tie all, in many ways. E.g. The limit single instance is an aspect. And in future we can have one aspect to TCP/IP for sample, that use asio, or other thing. I dont know. >> I guess I am confused about your vision of how a large, complex application would be structured if it were to make use of your library. If you check lib design, you will see, that lib is composed by a many independents pieces of code, that are tied at run time. http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/boost_applica tion/design_overview.html The lib provides the more usual features in ready to use form, but you can customize any piece, and tie in any way that you want. If this large application is very complex, you can decompose it in many aspects, and you can make one custom application mode, and you can use some of ready to use aspects on it too. To give you the right answer, I need know more about this application. Is hard to say. In my personal experience (little experience), I already used this lib (0.2, 0.3 and 0.4) on Client service, MPI cluster (for credit card processing), on TCP/IP (ASIO Based) Server (Daemon mode). All using plug-in system (that are provided by library too). >> What would be the division of labor between library-related classes (including user-derived library classes) and independent user-provided code? Check this: http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/boost_applica tion/design_overview.html This clarifies a little? Well, The user can use singularity and get access to context in any location too. >> Finally, note that the links to your example files do not work. This is true, the documentation was generated by quickbook, and dont work on my server, you need check code on github. Sorry! Well, one question. Do you think that this library can be useful? Sorry my english is not very good (is very bad), if any thing is not clean let me know! -- Renato

1 0

[mpl] clang error for narrowing from unsigned int 0xffffffff to long
by Edward Diener 15 Nov '13

15 Nov '13

In the mpl bitwise.cpp test there are lines like: MPL_ASSERT_RELATION( (bitor_<_0,_ffffffff>::value), ==, 0xffffffff ); MPL_ASSERT_RELATION( (bitor_<_1,_ffffffff>::value), ==, 0xffffffff ); MPL_ASSERT_RELATION( (bitor_<_8,_ffffffff>::value), ==, 0xffffffff ); Using clang under Windows with the VC++ RTL ( clang-cl ), clang gives an error of: bitwise.cpp(43,25) : error: non-type template argument evaluates to 4294967295, which cannot be narrowed to type 'long' [-Wc++11-narrowing] MPL_ASSERT_RELATION( (bitor_<_0,_ffffffff>::value), ==, 0xffffffff ); for the bitor_<_0,_ffffffff>::value expression part since the assert_relation template takes two 'long's as its values. Is this an actual bug according to the C++11 standard ? I would have thought that an unsigned int value of 0xffffffff would fit into a long as a -1, but it sounds like the new standard is saying that since the value of 4294967295 cannot be encompassed by a long it is an error. if it is an error how should it be fixed in MPL ?

3 9

typesafe printf with variadic template
by Michael Marcin 14 Nov '13

14 Nov '13

It seems a common example for C++11 and variadic templates is a typesafe printf which is supposed to obsolete things like Boost.Format. However there doesn't seem to be one usable out of the box. If this is really a large improvement shouldn't this facility be in boost?

4 3

Any interest in hashing algorithms SHA and/or FNV1a?
by foster brereton 14 Nov '13

14 Nov '13

I have been working on implementations of the SHA and FNV-1a class of hashing algorithms. Both are header-only. SHA (Secure Hash Algorithms) Implementations for SHA-1, -224, -256, -384, and -512. It does not implement the more recent SHA-3 (Keccak) algorithm. It would not be difficult to add support for 512/224 and 512/256 if they were desired. The routines support bit-level messages, meaning they can correctly digest messages that do not end on a byte boundary. More information here: http://en.wikipedia.org/wiki/Secure_Hash_Algorithm FNV (Fowler–Noll–Vo) The header supports the FNV-1a algorithm, which has better distribution characteristics than its cousin, FNV-1. I have added support for 32-, 64-, 128-, 256-, and 1024-bit variants. This is not a cryptographically secure algorithm, however is much faster than its crypto cousins and as such is a solid algorithm for obtaining unique hash values for e.g., data structures. I have also implemented a constexpr variant of the algorithm (32-bit and 64-bit only) for const char* to further performance when needed by pushing the hash to compile-time computation. More information here: http://en.wikipedia.org/wiki/Fowler%E2%80%93Noll%E2%80%93Vo_hash_function The algorithms are currently part of the Adobe Source Libraries on GitHub: SHA: https://github.com/stlab/adobe_source_libraries/blob/sha_cleanup/adobe/sha.… (note: the master branch version needs updating to this one.) FNV-1a: https://github.com/stlab/adobe_source_libraries/blob/master/adobe/fnv.hpp Would these algorithms be of general use to the Boost community? If so I would be willing to submit them formally.

7 25

Proposed Boost.Application Library new version available.
by Renato Forti 14 Nov '13

14 Nov '13

Hi Lars, >> I don't know if this has been raised before in the discussion of previous versions, but it's customary to not call something just "Boost.Whatever" if it's not an actual accepted Boost library. Thanks for the warning! >From now on I will always use: "Proposed Boost.Application Library" >> You should probably not use the actual Boost logotype in the documentation either... I used the Quickbook to generate the documentation. Quickbook adds 'boost' logotype automatically. Is there any way I can generate the documentation using the Quickbook, that does not include the 'boost' logotype? >> ... there should be one somewhere with the text "provisional" or "proposed" superimposed on it. On the first page of documentation I have this Caution: "Caution This is not yet an official Boost C++ library. It wasn't reviewed and can't be downloaded from www.boost.org. This beta is available to boost community to know real interest and get comments for refinement. The intention is to submit library to formal review, if community think that it is interesting!" That's not enough? Thanks a lot

2 2