January 2014 - Boost - lists.boost.org

[git] Some headers are executable
by Andrey Semashev 08 Jan '14

08 Jan '14

Hi, I've just checked out git and ran b2 headers and noticed that some headers have executable attribute. For example: $ find boost -executable -type f boost/pointee.hpp boost/assign.hpp boost/graph/vf2_sub_graph_iso.hpp boost/indirect_reference.hpp boost/parameter.hpp boost/detail/indirect_traits.hpp boost/detail/is_xxx.hpp boost/range.hpp This was not the case with svn. Is this the result of the transition? Can this be fixed?

2 4

[github] default PR destination
by Tim Blechmann 08 Jan '14

08 Jan '14

hi all, any opinion to change the default branch from "master" to "develop"? with the boost branching model all contributions via github's pull requests apparently have to go to "develop" rather than going directly into "master", so this should be the default destination for pull requests. github allows to set the default branch [1] ... not sure if this has any other side effects, but i'd vote for changing the default to "develop". thoughts? tim [1] https://help.github.com/articles/setting-the-default-branch

10 14

[ANN] Registration for C++Now 2014 is Open
by Boris Kolpackov 07 Jan '14

07 Jan '14

Hi, Registration is now open for the eighth annual C++Now conference (formerly BoostCon) which will be held in Aspen, Colorado, USA, May 12th to 17th, 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. In particular, one of the tracks is dedicated exclusively to tutorials. Last year the conference sold out pretty quickly and we expect it to happen again this year. As a result, we encourage anyone interested in attending to register early. Additionally, early bird hotel reservations end January 10th. For more information on registering, visit: http://cppnow.org/2014/01/2014-registration-is-open/ For early bird hotel reservations, visit: http://cppnow.org/location/lodging/ For general information about the conference, visit: http://cppnow.org/about/ Boris

1 0

[git] An ignore file for the top-level repository?
by Daryle Walker 07 Jan '14

07 Jan '14

I cloned a copy of the git version of the top-level Boost repository, which recursively added the individual libraries. The directions added two commands to run boot-strapping and build scripts. I had to set up an ".gitignore" file so the GUI GitHub app won't complain about those synthesized files. Shouldn't there already be an ignore file there that does this? (You only list the top-level files & directories; nested files automatically get ignored too.) I couldn't sync (i.e. upload) the ignore-file since I don't have write access for the top-level repository. So I'll get a conflict once someone does add an ignore file for everyone? Daryle W.

4 3

[build] Broken in develop?
by Andrey Semashev 07 Jan '14

07 Jan '14

Hi, I tried to update and recreate links to headers today and stumbled into this: $ b2 headers Unable to load Boost.Build: could not find build system. --------------------------------------------------------- /home/lastique/src/boost/boost-build.jam attempted to load the build system by invoking 'boost-build tools/build/src ;' but we were unable to find "bootstrap.jam" in the specified directory or in BOOST_BUILD_PATH (searching /home/lastique/src/boost/tools/build/src, /usr/share/boost-build). Please consult the documentation at 'http://www.boost.org'. Also, bootstrap.sh also seems to be not working: $ ./bootstrap.sh ./bootstrap.sh: 1: ./bootstrap.sh: ./tools/build/src/engine/build.sh: not found Building Boost.Build engine with toolset ... Failed to build Boost.Build build engine Consult 'bootstrap.log' for more details bootstrap.log contains: ./bootstrap.sh: 218: cd: can't cd to ./tools/build/src/engine I remember there were discussions about moving Boost.Build somewhere, and it appears that some scripts were updated for that but the actual Boost.Build code is still in tools/build/v2. I did 'git pull' in the Boost root, it's up to date.

3 3

[git] Did the user assignments carry over?
by Daryle Walker 07 Jan '14

07 Jan '14

What I mean is if the Subversion-to-Git transfer also mapped user accounts. Did any change in the Subversion repository that is blamed on me (on my Subversion/Trac account) get mapped to a change in the Git version that still blames me (on my GitHub account)? Or did all that blame information get purged? (Of course, assuming that it's possible, how would the converters know the mapping? And what happens when a Subversion user has dropped out or otherwise hasn't gotten a GitHub account (yet)?) Daryle W.

2 1

Proposed patch for Ticket #8250
by Borja Miñano 07 Jan '14

07 Jan '14

Good afternoon, I have proposed a patch for Ticket #8250 that is attached in the trac system. As I am new, I post to inform to take it into account for following versions. Hope this could help. -- Un saludo, Borja Miñano IAC3 - Universitat de les Illes Balears Mateu Orfila Building. Office F-213. Cra. Valldemossa km. 7,5 E-07122 Palma de Mallorca. Balears. Spain. Phone: +34 971 173 000 ext. 1318

