December 2013 - Boost - lists.preview.boost.org

[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