- Boost - lists.boost.org

General advice needed for new maintainers.
by Fletcher, John P 14 Feb '14

14 Feb '14

I have been maintaining Boost Phoenix for several weeks. To start with I was mainly attempting to fix as many bugs as possible and also sorting out things like missing copright and licence. I am now up to the more difficult bugs which take longer to fix. I also need some more information and some actions which I cannot take myself. I have asked about a number of these on this list and I am lacking answers to a good many of them, so I am going to summarise them here. I think it would be a great help to people undertaking maintenance for the first time, without having first been an originator of a library if some guidelines were in a document. 1. General guidelines on the responsibilities of a maintainer and who is responsible for the elements outside the developer's control. In particular, what happens when there is a release of boost? 2. General guidelines on the responsibilities for bugs and who to contact if a bug seems to be due to a different library. 3. Guidelines on the use of trac and how to get given the ability to record bugs as now fixed. 4. Where is the archive for boost-bugs? It would be useful to look at past fixes to find out what has gone on. Someone suggested searching but I cannot search until I know what is there. 5. A list of who is maintaining what. 6. Documentation. I am trying to get to grips with boostbook and quickbook. Some libraries are included in a section with indexed chapters and some are not. Is there a policy about this. When I asked how Phoenix could join the only reply I had was not to bother. Is there a documentation policy? It would be good to be able to generate the web pages myself to check them when I am making changes, which may be substantial. 7. More technical. How are things to be handled in relation to C++11. (a) Things which used to work which now don't with C++11? (b) Things which only work with C++11? (c) and what about C++14? I am fixing things in an adhoc way but it would be good to have a uniform approach. 8. Boost predef for version numbers. I have introduced this into Phoenix alongside the existing method. 9. Changelog. As a user I have found this useful in libraries I have used elsewhere, so I have put one into Phoenix following the style I found in wave. There is quite a lot here, but it has been building up for some time as I find I need more information to work effectively. John Fletcher P.S. Thanks to all those who have helped me get this far.

3 3

Interested in working with Boost C++ Libraries
by Arpit Sharma 13 Feb '14

13 Feb '14

Hello, My name is Arpit Sharma. I'm a 3rd year Computer Science student. I'm very much interested to work for Boost C++ Libraries in Gsoc 2014 and would like to work after that also. Any pointers on how to proceed. -Thank you, Arpit Sharma

2 1

Contributing to Boost as a part of GSoC 2014
by Kamal Gurala 13 Feb '14

13 Feb '14

Hi All, My name is Kamal Gurala, I am currently pursuing a B.tech in CSE from IIIT-Hyderabad ( India ). I have a good knowledge of C++, Data Structures, and Algorithms. I want to get started with contributing towards Boost. I would be obliged if any one could help me in this regard. Regards, Kamal Gurala

2 1

[fusion.adapted.std_tuple] bug
by Hui Li 13 Feb '14

13 Feb '14

Looks like 2 files share the same include guard macro definitions. This makes it very hard to use Boost.Fusion for std::tuple's, especially if both boost::tuple and std::tuple need to be adapted. mbpro:fusion huil$ find . -type f |xargs grep -w BOOST_FUSION_CATEGORY_OF_IMPL_09272006_0726 ./adapted/boost_tuple/detail/category_of_impl.hpp:#if !defined(BOOST_FUSION_CATEGORY_OF_IMPL_09272006_0726) ./adapted/boost_tuple/detail/category_of_impl.hpp:#define BOOST_FUSION_CATEGORY_OF_IMPL_09272006_0726 ./adapted/std_tuple/detail/category_of_impl.hpp:#if !defined(BOOST_FUSION_CATEGORY_OF_IMPL_09272006_0726) ./adapted/std_tuple/detail/category_of_impl.hpp:#define BOOST_FUSION_CATEGORY_OF_IMPL_09272006_0726

2 1

How to add a library to the BoostBook Documentation Subset?
by Fletcher, John P 12 Feb '14

12 Feb '14