4 3

[timer] conflict between tools/inspect and libs/timer
by Peter A. Bigot 06 Jan '14

06 Jan '14

A recent merge to master libs/timer includes support for inspect in the test suite, but the invocation requires support for a search-root argument in inspect. That support is not present in tools/inspect's master branch, causing the libs/timer tests to fail. The following process could help detect inter-module dependencies like this: * Initiate your workspace with the superproject checked out on branch master and all modules on the resulting commit (ignore branches). * Checkout the develop branch only for the module(s) you're working on. * Use "git submodule summary" at the superproject level to determine how your workspace differs from what would be expected in the master branch. If multiple modules show changes, there's a risk of coupling, and it might not be appropriate to push any of them to their master branch. * Use "git submodule update" to reset things when switching development between modules. Peter

6 16

graph_theory_review.html patch
by Mads Jensen 05 Jan '14

05 Jan '14

Hi, The link for the TOC of Introduction to Algorithms is broken. I've attached a patch to fix this; it now points to the page for the 3rd edition where the TOC and a sample chapter about multi-threaded algorithms can also be found. Also, the fourth author (Stein) is added. What are the rules for submission and inclusion of patches? I consider this quite trivial, but I have in mind to implement a couple of graph algorithms in order to learn the library, and get more acquainted with C++. Please CC when responding; I'm not yet a member of this mailing list. Thank you. -- Med Venlig Hilsen / Kind Regards, Mads Jensen Never laugh at live dragons. -- Bilbo Baggins [J.R.R. Tolkien, "The Hobbit"]

2 1

[develop] quickbook compile failure
by Tim Blechmann 05 Jan '14

05 Jan '14

