- Boost - lists.preview.boost.org

[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