I have taken over the task of maintaining Boost Phoenix. I want to start expanding the documentation which already uses Quickbook. The BoostBook Documentation Subset here includes a lot of libraries but not Boost Phoenix. http://www.boost.org/doc/libs/1_55_0/doc/html/index.html How do I get Boost Phoenix added, and are there any requirements for the documentation which need to be observed? Thanks John Fletcher

2 1

Building a new boost library in Google summer program!
by Khaled Ammar 12 Feb '14

12 Feb '14

Hi everyone, I'm new to this list so please excuse my lack of experience. I'm interested to build a boost library as part of Google Summer of Code ( http://www.google-melange.com/gsoc/homepage/google/gsoc2014) Could you please advice me who should I contact? -- Thanks, -Khaled Ammar PhD student at Uwaterloo www.khaledammar.com

3 2

Warning.. Regression testing changes forthcoming..
by Rene Rivera 12 Feb '14

12 Feb '14

We, mostly Ahmed Charles, will be moving the regression and release script code to independent git repos (i.e. moving the out of the boost super-repo). The first step is to copy the git histories. This requires that NO ONE make changes to the regression and release code. This first step will happen tonight at 8-12 pm PST. Further actions for testers to take will follow in the next 2-3 days. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

1 0

Where is boost/detail/limits.hpp used?
by Peter Dimov 12 Feb '14

12 Feb '14

I'm playing with a dependency checker I wrote that tells me what Boost module depends on what. Starting with the basics: Dependencies for config: detail: boost/detail/endian.hpp A dependency from config to detail is not a good thing because detail depends on too much. boost/detail/endian.hpp is now only a forwarding header to predef, so it could and probably should be moved to predef, which seems to depend on nothing. But I was wondering what in config uses endian.hpp. Turns out the only use is in boost/detail/limits.hpp, a file that has been put into config for some reason. I can't find anything in config or in Boost that uses this file. What is its purpose?

5 11

[Boost-users] User/Owner Information And in Boost File System
by MANTOSH KUMAR 12 Feb '14

12 Feb '14

Hi All, Point::1 ====== boost::filesystem library is great. However I found that boost::filesystem has no interface to fetch about the owner(userid/groupid) of a particular file. "stat()" system call has been provided by POSIX compliance system to fetch this information. I am pretty sure that this must have been thought by boost community while designing boost::filesystem library and there would be valid reason not to provide such interface. However I just wanted to know the thought of boost community. Point::2 ====== The following is the code snippet: std::vector<boost::filesystem::path> vec; boost::filesystem::recursive_directory_iterator rbgnitr(p); boost::filesystem::recursive_directory_iterator renditr; for(boost::filesystem::recursive_directory_iterator itr = rbgnitr; itr != renditr; ++itr) { v.push_back(*itr); } In the above "rbgnitr" does represent the starting node in a directory. However It looked bit strange while "renditr" for end node(one beyond end). The end node renditr" is basically empty instance of class "recursive_directory_iterator"......Just wanted to know why this was designed in this way..... Thanks & Regards, Mantosh Kumar India

2 1

Boost.Log crash - question on consequences of misconfiguration
by Pieter 12 Feb '14

12 Feb '14

LS, My question regarding Boost.Log is the following: could anything been said on what to expect when asking Boost.Log to write to a non-existing directory on a read-only drive? Does it keep trying to write or give up when the directory cannot be created, and would the user be informed in such a case? Background: today I ran into a problem using Boost.Log. I configured both a Console and a TextFile backend (both autoflushing) but happened to configure the latter wrongly- setting the location of the file on a not-existing directory on a read-only drive. This caused a program crash under certain circumstances - but no problems under other circumstances (related to the configuration of the application which should not be relevant here) - when it did crash, this happened after a few messages were logged. Crash happened shortly before program termination but before the main() function was terminated (for a while I thought I was seeing the problem described in the docs regarding the boost.filesystem related problem and it took me a while to learn this was not the case). Pieter

2 1