hi all, trying to compile quickbook with apple's clang gives me the following error: > tim@moka-mac:~/dev/boost/tools/quickbook$ ../../b2 > Performing configuration checks > > - symlinks supported : yes > - hardlinks supported : yes > ...patience... > ...patience... > ...found 3129 targets... > ...updating 6 targets... > common.mkdir ../../dist > common.mkdir ../../dist/bin > darwin.compile.c++ ../../bin.v2/tools/quickbook/src/darwin-4.2.1/release/link-static/files.o > src/files.cpp:129:47: error: implicit instantiation of undefined template 'std::pair<boost::unordered::iterator_detail::iterator<boost::unordered::detail::ptr_node<std::__1::pair<const boost::filesystem::path, boost::intrusive_ptr<quickbook::file> > > >, bool>' > boost::tie(pos, inserted) = files.emplace( > ^ > ../../boost/detail/container_fwd.hpp:145:42: note: template is declared here > template <class T1, class T2> struct pair; > ^ > src/files.cpp:257:14: error: too few template arguments for class template 'vector' > std::vector<mapped_file_section> mapped_sections; > ^ > ../../boost/detail/container_fwd.hpp:135:47: note: template is declared here > template <class T, class Allocator> class vector; > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > src/files.cpp:287:18: error: too few template arguments for class template 'vector' > std::vector<mapped_file_section>::const_iterator section, > ^ > ../../boost/detail/container_fwd.hpp:135:47: note: template is declared here > template <class T, class Allocator> class vector; > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > src/files.cpp:348:14: error: too few template arguments for class template 'vector' > std::vector<mapped_file_section>::const_iterator find_section( > ^ > ../../boost/detail/container_fwd.hpp:135:47: note: template is declared here > template <class T, class Allocator> class vector; > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > src/files.cpp:269:39: error: cannot initialize object parameter of type 'const quickbook::file' with an expression of type 'quickbook::mapped_file' > original_pos, source().size(), > ^~~~~~ > src/files.cpp:276:51: error: cannot initialize object parameter of type 'const quickbook::file' with an expression of type 'quickbook::mapped_file' > pos - original->source().begin(), source().size())); > ^~~~~~ > src/files.cpp:282:51: error: cannot initialize object parameter of type 'const quickbook::file' with an expression of type 'quickbook::mapped_file' > pos - original->source().begin(), source().size(), > ^~~~~~ > src/files.cpp:351:18: error: too few template arguments for class template 'vector' > std::vector<mapped_file_section>::const_iterator section = > ^ > ../../boost/detail/container_fwd.hpp:135:47: note: template is declared here > template <class T, class Allocator> class vector; > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > src/files.cpp:375:14: error: too few template arguments for class template 'list' > std::list<mapped_file> mapped_files; > ^ > ../../boost/detail/container_fwd.hpp:134:47: note: template is declared here > template <class T, class Allocator> class list; > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > src/files.cpp:401:18: error: no viable conversion from 'intrusive_ptr<struct quickbook::mapped_file>' to 'intrusive_ptr<struct quickbook::file>' > file_ptr r = data->new_file; > ^ ~~~~~~~~~~~~~~ > ../../boost/smart_ptr/intrusive_ptr.hpp:66:5: note: candidate constructor not viable: no known conversion from 'boost::intrusive_ptr<mapped_file>' to 'quickbook::file *' for 1st argument > intrusive_ptr( T * p, bool add_ref = true ): px( p ) > ^ > ../../boost/smart_ptr/intrusive_ptr.hpp:90:5: note: candidate constructor not viable: no known conversion from 'boost::intrusive_ptr<mapped_file>' to 'const boost::intrusive_ptr<quickbook::file> &' for 1st argument > intrusive_ptr(intrusive_ptr const & rhs): px( rhs.px ) > ^ > ../../boost/smart_ptr/intrusive_ptr.hpp:76:5: note: candidate template ignored: substitution failure [with U = quickbook::mapped_file]: no type named 'type' in 'boost::detail::sp_enable_if_convertible<quickbook::mapped_file, quickbook::file>' > intrusive_ptr( intrusive_ptr<U> const & rhs, typename boost::detail::sp_enable_if_convertible<U,T>::type = boost::detail::sp_empty() ) > ^ ~~~~ > ../../boost/smart_ptr/detail/operator_bool.hpp:52:5: note: candidate function > operator unspecified_bool_type() const BOOST_NOEXCEPT > ^ > src/files.cpp:413:16: error: cannot initialize object parameter of type 'const quickbook::file' with an expression of type 'quickbook::mapped_file' > return data->new_file->source().empty(); > ^~~~~~~~~~~~~~ > src/files.cpp:418:16: error: cannot initialize object parameter of type 'const quickbook::file' with an expression of type 'quickbook::mapped_file' > return data->new_file->source().size(); > ^~~~~~~~~~~~~~ > src/files.cpp:447:18: error: too few template arguments for class template 'vector' > std::vector<mapped_file_section>::const_iterator start = > ^ > ../../boost/detail/container_fwd.hpp:135:47: note: template is declared here > template <class T, class Allocator> class vector; > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > src/files.cpp:457:20: error: reference to non-static member function must be called > for (++start; start != x.data->new_file->mapped_sections.end() && > ^~~~~ > src/files.cpp:458:21: error: reference to non-static member function must be called > start->our_pos < end; ++start) > ^~~~~ > src/files.cpp:458:45: error: reference to non-static member function must be called > start->our_pos < end; ++start) > ^~~~~ > src/files.cpp:461:21: error: reference to non-static member function must be called > start->original_pos, start->our_pos - begin + size, > ^~~~~ > In file included from src/files.cpp:12: > In file included from ../../boost/unordered_map.hpp:17: > ../../boost/unordered/unordered_map.hpp:295:35: error: implicit instantiation of undefined template 'std::pair<boost::unordered::iterator_detail::iterator<boost::unordered::detail::ptr_node<std::__1::pair<const boost::filesystem::path, boost::intrusive_ptr<quickbook::file> > > >, bool>' > std::pair<iterator, bool> emplace( > ^ > src/files.cpp:129:47: note: in instantiation of function template specialization 'boost::unordered::unordered_map<boost::filesystem::path, boost::intrusive_ptr<quickbook::file>, boost::hash<boost::filesystem::path>, std::__1::equal_to<boost::filesystem::path>, std::__1::allocator<std::__1::pair<const boost::filesystem::path, boost::intrusive_ptr<quickbook::file> > > >::emplace<boost::filesystem::path, quickbook::file *>' requested here > boost::tie(pos, inserted) = files.emplace( > ^ > ../../boost/detail/container_fwd.hpp:145:42: note: template is declared here > template <class T1, class T2> struct pair; > ^ > In file included from src/files.cpp:12: > In file included from ../../boost/unordered_map.hpp:17: > ../../boost/unordered/unordered_map.hpp:299:20: error: no viable conversion from 'emplace_return' (aka 'pair<iterator, bool>') to 'std::pair<iterator, bool>' > return table_.emplace( > ^~~~~~~~~~~~~~~ > fatal error: too many errors emitted, stopping now [-ferror-limit=] > 20 errors generated. > > "g++" -ftemplate-depth-300 -O3 -finline-functions -Wno-inline -Wall -gdwarf-2 -fexceptions -g0 -DBOOST_ALL_NO_LIB=1 -DBOOST_DETAIL_CONTAINER_FWD -DBOOST_FILESYSTEM_NO_DEPRECATED -DBOOST_FILESYSTEM_STATIC_LINK=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -I"../.." -c -o "../../bin.v2/tools/quickbook/src/darwin-4.2.1/release/link-static/files.o" "src/files.cpp" > > ...failed darwin.compile.c++ ../../bin.v2/tools/quickbook/src/darwin-4.2.1/release/link-static/files.o... > darwin.compile.c++ ../../bin.v2/tools/quickbook/src/darwin-4.2.1/release/link-static/id_generation.o > src/id_generation.cpp:29:18: error: too few template arguments for class template 'vector' > typedef std::vector<id_placeholder const*> placeholder_index; > ^ > ../../boost/detail/container_fwd.hpp:135:47: note: template is declared here > template <class T, class Allocator> class vector; > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > src/id_generation.cpp:33:13: error: expected a class or namespace > placeholder_index::iterator, placeholder_index::iterator, > ^ > src/id_generation.cpp:33:42: error: expected a class or namespace > placeholder_index::iterator, placeholder_index::iterator, > ^ > src/id_generation.cpp:34:18: error: too few template arguments for class template 'vector' > std::vector<std::string>& generated_ids); > ^ > ../../boost/detail/container_fwd.hpp:135:47: note: template is declared here > template <class T, class Allocator> class vector; > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > src/id_generation.cpp:36:10: error: too few template arguments for class template 'vector' > std::vector<std::string> generate_ids(document_state_impl const& state, boost::string_ref xml) > ^ > ../../boost/detail/container_fwd.hpp:135:47: note: template is declared here > template <class T, class Allocator> class vector; > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > src/id_generation.cpp:38:14: error: too few template arguments for class template 'vector' > std::vector<std::string> generated_ids(state.placeholders.size()); > ^ > ../../boost/detail/container_fwd.hpp:135:47: note: template is declared here > template <class T, class Allocator> class vector; > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > src/id_generation.cpp:44:22: error: too few template arguments for class template 'vector' > typedef std::vector<id_placeholder const*>::iterator iterator; > ^ > ../../boost/detail/container_fwd.hpp:135:47: note: template is declared here > template <class T, class Allocator> class vector; > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > src/id_generation.cpp:45:35: error: member reference base type 'placeholder_index' (aka 'int') is not a structure or union > iterator it = placeholders.begin(), end = placeholders.end(); > ~~~~~~~~~~~~^~~~~~ > src/id_generation.cpp:45:63: error: member reference base type 'placeholder_index' (aka 'int') is not a structure or union > iterator it = placeholders.begin(), end = placeholders.end(); > ~~~~~~~~~~~~^~~~ > src/id_generation.cpp:55:41: error: indirection requires pointer operand ('iterator' (aka 'int') invalid) > while (group_end != end && (*group_end)->num_dots == (*it)->num_dots) > ^~~~~~~~~~ > src/id_generation.cpp:55:67: error: indirection requires pointer operand ('iterator' (aka 'int') invalid) > while (group_end != end && (*group_end)->num_dots == (*it)->num_dots) > ^~~ > src/id_generation.cpp:74:14: error: too few template arguments for class template 'vector' > std::vector<unsigned>& order; > ^ > ../../boost/detail/container_fwd.hpp:135:47: note: template is declared here > template <class T, class Allocator> class vector; > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > src/id_generation.cpp:76:34: error: too few template arguments for class template 'vector' > placeholder_compare(std::vector<unsigned>& order) : order(order) {} > ^ > ../../boost/detail/container_fwd.hpp:135:47: note: template is declared here > template <class T, class Allocator> class vector; > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > src/id_generation.cpp:95:14: error: too few template arguments for class template 'vector' > std::vector<unsigned>& order; > ^ > ../../boost/detail/container_fwd.hpp:135:47: note: template is declared here > template <class T, class Allocator> class vector; > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > src/id_generation.cpp:99:22: error: too few template arguments for class template 'vector' > std::vector<unsigned>& order) > ^ > ../../boost/detail/container_fwd.hpp:135:47: note: template is declared here > template <class T, class Allocator> class vector; > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > src/id_generation.cpp:124:14: error: too few template arguments for class template 'vector' > std::vector<unsigned> order(state.placeholders.size()); > ^ > ../../boost/detail/container_fwd.hpp:135:47: note: template is declared here > template <class T, class Allocator> class vector; > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > src/id_generation.cpp:128:30: error: non-const lvalue reference to type 'quickbook::xml_processor::callback' cannot bind to a value of unrelated type 'quickbook::get_placeholder_order_callback' > processor.parse(xml, callback); > ^~~~~~~~ > src/document_state_impl.hpp:143:48: note: passing argument to parameter here > void parse(boost::string_ref, callback&); > ^ > src/id_generation.cpp:131:28: error: member reference base type 'placeholder_index' (aka 'int') is not a structure or union > sorted_placeholders.reserve(state.placeholders.size()); > ~~~~~~~~~~~~~~~~~~~^~~~~~~~ > src/id_generation.cpp:133:52: error: member reference base type 'placeholder_index' (aka 'int') is not a structure or union > if (order[p.index]) sorted_placeholders.push_back(&p); > ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~ > fatal error: too many errors emitted, stopping now [-ferror-limit=] > 20 errors generated. > > "g++" -ftemplate-depth-300 -O3 -finline-functions -Wno-inline -Wall -gdwarf-2 -fexceptions -g0 -DBOOST_ALL_NO_LIB=1 -DBOOST_DETAIL_CONTAINER_FWD -DBOOST_FILESYSTEM_NO_DEPRECATED -DBOOST_FILESYSTEM_STATIC_LINK=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -I"../.." -c -o "../../bin.v2/tools/quickbook/src/darwin-4.2.1/release/link-static/id_generation.o" "src/id_generation.cpp" > > ...failed darwin.compile.c++ ../../bin.v2/tools/quickbook/src/darwin-4.2.1/release/link-static/id_generation.o... > ...skipped <p../../bin.v2/tools/quickbook/src/darwin-4.2.1/release/link-static>quickbook for lack of <p../../bin.v2/tools/quickbook/src/darwin-4.2.1/release/link-static>files.o... > ...skipped <p../../dist/bin>quickbook for lack of <p../../bin.v2/tools/quickbook/src/darwin-4.2.1/release/link-static>quickbook... > ...failed updating 2 targets... > ...skipped 2 targets... > ...updated 2 targets... compiler: > tim@moka-mac:~/dev/boost/tools/quickbook$ g++ -v > Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 > Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) > Target: x86_64-apple-darwin13.0.0 > Thread model: posix is this a known issue? thanks, tim

4 5

[regex] diagnosis and fix for #9544
by Peter A. Bigot 05 Jan '14

05 Jan '14

Trac rejected my comment because it has links in it, so here's the relevant information. This issue arose as of [http://gcc.gnu.org/viewcvs/gcc?view=revision&revision=197248 GCC SVN commit 197248] which implements [http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3582.html N3582]. It occurs because the [http://gcc.gnu.org/viewcvs/gcc/trunk/gcc/cp/parser.c?r1=197248&r2=197247&pa… change on line 4109] preserves parentheses at the front end (with that change reverted, gcc works correctly). This is now [http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59681 PR C++/59681]. The fix in GCC is not trivial, so I've just made [https://github.com/boostorg/regex/pull/1 pull #1] so the trivial fix for boost (remove the parens) can be applied.

1 0

Request for comments on super-project workflow doc
by Beman Dawes 04 Jan '14

04 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 Comments welcome! Thanks, --Beman

6 11

Removing _1 from the global namespace (again)
by Peter Dimov 04 Jan '14

04 Jan '14

If we're going to call the next release 2.0, we'll be allowed some latitude with respect to breaking changes, so maybe this is the right time to finally remove the Bind placeholders from the global namespace. This will, however, break many things all around Boost (to say nothing about the outside world), as a quick grep can readily reveal. And, consequently, it will generate a certain amount of work for the maintainers of the affected libraries that, from their point of view, can appear unnecessary. So I'll need a certain amount of community consensus before going ahead and breaking everyone's code. :-)

14 15

[git] How to create a new submodule from existing submodule components?
by Beman Dawes 04 Jan '14

04 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 the Proposed assert submodule and Super-project workflow on their threads. Thanks, --Beman

3 5

[git-help] Doc. Suggestion: How to setup a custom boost "distribution"
by Klaim - Joël Lamotte 04 Jan '14

04 Jan '14

This is a suggestion for documentation, that "could" not be a good idea, I'm not totally sure. The goal would be to provide a simple recipe to setup a boost super-repo fork that would contain only a specific set of libraries, chosen by the user. I believe it would be of interest to a lot of companies that consider using boost but don't want to have to use the whole package. As Ryppl isn't ready yet, I was thinking that just providing a way to do it using the fork would already be helpful. It would also allow some people to provide a well tested custom distribution that would be easy to keep up to date. I expect people to experiment such things (I think I will at some point). The goal is NOT to resolve dependencies, or detect dependencies issues. It would be only to show that you can strip down the count of libraries if you wish in your own fork. The user will have to deal with dependency issues on his own, which is ok in a lot of cases, I assume. However, I'm not a specialist and I will not have time to try my idea immediately so I would like to ask if the following process is enough to do achieve the goal: 1. fork boost super-repo (clone locally, clone on your own server, or use the github fork button); 1.1. optionally, switch to a company or project-specific branch name; 2. in the fork, to remove libraries you don't want: 2.1. go in the root directory and edit the '.gitmodules' file 2.2. in this file, you will see each library module defined as follow: [submodule "any-library"] path = libs/any-library url = ../any-library.git fetchRecurseSubmodules = on-demand 2.3. locate and remove these declarations of each library you want to remove from the fork. 2.4. save the file. 3. commit the change 4. [git pull ?] 5. compile boost as usual. I'm not sure about the 4th point, but I think an operation is necessary so that git removes the library directories in the local clone. If these instructions are correct (once 4 is confirmed) and complete and are considered useful, maybe putting them somewhere in the doc would be worthwhile. Thoughts?

3 3

[git] mode and whitespace changes remaining between develop and master
by Nathan Ridge 04 Jan '14

04 Jan '14

Hello, I am trying to follow the instructions for "Establishing a merge point after SVN Conversion" [1] for the Boost.Range library. After cherry-picking all the commits to develop that have not been merged to master, onto master (all locally, I have not pushed anything yet), I am finding that there are still some mode and whitespace differences between master and develop (see the diff at the bottom of the message). I cannot find the commits that are responsible for these changes - is it safe to just ignore them? Thanks, Nate [1] https://svn.boost.org/trac/boost/wiki/PostCvtMergePoint diff --git a/include/boost/range.hpp b/include/boost/range.hpp old mode 100755 new mode 100644 diff --git a/include/boost/range/adaptor/strided.hpp b/include/boost/range/adaptor/strided.hpp old mode 100644 new mode 100755 diff --git a/include/boost/range/adaptor/transformed.hpp b/include/boost/range/adaptor/transformed.hpp old mode 100644 new mode 100755 diff --git a/include/boost/range/algorithm_ext/is_sorted.hpp b/include/boost/range/algorithm_ext/is_sorted.hpp old mode 100644 new mode 100755 diff --git a/include/boost/range/detail/demote_iterator_traversal_tag.hpp b/include/boost/range/detail/demote_iterator_traversal_tag.hpp old mode 100644 new mode 100755 diff --git a/include/boost/range/detail/implementation_help.hpp b/include/boost/range/detail/implementation_help.hpp old mode 100644 new mode 100755 index 1f7d163..ca12fa4 --- a/include/boost/range/detail/implementation_help.hpp +++ b/include/boost/range/detail/implementation_help.hpp @@ -21,13 +21,13 @@ #include <wchar.h> #endif -namespace boost +namespace boost { namespace range_detail { template <typename T> inline void boost_range_silence_warning( const T& ) { } - + ///////////////////////////////////////////////////////////////////// // end() help ///////////////////////////////////////////////////////////////////// @@ -36,7 +36,7 @@ namespace boost { return s + strlen( s ); } - + #ifndef BOOST_NO_CWCHAR inline const wchar_t* str_end( const wchar_t* s, const wchar_t* ) { @@ -51,7 +51,7 @@ namespace boost ; return s; } -#endif +#endif template< class Char> inline Char* str_end( Char* s ) @@ -64,7 +64,7 @@ namespace boost { return boost_range_array + sz; } - + template< class T, std::size_t sz> inline const T* array_end( const T BOOST_RANGE_ARRAY_REF()[sz] ) { @@ -74,7 +74,7 @@ namespace boost ///////////////////////////////////////////////////////////////////// // size() help ///////////////////////////////////////////////////////////////////// - + template< class Char> inline std::size_t str_size( const Char* const& s ) { @@ -96,7 +96,7 @@ namespace boost } } // namespace 'range_detail' - + } // namespace 'boost' diff --git a/include/boost/range/iterator.hpp b/include/boost/range/iterator.hpp index 4ba9122..2966bdf 100644 --- a/include/boost/range/iterator.hpp +++ b/include/boost/range/iterator.hpp @@ -25,46 +25,46 @@ namespace boost { -#if BOOST_WORKAROUND(BOOST_MSVC, == 1310) - - namespace range_detail_vc7_1 - { - template< typename C, typename Sig = void(C)> - struct range_iterator - { - typedef BOOST_RANGE_DEDUCED_TYPENAME - mpl::eval_if_c< is_const<C>::value, - range_const_iterator< typename remove_const<C>::type>, - range_mutable_iterator<C>>::type type; - }; +#if BOOST_WORKAROUND(BOOST_MSVC, == 1310) - template< typename C, typename T> - struct range_iterator< C, void(T[])> - { - typedef T* type; - }; - } - -#endif + namespace range_detail_vc7_1 + { + template< typename C, typename Sig = void(C)> + struct range_iterator + { + typedef BOOST_RANGE_DEDUCED_TYPENAME + mpl::eval_if_c< is_const<C>::value, + range_const_iterator< typename remove_const<C>::type>, + range_mutable_iterator<C>>::type type; + }; + + template< typename C, typename T> + struct range_iterator< C, void(T[])> + { + typedef T* type; + }; + } + +#endif template< typename C> struct range_iterator { #if BOOST_WORKAROUND(BOOST_MSVC, == 1310) + + typedef BOOST_RANGE_DEDUCED_TYPENAME + range_detail_vc7_1::range_iterator<C>::type type; + +#else - typedef BOOST_RANGE_DEDUCED_TYPENAME - range_detail_vc7_1::range_iterator<C>::type type; - -#else - - typedef BOOST_RANGE_DEDUCED_TYPENAME - mpl::eval_if_c< is_const<C>::value, + typedef BOOST_RANGE_DEDUCED_TYPENAME + mpl::eval_if_c< is_const<C>::value, range_const_iterator< typename remove_const<C>::type>, range_mutable_iterator<C>>::type type; - -#endif + +#endif }; - + } // namespace boost #endif

2 1

[MPL] true_type,false_type versus true_,false_
by Erik Erlandson 04 Jan '14

04 Jan '14

I've been using true_type and false_type in some of my interfaces, for example: https://github.com/erikerlandson/edit_distance/blob/master/include/boost/al… However it seems as though true_ and false_ are more compatible with MPL logic functions. Is there any particular reason to use one over the other? Would it be preferable to use true_ and false_?

2 1

[regression] OK to merge? Should tools/regression be a submodule?
by Beman Dawes 04 Jan '14

04 Jan '14

* The directory tools/regression/src/report was missing from svn branches/release, so it is also missing from modular boost master. Although I haven't checked, that probably means the are other unmerged changes in develop. OK to merge develop to master (after suitable testing?) * Should tools/regression be a submodule? Does anyone remember why it remains a part of the super-project? If we are going to convert tools/regression to a submodule, should we do it now or wait until the dust settles? --Beman

5 11

Re: [boost] [AFIO] Callback API
by Bjorn Reese 03 Jan '14

03 Jan '14

Moving the discussion from boost-users to boost-dev, and thus the full context is quoted. On 12/21/2013 01:53 AM, Niall Douglas wrote: > On 20 Dec 2013 at 19:16, Bjorn Reese wrote: > >>> Can you suggest something? I honestly can't think of anything simpler >>> which also provides strong write ordering guarantees. >> >> I have not given this much thought so consider the following a >> brainstorm. > > We really ought to move this off boost-users ... but we'll see how it > goes. > >> I am thinking about an API that uses handles that looks more like Asio >> sockets. Write ordering can be handled, not by batching operations >> together, but rather calling the next write operation from the callback >> of the previous operation (Asio-style.) This will not always yield good >> performance, but oftentimes that is less relevant. If you need >> performance, then the "advanced" dispatcher API is available. >> >> So there could be a file handle (and directory handle) class for file >> (directory) manipulation calls, which hides all the details of the >> dispatcher etc. >> >> class file_handle >> { >> public: >> void read(buffer, read_callback); >> void write(buffer, write_callback); >> // and so on >> }; >> >> class directory_handle >> { >> public: >> void create(name, create_callback); // uses file(single) or dir(single) >> void remove(name, remove_callback); // uses rmdir(single) >> void watch(name, watch_callback); // directory monitoring >> // and so on >> }; > > I'm struggling to see the merit in such an approach - it would be > incredibly verbose and complex to write even simple solutions, > because i/o on files is not like sockets, *especially* that you > almost never must strongly order i/o across a sequence of multiple > sockets, but that is a very common case with files e.g. during ACID. First, it follows a pattern that is familiar to Asio users. So rather than you being the only one who can write applications on top of Afio, you get a broader community who are already familiar with the callback approach. Second, you can more easily combine it with Asio socket code to create compound services that mixes socket and file access. For instance, a peer-to-peer file distribution mechanism. > AFIO tries to help users to not write callbacks except when > necessary, but if you do want a user defined callback you simply > chain a call() or completion() operation to the item whose completion > you want called back upon. > > The idea is, you see, that you subclass the async_io_dispatcher class > with additional completion handlers, and use those as building blocks > for further subclasses of async_io_dispatcher. That hopefully gets > people to break up their callbacks into reusable completion handlers, > and saves people writing and debugging code. > Before you say "this should be in the documentation", yes it should > and will be after Paul gets his directory monitoring implementation > working. I'm thinking that will form the fourth section in the > beginner's tutorial - how to modularise and make reusable the > normally bespoke glue code which makes up traditional callbacks. It > might actually be worth adding a section 3b which shows how the naïve > approach in 3a is a very stupid idea :) > > As much as this sort of operation dependency graph based design works > well for its niche, I agree there is a swathe of code which ends up > looking like the find in files implementation, and for that hopefully > fibers will make look much more sane. I am not arguing against the current API. Instead, I am arguing for the addition of a more familiar Asio-style callback API. I have no trouble with a fiber-enchanced API (similar to Asio with coroutines.)

3 5

[MSM] Additional template arguments for process_event
by Juan Carlos Franzoy 03 Jan '14

03 Jan '14

The short question is: Would it be possible/convenient that boost::msm::back::state_machine::process_event receive more template parameters? template< class Event, typename... ARGS > process_event( const Event& event, ARGS&&... args ); args been forwarded to transition actions? I've been searching in boost.development mailing list archives and didn't see this question before. The need of additional template parameters is based on the fact that ARGS may not be defined at the moment of the state_machine isntantiation. Note: I would love to notice that I am wrong, and all this is an unnecessary complication, please let me know if that is the case. Thanks for reading. The long story follows: I am trying to use MSM for the first time. I am evaluating the factibility and convenience of a library to try to make easier the construction of protocol stacks over Boost.Asio. Protocol stack layers are often Finite State Machines. The idea is that the user of the library would program reusable 'layers' and use a library facility called LayerLinker to links the layers. For example this is a simplified pseudocode: template< typename STACK, int POSITION > class LayerLinker { typedef ... layer_t; typedef LayerLinker<STACK,POSITION+1> upper_linker_t; typedef LayerLinker<STACK,POSITION-1> lower_linker_t; layer_t layer_; upper_linker_t *up_; lower_linker_t *low_; public: LayerLinker( boost::asio::io_service& ios ) : layer_{ios} {} template<class EVENT> void processUpstreamEvent( const EVENT& ev ) { layer_.processUpstreamEvent( *this /* let the layer know my type */, ev ); } // similar for processDownstreamEvent() // Called by layer_ to send an event to the upper layer template<class EVENT> void sendUpstreamEvent( const EVENT& ev ) { if ( up_ ) { up_->processUpstreamEvent( ev ); } } // similar for sendDownstreamEvent() }; struct MyTopLayer { typedef ... my_fsm_t; my_fsm_t myFsm_; public: template<class LINKER, class EVENT> void processUpstreamEvent( LINKER& linker, const EVENT& ev ) { // in transition actions the FSM can send events to upper layers. myFsm.process_event( ev, linker /* additional parameter here */ ); } // similar to processDownstreamEvent }; // similar for MyMiddleLayer and MyBottomLayer int main() { typedef boost::mpl::vector<MyTopLayer,MyMiddleLayer,MyBottomLayer> stack_t; boost::asio::io_service ios; LayerLinker<stack_t, 0> topLinker{ios}; LayerLinker<stack_t, 1> middleLinker{ios}; LayerLinker<stack_t, 2> bottomLinker{ios}; topLinker.setLowerLinker( middleLinker ); middleLinker.setUpperLinker( topLinker ); middleLinker.setLowerLinker( bottomLinker ); bottomLinker.setUpperLinker( middleLinker ); topLinker.processDownstreamEvent( InitEvent{} ); ios.run(); } // from asio callbacks borromLinker.processUpstreamEvent( ReadEvent{...} ); Although I could make it without extra parameters to process_event, it is basically a workaround. THANKS A LOT for reading 95 lines. Juan Carlos Franzoy

2 1

[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