- Boost - lists.preview.boost.org

[filesystem] temp_directory_path() behavior on Windows
by Beman Dawes 20 Feb '15

20 Feb '15

temp_directory_path() on Windows is currently implemented by calling the Windows API GetTempPath() function. Ticket https://svn.boost.org/trac/boost/ticket/5300 points out that GetTempPath() does not work as expected for environmental variables longer than roughly 130 characters. I've added a test to Boost.Filesystem that verifies that boost::filesystem::temp_directory() is affected. The suggested fix is to use GetEnvironmentVariable to in effect implement GetTempPath() the way we would like it to work. That makes sense to me, so I looked up the specs for GetTempPath(): The GetTempPath function checks for the existence of environment variables in the following order and uses the first path found: 1. The path specified by the TMP environment variable. 2. The path specified by the TEMP environment variable. 3. The path specified by the USERPROFILE environment variable. 4. The Windows directory. (4) Makes me queasy. I suspect it will fail anyhow because of permissions errors, but I would prefer to have temp_directory_path() report an error if 1, 2, and 3 are not present. temp_directory_path() already reports an error if a path is found but it is not a directory. OTOH, excluding the Windows directory is a breaking change for anyone currently depending on that behavior, so I thought it best to ask for comments before charging ahead. Thoughts? --Beman

8 39

[log] custom architecture and address-model
by Vladimir Prus 19 Feb '15

19 Feb '15

Hi, it seems that Boost.Log defines, and checks, it's own log-address-model and log-architecture and log-instruction-set properties. Naturally, if I'm trying to make regular address-model and architecture properties always set, these are getting in the way. Do we really need per-library properties? If a user wants to build Boost.Log with a particular architecture, I would think he can do: ./b2 --with-log <whatever> If so, is everybody fine if I eliminate these custom features eventually? -- Vladimir Prus CodeSourcery / Mentor Embedded http://vladimirprus.com

3 6

[Review] Boost.Endian mini-review
by Joel FALCOU 19 Feb '15

19 Feb '15

The mini-review of Boost.Endian starts today and runs through Sunday, February 1. The library repository is available on GitHub at https://github.com/boostorg/endian The docs for the library can be viewed online at https://boostorg.github.io/endian/ The objective of the mini-review is to verify that the issues raised during the formal review have been addressed. Those issues are documented at https://boostorg.github.io/endian/mini_review_topics.html which also describes the resolution of each issue. Comments and suggestions unrelated to the mini-review issues are also welcome, but the key question the review manager needs your opinion on is this: Is the library ready to be added to Boost releases? -- Joel Falcou, Endian Review Manager

16 57

[endian] Post-mini-review status: endian ready to merge to master
by Beman Dawes 18 Feb '15

18 Feb '15

Here is a post-mini-review status report to support a pull request to merge endian into the boost super-project master branch as a submodule. (It has been a submodule of the super-project develop branch for months.) The mini-review ran from January 23rd through February 1st. There were over 50 messages posted in the main review thread ("[Review] Boost.Endian mini-review"). The key question Joel Falcou, the review manger, asked was: Is the library ready to be added to Boost releases? All seven responses to the question were "Yes" votes (Peter Dimov, Nevin Liber, Philip Bennefall, Jason Newton, Jeremy Maitin-Shepard, Cliff Green, Bjorn Reese), and none of these votes were conditional. Other things that came out of the mini-review discussion: * Major concern: The default alignment needs to revert to unaligned. There should be no problem completing this before the final 1.58.0 release, and probably before the beta, but I need to carve out a quiet couple of hours to review the discussions before actually doing the revert. * Major concern: Floating point support needs an additional test program tailored to the characteristics of floating point numbers. A warning needs to be added to the docs alerting users that FP support is much less mature than integer support. The plan is to create the new test program in the next few days, and ask on the list for contributions of test cases from FP experts. * Requests for new features: A couple of simple to analyze and implement features have already been added. Other possible new features were added to a "Future directions" section of the docs so they won't be forgotten. * Technical fixes and suggestions. Most of these have already been applied. * Documentation fixes and suggestions. Most of these have already been applied, with three or four docs change emails still to be processed. Today is the cut off for 1.58.0 new libraries, so I'm planning to submit pull requests to merge endian submodule support from the boost super-project's develop branch into its master branch. (endian submodule support has been in the boost super-project's develop branch for months.) Thanks to all of those who contributed to the mini-review! --Beman

1 0

[GSoC] interested in implementing numerical algorithms for uBLAS
by Ganesh Prasad 17 Feb '15

17 Feb '15

Hi I am interested in implementing numerical algorithms optimized for distributed/parallel architectures for Boost.uBLAS. I have been applying for this project for previous 2 years, so I have definitely done some research in this field. Also, I have been working on Clusters for last 7 months as an Academic project (Product Development). So, basically I am acquainted with programming for distributed architectures with MPI. best wishes Ganesh Prasad

2 1

[threads] Win32 Events on POSIX
by Fu ji 17 Feb '15

17 Feb '15

Hello, I want to port win32 events on Posix using Boost. To avoid the re-invented the wheel I use PEvents: https://github.com/neosmart/pevents which is on MIT licence. But with my current knowledge I do some mistakes because I have deadlock. Maybe someone with bigger knowledge about differencies in boost and pevents might help with this ? I know that there is also thread-safe boost.signals2 with observer pattern but it does not provide WaitForMultipleObjects functionality. Best regards.

5 16

[nowide] Bug fix for older Windows versions
by Michael Smith 17 Feb '15

17 Feb '15

I found an issue with the implementation of cout/cerr in Boost.Nowide. It will fail in the middle of writing output due to a segfault in VerifyConsoleIoHandle (during WriteConsoleW). See the attached files for a patch and example (I've tested with MinGW-w64 4.8.3).

1 0

Fwd: Boost.Fixed_Point for GSoC 2015?
by Nikhar Agrawal 17 Feb '15

17 Feb '15

Hi everyone, I'm Nikhar Agrawal, currently an undergraduate student at IIIT-Hyderabad pursuing a degree in Computer Science and Engineering. I have been a succesful GSoC participant twice in a row. In 2013, I did GSoC under Boost C++ libraries under the mentorship of Christopher Kormanyos with continuous guidance from John Maddock and Paul Bristow. In 2014, I did GSoC under GNOME. In 2014, I had also submitted a proposal for Boost.Fixed_Point. Here's the link to the proposal I submitted last year: https://docs.google.com/document/d/1Ylc_OJBpoN_lNgMrYh0l-O_qCb-EDJQy0JGoh5u… Unfortunately, the project couldn't go through because of lack of slots. I would like to try again this year. Christopher isn't available as a mentor though. Chris and Niall suggested that I float a mail through the mailing list to see if there are any takers for this project who'd be willing to mentor it. The proposal hasn't changed much from what I submitted last year. We may have to limit it's scope to something that'd be ideal for one summer though. I'll be more than happy to discuss it with anyone who's interested in the project. Thanks. Nikhar P.S.: I'm attaching some mails from the conversation I've had with Niall and Christopher in this regard. ---------- Forwarded message ---------- From: Niall Douglas <s_sourceforge(a)nedprod.com> Date: Wed, Feb 11, 2015 at 8:12 AM Subject: Re: Boost.Fixed_Point for GSoC 2015? To: nikharagrawal2006(a)gmail.com Cc: Christopher Kormanyos <e_float(a)yahoo.com> Nikhar, Firstly my commendation to you on keeping up interest after not getting a place last year. For your information, we requested 12 slots and received just 7, and after I begged Google for another we got eight for 2014. That meant four projects did not get funding, and yours was one. Can I suggest that you perhaps consider approaching potential mentors in Boost and see if you can find one interested? Please do CC my email in your approaches so they know I have vetted you, and mention you were a successful student in 2013. Given that Chris won't be available this year, you may need to consider not doing fixed point as I am unaware of a suitable alternative mentor who is available. When approaching potential mentors, try to suggest ideas that are something the mentor badly wants in their particular specialism. Try searching the mailing lists and past GSoC ideas to see which mentors might have which pet projects which get them enthusiastic. Just this week a student called Damian Vicino managed to persuade Robert Ramey to mentor work on safe_numerics. I did not know Robert had an interest in this, but Damian obviously figured it out and won a mentor. Good luck in your efforts. Niall On 10 Feb 2015 at 21:24, Christopher Kormanyos wrote: > Hi Niall, > I will not be available as a GSoC mentor this year. > Just a heads-up, Nikhar Agrawal, a successful veteranGSoC candidate, has expressed interest in thefixed-point project. > I do not know if anyone would like to mentor it. > > See text below. > Thank you for your continued support. > Best regards, Chris > > > It seems that the discussions for GSoC 2015 have begun> on the mailing list. > > The fixed point project couldn't make through last year.> Is there interest in it for this year from you guys?> Would you like me to post about it on the mailing list?> I'm still very much interested in this. I contacted about this> project a couple of times last year after the summers> but everyone was busy with other stuff. And I think the> GSoC deadlines provide a lot of motivation anyways. > So let me know what you guys think about it and> if I should apply for the project. > Cheers. :)> Nikhar > Hi Nikhar, > Thank you for keeping in touch. > I will not be available as a GSoC mentor this year.In my opinion, the fixed-point project is a good one.We just need to find a mentor for the project. > The fixed-point project needs to have a clearly definedscope. The preliminary specification suggested byLawrence Crowl represents man-years of coding effort. > > If there is a way to limit the scope of the project toa reasonable level for one summer and find a mentor,then go for it ! > Please post any suggestions and or comments or questionson the board. > You were a very successful participant in GSoC 2013.With help from John and Paul, the ground work you did hasbeen included in Boost. We now have Bernoulli, high-precisiontgamma(), and also polygamma() for integer order. > > Boost is a long-term endeavor. I encourage you to stickwith it --- and keep up the good work ! > Good luck. > > Cheers, Chris > > > On Tuesday, February 10, 2015 4:29 PM, Nikhar Agrawal < nikharagrawal2006(a)gmail.com> wrote: > > > Hi everyone, > How are you all doing? > > It seems that the discussions for GSoC 2015 have begun on the mailing list. > The fixed point project couldn't make through last year. Is there interest in it for this year from you guys? Would you like me to post about it on the mailing list? I'm still very much interested in this. I contacted about this project a couple of times last year after the summers but everyone was busy with other stuff. And I think the GSoC deadlines provide a lot of motivation anyways. > So let me know what you guys think about it and if I should apply for the project. > Cheers. :)Nikhar > > On Tue, Apr 22, 2014 at 1:25 AM, Nikhar Agrawal < nikharagrawal2006(a)gmail.com> wrote: > > Hi all, > GSoC results are out and unfortunately, the fixed-point project didn't go through. However, the last couple of months or so, having invested time in discussing various design issues and going through various code prototypes, I have become really interested in developing a fixed-point library. And I stick to my word of being willing to develop library outside of GSoC as well. It would be great to have your continued guidance. Though with GSoC in summer, I wonder you'd have your official projects as first priority. I had submitted another proposal to GNOME and I got into GSoC via that as well. > So, I was wondering what could be a good way forward? How I could contribute to fixed-point library? The first question is if there's an interest in the library still from all your sides as well now that it's not an official GSoC project? If yes, I guess we could continue our collaborations just like they happened during last GSoC? Though probably less frequently? What do you guys think? > Also, if it's not an inappropriate thing to ask, could you kindly elaborate why the project didn't go through? Seeing the comments of everyone involved, I had a feeling that proposal was very well received. > Thanks.Nikhar > > > > > > > > --- Boost C++ Libraries Google Summer of Code 2015 admin https://svn.boost.org/trac/boost/wiki/SoC2015

1 0

Interested in choosing a Boost C++ project for GSOC 2015
by Prasad Priyadarshana Fernando 17 Feb '15

17 Feb '15

Hi, I am interested in choosing a Boost C++ project for GSOC 2015. Can anbody kindly let me know what are the projects you have for this years GSOC and How to interact with those projects to do bug fixes and to get familiar with the existing code bases. Thanks *Prasad Priyadarshana Fernando <http://www.linkedin.com/in/prasadfernando>* Mobile: +1 330 283 5827

3 7

GSOC 2015 Applicant
by Muhammad Junaid Muzammil 17 Feb '15

17 Feb '15

Hello, I am Muhammad Junaid Muzammil interested in extending the PRNG support primarily for the Boost Compute library as a GSOC project. In this regard, the basic aim is to add the support of stateless counter based PRNG to the library. Different families of RNG from Random123, including Threefry, Philox and ARS will be incorporated in the library. Potential mentor for this particular project could be Kyle Lutz. Thanks, Junaid.

3 4

[gsoc15] Org application closes on Friday 20th
by Niall Douglas 17 Feb '15

17 Feb '15

Three days remain until the GSoC org application closes on Friday 20th of April. As can be seen at https://svn.boost.org/trac/boost/wiki/SoC2015, we have just SIX project proposals and FIVE mentors who have publicly made themselves available on the ideas list this year. This is significantly lower than this time last year. If you would like to attract students to work on your Boost library in 2015, please consider adding a formal project idea to the list above before Friday. If you would like to mentor in some topic or field, please make yourself known to us so we can add you to the list of available mentors for 2015. Oh, and don't forget to mention the fields you are interested in! Thanks, Niall and Boris --- Boost C++ Libraries Google Summer of Code 2015 admin https://svn.boost.org/trac/boost/wiki/SoC2015

1 0

[config] clang on Windows and BOOST_SYMBOL_EXPORT problem
by Edward Diener 15 Feb '15

15 Feb '15

I have been recently discussing a problem regarding clang on Windows on the clang developers mailing list, but without any final resolution yet. This problem affects those using clang on Windows with Boost along with exported classes. This combination occurs when testing Boost.Test but I imagine also occurs with other Boost libraries and of course could affect Boost end-users using clang on Windows. The problem does not occur with clang on Linux for reasons which shall be understood in the explanation. The bug manifests itself in such code, compiled with clang, as: #include <boost/config.hpp> #include <boost/scoped_ptr.hpp> class BOOST_SYMBOL_EXPORT AClass { boost::scoped_ptr<int> sp_pointer; }; int main() { return 0; } On Windows for clang the BOOST_SYMBOL_EXPORT becomes __declspec(dllexport) whereas on Linux it becomes __attribute__((__visibility__("default"))). Clang decides with __declspec(dllexport) or its equivalent __attribute__((dllexport)), but not with __attribute__((__visibility__("default"))), that after generating a default copy constructor and assignment operator for a class which has not defined is own, even if an object of that class is never copied or assigned, if the default copy constructor or assignment operator is invalid the compilation is in error. Since the above class has a member which is non-copyable and non-assignable we get errors from clang along the lines of: > test_clang_bug.cpp:3:1: error: field of type 'boost::scoped_ptr<int>' has private copy constructor > AClass { boost::scoped_ptr<int> sp_pointer; }; > ^ > ..\..\..\boost/smart_ptr/scoped_ptr.hpp:47:5: note: declared private here > scoped_ptr(scoped_ptr const &); > ^ > test_clang_bug.cpp:3:1: note: implicit copy constructor for 'AClass' first required here > AClass { boost::scoped_ptr<int> sp_pointer; }; > ^ > test_clang_bug.cpp:3:1: error: 'operator=' is a private member of 'boost::scoped_ptr<int>' > AClass { boost::scoped_ptr<int> sp_pointer; }; > ^ > ..\..\..\boost/smart_ptr/scoped_ptr.hpp:48:18: note: declared private here > scoped_ptr & operator=(scoped_ptr const &); > ^ > test_clang_bug.cpp:3:1: note: implicit copy assignment operator for 'AClass' first required here > AClass { boost::scoped_ptr<int> sp_pointer; }; > ^ > 2 errors generated. I have argued on the clang developers list that requiring C++ programmers to provide a default copy constructor for a class whose object is never meant to be copied or a default assignment operator for a class which is never meant to be assigned, even if that means private declarations in C++03 or deleted declarations in C++11, can never be a good idea and goes against the C++ standard. The clang answer has been that exporting classes is outside the C++ standard so the C++ standard rules do not apply in this case. Note again that having BOOST_SYMBOL_EXPORT become __attribute__((__visibility__("default"))) for clang on Windows targeting mingw/gcc fixes this problem for that compilation environment. In fact for gcc using mingw/gcc we do indeed use __attribute__((__visibility__("default"))) and that works fine with mingw/gcc in the exact same exporting situations. Similarly for VC++ compilation having BOOST_SYMBOL_EXPORT be __declspec(dllexport) works fine also. I have not yet been able to get from clang developer why exporting a class using __declspec(dllexport) or its equivalent __attribute__((dllexport)) works the way it does, but using __attribute__((__visibility__("default"))) gives no problems. The discussion still appears to be ongoing. Do we want to change BOOST_SYMBOL_EXPORT on clang with Windows targeting mingw/gcc to specify __attribute__((__visibility__("default"))) as we do with mingw/gcc ? It is a fairly simple change which I can make. I just wanted to bring this whole issue to the attention of Boost before I implement any change. I am of course still hoping tha clang changes the way it views the exporting situation and still think they are wrong.

2 5

[GSOC] Devector project
by Divyansh Gupta 15 Feb '15

15 Feb '15

Hi all, I've been following the mailing list for a few months and I wanted to know more about the Devector project idea that was being discussed last week. I couldn't find it on the 2015 ideas page so I read about it on the 2009 page and I'm really interested in doing it as a GSOC project. So then I also read the segmented iterators paper and the std::vector and std::deque references. I found an existing implementation of devector on GitHub ( https://github.com/orlp/devector/blob/master/readme.md) Some of the shortcomings of this implementation as per the 2009 ideas page: 1. Does not provide reference stability on insertion since it's just one continuous block of memory which has to be reallocated in its entirety. 2. Hence obviously does not provide option for setting chunk size or use segmented iterators. I was hoping that the devector idea is added to the 2015 ideas page with a competency test since I don't have any open source contributions besides the research projects in my institute. But I'm a quick learner and am confident that I can prove my worth through a competency test. Thus I kindly request Thorsten or Niall to please add devector to the ideas page and provide a competency test if possible. Regards, Divyansh Gupta, Sophomore Undergraduate Student, Indian Institute of Technology - Kharagpur

1 0

[PropertyTree] In-Memory Performance of Xml/Json Serialization?
by john smith 15 Feb '15

15 Feb '15

I'm personally more interested in the Xml characteristics, but I have noticed that the JSON parsing is much slower as it doesn't use rapidXml. The implementation of the JSON and XML read/write methods both use std::basic_*stream which is slow for in-memory usage. In the xml methods there also appears to be a strong assumption that "Key" is a std::string which then follows that the "Ptree::key_type::value_type" is of type char. Is there or would there be any opposition to the development of more performant write_xml() and read_xml() methods for in-memory use? These new performant overloads could either use std::string or char* directly instead of the slower stringstream classes? If the Key template argument is an std::string, the *printf* c-style methods could be used to improve performance and eliminate the locks that stringstreams uses. There is already an std::string based arg set that is used for a filename, so that would need to be overcome.

1 0

Re: [boost] GSOC 2015 : Project on Concurrent Hash Tables
by Amarnath V A 14 Feb '15

14 Feb '15

Hello Nial, I am a graduate student from India and I have spent some time looking into the boost GSoC page for last few days. And concurrent hash tables project has grabbed my attention. I would like to see if I am competent enough to contribute to the project. First of all, like you had mentioned in the mailing list to another prospective candidate, I have got the source code and compiled the unit tests. And they are passing as expected (as far as I understand). I have a few questions regarding the code base before I jump in try to complete the test. 1. As I have experience only on C++98, I am not sure what is the purpose of the move constructors. Reading up on internet gave me fair idea about move constructors in general. In our context, is there anything specific to be taken care? Could you provide few ideas of what is the expected result of the move? The important question I have is should the move rehash all the hashes? (Is that why you were mentioning about rehash()?) 2. Similarly, does the copy constructor need to just perform a deep copy of the hash table? Or should it also perform a rehashing? 3. Could you also point me to any white paper or publication that gave you how to go about with the implementation of concurrent_unordered_map? 4. Being a Linux user, I am using Ubuntu as my dev box. I have currently build the source code using gcc v4.8.2 and clang v3.4. Is this fine? Sorry if my mail ends up as a cross post. I am new to this list. And thanks for bearing with my (maybe silly) questions. Thanks, Amarnath

2 1

Re: [boost] [gsoc15] Proposal
by Ganesh Prasad 13 Feb '15

13 Feb '15

The METALISCPP project was only a starter. My idea was to implement a very minimal syntactical abstraction over the metaprogramming constructs and build a prolog like library over it. As you can see, the METALISCPP simply uses macros to hide all those long template-based codes and provide an easier and more convenient syntax. The main motivation behind it was to have a library that would handle polices, inheritance, complex dependencies and such conveniently at compile time with a logic oriented syntax. Then I started thinking about extending the idea for a complete First Order Logic Programming Library and got stuck there. If you are willing to mentor it this year, we can try to improve the performance and syntactically modify the metalog library, maybe we'll end up with something as convenient as Boost::Phoenix. Best Wishes Ganesh PS I've forked metalog and trying to figure out what useful things can be done with it in 3 months time.

2 1

Asking for boost.persistent source code
by Yichao Zhang 13 Feb '15

13 Feb '15

Hi, I ran into the boost.persistent library the other day and think it got a really neat interface, and the transactions are exactly what I had in mind when I look for a persistent library. The code is not in the sandbox, but I really would like to have a copy of it. It would be nice if the original author can drop me a tarball. Thanks in advance, Yichao

1 0

[gsoc15] Attn: We need 2015 mentors and project ideas for Boost!
by Niall Douglas 12 Feb '15

12 Feb '15

Dear Boost community, We are now within one month of the beginning of Google Summer of Code 2015! Last year's GSoC furthered the continuing success of the Boost GSoC programme with the first ever Boost funded extension to a GSoC project (that being Boost.Hana by Louis Dionne mentored by Joel Falcou, congrats to both of them on passing an exceptionally tough selection process), and over $50,000 of Google funding brought to Boost in 2014. We also sent three representatives to last year's mentor summit, including one student whose entire expenses the Boost Steering Committee very generously covered. As part of filling in our application for 2015, we must supply to Google a list of potential GSoC mentors and potential GSoC projects for summer 2015. There are a number of changes to how we design project ideas for students this year intended to improve the GSoC experience for both students and mentors, so please examine the ideas page which outlines those changes at https://svn.boost.org/trac/boost/wiki/SoC2015 and if you have any questions or concerns about those changes, please ask now rather than just before the GSoC deadline. If you think yourself able to mentor a student doing some work on Boost this summer, *please* consider adding a description of the proposed work item and your name to the list. Last year we acquired eight slots from Google and had to disappoint two mentors and students, we hope with the improved selection process we can get back to the ten annual slots we once had. If you want to know more about mentoring a Google Summer of Code funded student work before you nominate yourself, please feel free to ask on the main Boost developers mailing list boost(a)lists.boost.org. Thank you in advance for your time. Niall Douglas (Boost Google Summer of Code admin) Boris Schäling (Boost Google Summer of Code admin) --- Boost C++ Libraries Google Summer of Code 2014 admin https://svn.boost.org/trac/boost/wiki/SoC2014

7 19

[gsoc15] Proposal
by Ganesh Prasad 12 Feb '15

12 Feb '15

Now that we are rather well ahead with the phoenix library, I propose to develop a compile-time Logic Programming library for boost. I understand that a handful of months during GSoC15 are not enough for developing a complete and usable library, but the foundations of the library can be laid during this GSoC. I have some experience with writing a small compile-time library for functional programming with a LISP like syntax. That can be found at https://github.com/GnsP/GNS--META_LISCPP . Currently I am trying to identify the requirements for a decent compile-time logic library. If it could be acceptable as a GSoC project (I don't know, the idea is pretty big one for 3 months), I'll be back with an initial design of the proposed library. Best Wishes Ganesh Prasad PS I had been planning on this library since last year, I am positive that this project is feasible (though Logic programming would require non-determinism, it can be handled to some extent with template metaprogramming, I'm still working on it).

2 1

Re: [boost] [polygon] voronoi diagram in a bounding box
by Dan Chen 11 Feb '15

11 Feb '15

Hi Andrii, This helps. Thanks a lot! Dan

1 0

GitHub third-party application permissions
by Vladimir Prus 11 Feb '15

11 Feb '15

Hi, the GitHub boostorg organization is configured in a way that any application authorized by any organization member will have full access to boostorg data. Is that desirable? I've noticed accidentally, and don't know much about github permission model, but it seems that all authorized applications will have access to all repositories the user has, there does not appear a way to limit either repositories or operations. Comments? -- Vladimir Prus CodeSourcery / Mentor Embedded http://vladimirprus.com

1 0

Cleanup of test results.
by Rene Rivera 11 Feb '15

11 Feb '15

Just an FYI for testers and authors.. I implemented some changes to the report generation that: a) Expires old results to not be shown in the results. I'm considering old to be anything past two weeks of age. This applies to all branches (i.e. develop and master). b) Filtering of master, aka release, results to only include an approved list of testers. This brings in some explicit control to what is considered the release toolsets. Which is something we used to enforce, but lost after the git transition. So it's back now. Rene. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

2 3

[GSoC 2015] Boost Document library development
by amitoj singh 11 Feb '15

11 Feb '15

Hello, My name is Amitoj Singh. I am pursuing B.Tech form Guru Nanak Dev Engineering college. I would like to work on Boost Document library Development. Can I have a more details on this project so that I can submit my first patch. Thanks! Regards! -- "Never repeat yourself" Amitoj singh slideshare.com/amitoj95 github.com/amitojsingh amitojsworld.wordpress.com

1 0

Re: [boost] [polygon] voronoi diagram in a bounding box
by Dan Chen 10 Feb '15

10 Feb '15

Hi Andrii, I'm implementing a Lloyd's algorithm to get a centroidal Voronoi tessellation of a box. In this algorithm, I need to get the voronoi cells in the box, and find the centroids of these cells. Thanks,Dan

2 1

[gsoc15] Google Summer of Code 2015 ideas needed before 20th Feb
by Niall Douglas 10 Feb '15

10 Feb '15

Dear Boost community, The Google Summer of Code 2015 organisation application period has begun. We need project ideas for our ideas page at https://svn.boost.org/trac/boost/wiki/SoC2015, plus anyone willing to mentor. Last year we got eight slots, the previous year seven slots. Let's try to get back to ten slots for 2015! Niall & Boris --- Boost C++ Libraries Google Summer of Code 2015 admin https://svn.boost.org/trac/boost/wiki/SoC2015

1 0

Regression testing: too many runners?
by Dmitry Moskalchuk 09 Feb '15

09 Feb '15

Guys, As you may know, I'm working on automatic regression testing of Boost on Android. I spent several weeks debugging it and now it seems to be close to the finish - i.e. we'll have soon fully automatic 24x7 regression testing with uploading all results to the Boost public FTP. As you can see, some results are already uploading on a regular basis - http://www.boost.org/development/tests/master/developer/summary.html (there are results of just few libraries at the current moment since I've limited testing by only those libraries to save time needed for debugging testing scripts; as far as I finish with my debugging, I'll enable testing of all libraries). However, I've realized that for thorough testing matrix of the variants become really big. Look, right now there are nine runners for Android, and this number is in fact very limited. They differs by target ABI (three arm variants, x86 and x86_64) and version of Android (API level 19 - Android 4.4 and 21 - Android 5.0). However, it has sense to test also on Android 4.0, 4.1, 4.2 and 4.3 since theirs market share is still large (see https://developer.android.com/about/dashboards/index.html) Add to that MIPS target ABI (not yet included to the testing) and multiple by two to have tests running with both default settings and with -std=c++11 - and you'll get really big total number of runners. I'm asking for advice from community. It's not the big problem for us to run all such tests in all variants, but I'm unsure if it will be acceptable for Boost community to see such wide table of runners. I'm afraid it will look like a flood. We also publish Android-only results on https://boost.crystax.net/master/developer/summary.html and we'll definitely display all results from all runners there. Please let me know if the same approach would work for http://www.boost.org/development/tests/master/developer/summary.html or should I limit somehow runners to be uploaded to the Boost FTP. -- Dmitry Moskalchuk

4 5

[githelp] Relative submodule paths..
by Rene Rivera 09 Feb '15

09 Feb '15

I've been trying to clean out the pull requests for the boost super-project and I ran into this one <https://github.com/boostorg/boost/pull/33>. And I don't really know if it makes sense, as I have personally not done a fork of the super-project. Is it a real problem? Should we change all the sub-project references? If yes, what are the likely impacts on others and existing release processes? -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

4 5

[polygon] voronoi diagram in a bounding box
by Dan Chen 08 Feb '15

08 Feb '15

Hi all, I am not sure whether this is the right place to ask this question. Basically, I want to compute the the voronoi diagram of a set of points in a bounding box, and output the voronoi cells. My idea is, after getting the voronoi diagram vd of the point set, for each voronoi cell in vd, compute the intersection of the cell and the bounding box. I am wondering whether this can be done in a better way with the boost libraries. Thanks,Dan

2 1

[voronoi] Issue with boost::polygon::voronoi_diagram<> as class variable
by duke 08 Feb '15

08 Feb '15

For some reason when I have a voronoi_diagram as a class variable (which it needs to be in this case), I get this error on compile: Error 49 error C2248: 'boost::polygon::voronoi_diagram<T>::operator =' : cannot access private member declared in class 'boost::polygon::voronoi_diagram<T>' I'm new to C# so it may be something obvious. - George

2 1

[MPL] Advice on how to proceed with a bugfix pull request
by Bruno Dutra 08 Feb '15

08 Feb '15

Hello everyone, I've found a fix to this bug <https://svn.boost.org/trac/boost/ticket/7769#no3>, which is based on BOOST PP library and thus should be supported across the various platforms, even though I just tested for a specific set up as I mentioned on my comment there. I've added some code snippets, from which it is straightforward to develop a patch, but I guess it would be best if I just issued a pull request myself. Since this is my first time contributing to MPL and to BOOST itself for all that matters, I'd like to first hear some advice on how to do this properly. For instance, to which branch should I issue the pull request? By the way, is this indeed the best way to proceed at all? Kind regards, *Bruno C. O. Dutra*

2 2

A proposal
by Mudit Sharma 08 Feb '15

08 Feb '15

After creating QR,LU and Cholesky for Boost..can we develop algorithms for determining which of QR,LU,Cholesky..etc. should be used in solving linear equations based on analyzing the running time and numerical stability specific to the problem. Is it feasible? Thanks!

2 1

Re: [boost] A proposal
by Ganesh Prasad 08 Feb '15

08 Feb '15

LU is already implemented in UBLAS. As of QR, SVD and Cholesky you might want to spend more time in debugging and testing for any one or two of the algorithms. https://github.com/GnsP/viennacl-dev/tree/master/viennacl/linalg you can find some useful sources here. Best wishes Ganesh

1 0

[c++11] MSVC does not define __cplusplus?
by Oliver Kowalke 07 Feb '15

07 Feb '15

Hi, I encountered that '__cplusplus < 201103L' evaluates on MSVC (14.0 ...) to true?! At least on GCC + CLANG this test works - what about MSVC? best regards, Oliver

4 4

[new libraries] [sort] New Library Check list updated
by Beman Dawes 07 Feb '15

07 Feb '15

As we started through the process of adding the sort library as a module, it became obvious the docs for how to do this were quite out-of-date. The best document for adding new libraries is https://svn.boost.org/trac/boost/wiki/ReleasePractices/ManagerCheckList#New…, and that section has now been updated. Although this document is written from the perspective of release managers, the New Library Checklist section serves as a roadmap for what is expected as a new library goes through the stages of being added to a Boost distribution. Comments and corrections welcome, --Beman

5 6

Serialisation: Is is_trivial<T> a sufficient precondition to bypass serialisation?
by Niall Douglas 06 Feb '15

06 Feb '15

A library user has raised an interesting question at: https://github.com/BoostGSoC13/boost.afio/commit/ac32ebfceb9a08b133e8c d47000d3b4807bc3e42#commitcomment-9574522 Basically, AFIO v1.3 has new pre-serialisation metaprogramming in response to Robert's comments on his Incubator about it being too hard to serialise and deserialise data with AFIO. AFIO will now consume any STL container and will implicitly auto expand to ASIO scatter gather buffers any: 1. Trivial type T 2. C array of trivial type T 3. STL container of trivial type T, including initializer_list. A free function, to_asio_buffers(T), can be specialised by external code to extend this with custom ASIO scatter gather buffers generation. Note that AFIO explicitly and intentionally expects that anyone interested in async file i/o will be doing their serialisation and endian conversion far away from AFIO code, so to_asio_buffers(T) is really for marking extra types to be treated as implicit auto expand. The user asks the question: Is is_trivial<T> a sufficient precondition for this auto expansion to be safe, or should is_standard_layout<T> also be required? The user notes that is_trivial<T> && is_standard_layout<T> == is_pod<T> which seems a little overkill to me. There is also the possibility that is_trivial<T> is too conservative. Some may argue that is_trivially_copyable<T> would be sufficient. Thoughts? Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

5 7

[release-mgt] missing library
by Oliver Kowalke 05 Feb '15

05 Feb '15

Hello, some weeks ago we discussed/decided that the C++11-only version of boost.coroutine should be a new lib -> boost.coroutine2. Daniel has already created a git-submodul inf the boostorg-repo and I've added the sources to branches master and develop. Unfortunately I'm missing coroutine2 (link) in <boost>/lib/coroutine2, entries in <boost>/libraries.htm and <boost>/lib/maintainers.txt. File <boost>/website/blob/master/feed/history/boost_1_58_0.qbk already contains announcement of boost.coroutine2. Could you execute the missing steps to add coroutine2 to release 1.58 please? best regards, Oliver

3 3

boost interval arithmetic
by Павел Кудан 05 Feb '15

05 Feb '15

The difference in behaviour of comparison operators and basic arithmetic operators looks as probable misconception. Default and changeable behaviour of comparison operators consists in throwing exception in intermediate situation (intersecting intervals, ! (a>b) == (a <= b) is not applicable). Great decision for correct migration from float numeric code. The only and unchangeable behaviour of arithmetic operators consists in silent returning only one of possible intervals in intermediate situation (possible return is not single, multiple interval result). The source of mistakes and undesired behaviour at migration from float numeric. At least, throwing exception by arithmetic operators at intermediate situation would provide behaviour unity of comparison and arithmetic operators and functions. Best regards, Pavel Coodan

7 51

[release-mgt] Name of release manager's repository?
by Beman Dawes 05 Feb '15

05 Feb '15

We used to have a directory <boost-root>tools/release that contained scripts used by release managers. As part of the modularization effort, it was separated into its own GitHub repository, boostorg/release. It is not a submodule of the boost super-module as it is primarily of interest only to release managers. That seems to me to be a "good thing". But I'm wondering if the "release" name might be confusing, since it doesn't contain releases or release tags themselves. Would renaming it "release-mgt" or similar be clearer? --Beman

2 2

BOOST_HAS_PRAGMA_ONCE
by Stephen Kelly 05 Feb '15

05 Feb '15

Hello, As of commit 5b20f4910d8b6b48b0b6ad2df693d36edf54cf21 in the interprocess repo, the affected files seem to expect prior include of config by the the includer. Apparently this is not obvious to everyone, so it seems worth pointing out. Thanks, Steve.

4 10

Regression tests stopped on Saturday?
by Neil Groves 05 Feb '15

05 Feb '15

Hi, I know there has been a lot go good work going on updating regression testing, and I might have missed an email. I'm currently waiting for some tests to cycle, but there appear to have been no updates since Saturday. Is this expected? Thanks, Neil Groves

6 10

Boost regression testing on Android
by Dmitry Moskalchuk 04 Feb '15

04 Feb '15

Hi all, We've just published CrystaX NDK 10.1 (https://www.crystax.net/android/ndk) which is a drop-in replacement for the Google's Android NDK, and we've included prebuilt Boost 1.57.0 libraries there, to make life easier for those developers who want to use Boost on Android. The reason I write here is that in CrystaX NDK we were able to build Boost for Android without any changes in Boost sources, just because CrystaX NDK makes Android much more POSIX-conformant than original Android is, and Boost just works on top of it. If you're interested how we did it, please read description of CrystaX NDK release on https://www.crystax.net/android/ndk. Another important point is that we were able to run Boost regression tests on Android devices - again, without any changes in Boost sources, just providing own 'adbrunner' script as tests launcher. The only thing needed is to plug one or more Android devices to USB ports and/or run one or more Android emulators and then run script for Boost testing provided by CrystaX NDK. As long as those devices/emulators are available by ADB, Boost regressions tests will run on all of them. As far as I know, Boost is not yet officially supported on Android platform, mainly because of lack of regular regression testing procedure. I wonder if someone would be interested in our results and, if yes, would he/she like to participate in further Boost-on-Android improvements? -- Dmitry Moskalchuk

3 6

[mixin] Library name
by Borislav Stanimirov 04 Feb '15

04 Feb '15

To those unfamiliar with the Boost.Mixin - it is a new library submitted for review. The docs are here: http://ibob.github.io/boost.mixin/index.html The code is here: https://github.com/iboB/boost.mixin It has been suggested multiple times that perhaps the name "mixin" isn't appropriate, so I was wondering if I can find a better one. The current name, mixin, is, as the library itself, inspired by the mixins in the Ruby programming language. However, it doesn't do exactly what Ruby's mixins do (as mentioned here: http://ibob.github.io/boost.mixin/boost_mixin/introduction.html#boost_mixin… ) My current alternative ideas are: * EntityComponent - not great since it doesn't exactly follow the entity-component-system pattern, although it can be said that it allows the construction of entities from components. * DynamicMixin - to emphasize that it's not to be confused with the CRTP mixins. It still has "mixin" in it's name though. * Trait - since it resembles the traits in Self, Scala, PHP, etc. However, a trait is more a "compile time" feature (even when talking about PHP) * TypeComposition or TyCo - a very vague description * Polymorph - since it allows the composition of polymorphic types at run time, but that's pobably even more vague Other ideas are welcome. Thanks -- Borislav

3 2

A general qurey
by Mudit Sharma 04 Feb '15

04 Feb '15

What can be done to run boost on Dev-C++? What else can be used for boost?

3 2

[chrono][multiprecision][gsoc] Project proposal, looking for feedback and mentor.
by Damian Vicino 03 Feb '15

03 Feb '15

Hi, I’m collaborating with other students working in “Simulation Driven Development” (SimDD), mostly for embed systems. The main idea in SimDD is modelling complete systems (not necessarily software) and make simulations of them. Once the simulation has the expected results start replacing some sub-models (software pieces) by real application code. The pieces that are not replaced are used to provide testing facilities. The main fields where this SimDD is used are robotics and embed systems. Where you can clearly separate models in three groups: the software, the interaction (i.e. sensors) and the environment. The software is what you are developing, the environment is the things the software will interact with and the sensors are what info the software gets from the environment and how. When the software is ready, it interacts with the sensors and the simulated environment for testing. Once tested in simulated environments it can be implemented in real world. In this context, I work in time representation problems for discrete event simulation and I will like to propose some additions to the Boost library as GSOC project. — Adding a clock to chrono for virtual simulation time, so models and real code can both work using same library for time representation. — Adding multi base support for multi-precision library. — Adding the option for an accurate mode to multi-precision (meaning a failure should happen when the result requires to be rounded and, if possible, detected at compile time). — Supporting multi base multi-precision in chrono. — For sure, documentation and tests included for everything. Is anybody interested in these additions? Can you provide some feedback about them? Is anybody interested in be my mentor for GSOC in this project? In the last year, I had being working in a general-purpose Discrete Event Simulation library as a side-project that I hope to contribute to boost. The library was submit for registration to blincubator today and in the following days I will be uploading it. Best regards, Damian Vicino

2 1

[config] Visual Studio 2015 Preview CTP 5 FWIW
by Beman Dawes 03 Feb '15

03 Feb '15

VC++ in the 2015 CTP 5 is reporting version 19.00.22512, so needs to be bumped in compiler/visualc.hpp. C++14 digit separators and C++11 universal character names in literals are supposed to be implemented, but I haven't tested them. It would also be interesting if some of bugs in recently added C++11/14 features have been fixed. --Beman

1 0

Hi everyone
by PUNEET KOHLI 03 Feb '15

03 Feb '15

Hello guys. I came to know about your organization from the melange page.Your projects really got me interested. I am a very proficient in c & c++. I have been doing a lot of competitive programming for more than a year so , i can certainly code.I wish to apply to GSOC this year and would love the opportunity if it comes from your organization. Thus, i am looking for a way to contribute and work for you.

2 3

[preprocessor] integration of 'vctuple' branch breaks [accumulator] on msvc
by Jürgen Hunold 02 Feb '15

02 Feb '15

Hi! It seems that commit 01848af60d7639fd441b5d03462e848175cf1692 Merge: fd135a0 dc54fee Author: Edward Diener <...@...> Date: Fri Jan 30 23:16:08 2015 -0500 Merge branch 'vctuple' into develop completely breaks Boost.Accumulator on all msvc versions. I've some code breaking with msvc-12.0 and the msvc-10.0 tests in the regression matrix are all red. For example: http://www.boost.org/development/tests/develop/developer/output/teeks99-08c… fails with: .../accumulators/reference_accumulator.hpp(72) : error C2061: syntax error : identifier 'BOOST_PP_CAT' .../accumulators/reference_accumulator.hpp(72) : error C2947: expecting '>' to terminate template-parameter-list, found '>' .../accumulators/reference_accumulator.hpp(72) : fatal error C1903: unable to recover from previous error(s); stopping compilation Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold(a)gmx.eu ! Germany

2 1

GSOC 2015 : Project on Concurrent Hash Tables
by Anmol Sood 02 Feb '15

02 Feb '15

Hi, I am Anmol Sood,a second year undergraduate student, pursuing Mathematics and Computing at Indian Institute of Technology,Delhi. I have been following the Boost mailing list for the last couple of months and I have been trying to understand some Boost libraries and enhancing my skills in generic programming at the same time. I saw the GSOC 2015 Boost page ( https://svn.boost.org/trac/boost/wiki/SoC2015) and the project on concurrent hash tables looks really interesting to me. I would like to know on the kind of pre-requisite skills required for the project and if I could share the progress I am making on writing code for the programming competency test here. Any tips/advice on helping me to get started on working for this project will be really helpful. Thanks.

2 1

Re: [boost] [type_traits] Rewrite and dependency free version
by Emil Dotchevski 02 Feb '15

02 Feb '15

On Mon, Feb 2, 2015 at 11:57 AM, Robert Ramey <ramey(a)rrsd.com> wrote: > this is the result of naming issues. the word array has been used for > boost::array, std::array and the built-in C/C++ array. They all ended > up in the same header so that one could find them when they were needed. > Ideally they should be separated, and boost::array's serialization should go into a boost::array header. As for serialization core dependencies, isn't it possible to define serialization function template overloads for user-defined types without including serialization library headers? E.g. aren't all function calls one makes in operator<< overloads dependent on the archive template argument? -- Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode

2 1

[sync] [thread] Faster mutex
by Antony Polukhin 02 Feb '15

02 Feb '15

Hi, One of the Mesa developers implemented a faster mutex: http://lists.freedesktop.org/archives/mesa-dev/2015-January/075260.html According to the sources of glibc, Mesa's mutex has a much smaller size (only 1 uint32_t vs 6 ints + 2 pointers), performs less actions before and after the actual syscall (no getting and setting of the mutex->__data.__owner, no type field checks) This gives an ~10% speedup. Just curious, maybe ideas from Mesa's mutex could be useful for some of the Boost libraries. -- Best regards, Antony Polukhin

4 4

[predef][check] linux clang triggers BOOST_MAC_OS
by Jürgen Hunold 01 Feb '15

01 Feb '15

Hi! I'm using clang + libc++ on Linux and the Predef "check" magic activates "BOOST_MAC_OS". That means I get: Performing configuration checks - symlinks supported : yes warn: Unable to construct ./info_as_objcpp warn: Unable to construct ./info_as_objc - BOOST_OS_MACOS : yes when running the predef test suite. Command chain: cd libs/predef/test rm -rf ../../../bin.v2/libs/predef/ ../../../bin.v2/check/ ../../../bin.v2/project-cache.jam b2 -a --verbose-test 2>&1 -d+2 --debug-configuration | tee verbose.log verbose.log is attached as zip file. And in fact the macos test are run: clang-linux.compile.c.without-pth BOOST_ROOT/src/devel/boost/bin.v2/libs/predef/test/macos_endian.test/clang- linux-3.7.0/debug/macos_endian.o which is only supposed to be run on macos. The test even passes because it internally checks for "__APPLE__" being defined, which should probably be removed, as the check should be done by the build system. Compiler: clang++ -v clang version 3.7.0 (trunk 227683) Target: x86_64-unknown-linux-gnu Thread model: posix That is current clang trunk. Though I'm already running with -d+2 --debug-configuration I get no output from the configuration test itself. Any ideas on how to debug this further? Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold(a)gmx.eu ! Germany

2 3

Change in range requirements
by Ganssauge, Gottfried 01 Feb '15

01 Feb '15

Please consider the following program: bool predicate(char c) { return c != '0'; } int main (int, char **) { using namespace boost::adaptors; boost::copy( boost::make_iterator_range( std::istream_iterator<char>(std::cin >> std::noskipws), std::istream_iterator<char>()) | filtered(predicate), std::ostream_iterator<char>(std::cout)); return 0; } It works brilliantly with boost-1.54 although std::istream_iterator is only an input iterator. Recently I tried switching to boost-1.57, but suddenly this program stopped working - it won't compile any longer, because istream_iterator is not a forward_iterator: g++ -I ~/source/aurora-python/test-build/parts/boost range_filter.cpp -o range_filter ... # lots of gobbledygook skipped range_filter.cpp:18:64: required from here /home/gotti/source/aurora-python/test-build/parts/boost/boost/concept_check.hpp:210:13: error: conversion from 'boost::iterators::single_pass_traversal_tag' to non-scalar type 'boost::iterators::forward_traversal_tag' requested Y y = x; ^ When I build an equivalent program using boost::filter_iterator it keeps compiling and working fine. Why is it, that the requirements for certain range adaptors (e.g. filtered, transformed) suddenly exclude input ranges? The corresponding iterator adaptors keep working... Gottfried Ganßauge Entwickler Content Engineering & Development ------------------------------------------------------------------ Haufe-Lexware GmbH & Co. KG Ein Unternehmen der Haufe Gruppe Munzinger Str. 9, 79111 Freiburg Tel. +49 761 898-0 Internet: http://www.haufe-lexware.com ------------------------------------------------------------------ Kommanditgesellschaft, Sitz und Registergericht Freiburg, HRA 4408 Komplementäre: Haufe-Lexware Verwaltungs GmbH, Sitz und Registergericht Freiburg, HRB 5557; Martin Laqua Beiratsvorsitzende: Andrea Haufe Geschäftsführung: Isabel Blank, Markus Dränert, Jörg Frey, Birte Hackenjos, Randolf Jessl, Markus Reithwiesner, Joachim Rotzinger, Dr. Carsten Thies ------------------------------------------------------------------

2 1

Regression testing - is procedure changed?
by Dmitry Moskalchuk 01 Feb '15

01 Feb '15

I just found that there was commit into master where whole $BOOST/tools/regression folder was removed - https://github.com/boostorg/boost/commit/50ca965a872e5d454dbdc36c2764e6e3ba…. That means instructions at http://beta.boost.org/development/running_regression_tests.html are not actual anymore. Could any one advice how to do regression testing now? I'm bit confused since I already spent significant time setting up regular regression testing of Boost on Android, and now it become completely broken. -- Dmitry Moskalchuk

2 5

Re: [boost] [Boost-testing] master and develop regressions shunt on "error: Could not find a Jamfile..."
by Jürgen Hunold 01 Feb '15

01 Feb '15

Hi Jim, Am Sonntag, 1. Februar 2015, 05:17:40 schrieb Jim Bell: > Note that I'm using a preinstalled bjam.exe. > > Both master and develop regressions shunt with this in results/bjam.log: Rene has removed tools/regression without removing the reference to it. My PR at https://github.com/boostorg/boost/pull/57 fixes this. I'm not sure if the new regression repository should be re-added as a submodule instead. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold(a)gmx.eu ! Germany

3 2

Automatically updating libs/maintainers.txt
by Daniel James 01 Feb '15

01 Feb '15

Hi, I've just written a little script to update libs/maintainers.txt from the library metadata. You can see the main changes here: https://github.com/boostorg/boost/commit/94897806350320ac87d629bb933d5aea4d… I've only done this on develop so far, so nothing's final. I will do the library list as well soon, but that might be a bit more disruptive. Daniel

2 1

[type_traits] Rewrite and dependency free version
by John Maddock 01 Feb '15

01 Feb '15

I'm going to throw this out there to see what folks think: In a branch called "Version2", see https://github.com/boostorg/type_traits/tree/Version2 is a partially rewritten type_traits lib: it doesn't yet contain all the traits of the old one, but there's a pretty good selection to test. The main pros for this version are: 1) Zero dependencies other than Boost.Config. 2) No horrible macro-obfuscation - all "real code", making it easier to read and maintain. 3) Substantially reduced template instantiations where practical - often half as many as before. 4) Substantially reduced #includes - the aim is that all files should include only what they need and no more - with what's needed determined by the actual implementation variant when appropriate. There were also a lot of spurious #includes left over from old workarounds no longer used. The main cons: 1) I don't know what I've broken, but surely something, you can help by testing but I would guess we would never be 100% sure it's all right until it's out in the field. This is the main reason for avoiding this until now. 2) MPL interoperability should still work, but files which expect type_traits headers to have included mpl ones will be broken unless they explicitly include what they need. 3) Current MPL inter-operability is fragile see https://github.com/boostorg/type_traits/blob/Version2/include/boost/type_tr… 4) Function dispatching to an mpl::bool_ involves an (inline) function call where as the old inheritance scheme did not. This should mostly disappear once optimizations are turned on, but is still a potential issue for some folks I suspect. 5) I haven't got to the "difficult" headers like common_type.hpp yet. 6) Whatever I've forgotten ;) Of course (2), (3) and (4) could be solved by making mpl's bool.hpp some kind of "core" header. So... what I need from you kind folks is: * Is this the right way forward? * Can you test with your favourite compilers and compare with results for develop - So far I've tested with msvc-10,11,12,14 Intel 14,15, GCC-4.5.4...4.9.1, plus a reasonably recent clang. * If anyone would like to help converting further traits all help would be much appreciated.... Oh and the compiler requirements in the docs are all wildly out of date too... Regards, John.

22 115

A possible solution to the SFINAE/decltype puzzler
by pfultz2 01 Feb '15

01 Feb '15

A couple years ago Eric Niebler posted a question on here about improving error messages with SFINAE and trailing decltype: http://boost.2283326.n4.nabble.com/C-11-decltype-SFINAE-puzzler-td4632622.h… The problem was getting a useful error message when writing something like this: struct h_f { template<class T> auto operator()(T x) const -> decltype(*x) { return *x; } }; constexpr static h_f h = {}; struct g_f { template<class T> auto operator()(T x) const -> decltype(h(x)) { return h(x); } }; constexpr static g_f g = {}; struct f_f { template<class T> auto operator()(T x) const -> decltype(g(x)) { return g(x); }; }; constexpr static f_f f = {}; int main() { f(0); } His solution at the time was to turn the substitution failures into errors. Of course, this has some problems as well. First, it removes the template constraints from the functions. Secondly, it can produce more errors(rather than one error with multiple "notes"). Ideally, it would be better to transport to the top the substitution failures. Well, using template aliases this can be done: https://gist.github.com/pfultz2/3d66795ef18361699fbb When I compile this code I get an error like this: reveal1.cpp:104:5: error: no matching function for call to object of type 'const reveal_failure<f_f>' f(0); ^ reveal1.cpp:56:10: note: candidate template ignored: substitution failure [with Ts = <int>, Id = identity]: indirection requires pointer operand ('int' invalid) auto operator()(Ts&&... xs) const -> decltype(F()(std::forward<Ts>(xs)...)) ^ Now, when there is multiple overloads(or multiple notes), this can be extended to handle this situation, as well. An overload for each note, can be added. Plus, the backtrace can be "flattened" so that only the "leafs" are shown. I do this here: https://gist.github.com/pfultz2/ac74129e73393f798e41 So for the 'advance' function it shows an error like this: reveal2.cpp:288:5: error: no matching function for call to object of type 'reveal<conditional<advance_advanceable, advance_decrementable, advance_incrementable> >' advance(f, 1); ^~~~~~~ reveal2.cpp:215:13: note: candidate template ignored: disabled by 'enable_if' [with Ts = <foo &, int>, Id = identity] REQUIRE_OF(models<Advanceable(Iterator, int)>()); ^ reveal2.cpp:7:82: note: expanded from macro 'REQUIRE_OF' #define REQUIRE_OF(...) template<class Id> using apply = typename std::enable_if<(Id()(__VA_ARGS__)), int>::type ^ reveal2.cpp:234:13: note: candidate template ignored: disabled by 'enable_if' [with Ts = <foo &, int>, Id = identity] REQUIRE_OF(models<Decrementable(Iterator)>()); ^ reveal2.cpp:7:82: note: expanded from macro 'REQUIRE_OF' #define REQUIRE_OF(...) template<class Id> using apply = typename std::enable_if<(Id()(__VA_ARGS__)), int>::type ^ reveal2.cpp:258:13: note: candidate template ignored: disabled by 'enable_if' [with Ts = <foo &, int>, Id = identity] REQUIRE_OF(models<Incrementable(Iterator)>()); ^ reveal2.cpp:7:82: note: expanded from macro 'REQUIRE_OF' #define REQUIRE_OF(...) template<class Id> using apply = typename std::enable_if<(Id()(__VA_ARGS__)), int>::type ^ reveal2.cpp:168:10: note: candidate template ignored: substitution failure [with Ts = <foo &, int>]: no matching function for call to object of type 'advance_advanceable' auto operator()(Ts&&... xs) -> decltype(F1()(std::forward<Ts>(xs)...)) ^ ~~ reveal2.cpp:174:10: note: candidate template ignored: substitution failure [with Ts = <foo &, int>, $1 = 0]: no matching function for call to object of type 'conditional<advance_decrementable, advance_incrementable>' auto operator()(Ts&&... xs) -> decltype(F2()(std::forward<Ts>(xs)...)) ^ So there is one note for each overload of `Advanceable`, `Decrementable`, and `Incrementable`. There is two additional notes at the bottom, this comes from the original function(ideally it would need to be normalized). I go into more detail about how this works here: http://pfultz2.com/blog/2015/01/31/improving-error-messages/ However, this is isn't quite perfect yet. First, it requires putting the type requirements into a nested failure struct. Secondly, not all the types are reported back to clang. It doesn't show the user what type `Iterator` is. Ideally, it would be nice if there was a way to push clang to report the substitution failure at least one level deeper for an expression. This is about as close as I've gotten. Is there any feedback? Questions? Perhaps some improvements? Thanks, Paul Fultz II -- View this message in context: http://boost.2283326.n4.nabble.com/A-possible-solution-to-the-SFINAE-declty… Sent from the Boost - Dev mailing list archive at Nabble.com.

1 0

Bugs
by Mudit Sharma 31 Jan '15

31 Jan '15

Where can i find bugs which can be solved for boost? Thanks!

2 1

libraries affected by common factor gcd and lcm namespace change moving from math to integer library
by Paul A. Bristow 30 Jan '15

30 Jan '15

A quick grep (for gcd_ and lcm_ in *.*pp) suggests that the following libraries are affected by gcd and lcm namespace change moving from math to integer library. At present, math_fwd.hpp provides some typedefs and declarations needed for these, and a copy of the common factor codes, so nothing may fail immediately, but these duplicate will be removed after at least one release. Chrono Interprocess Math Multiprecision Ratio Rational Units All libraries should use the declarations in integer/integer_fwd.hpp and /integer/common_factor_ct.hpp and /integer/common_factor_rt.hpp. (And there may be documentation changes too?) Something needs to be done ;-) (If you want *me* to resolve anything, then I need write access to your library). Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830

4 4

[uuid] Issue 9407: please merge fix
by Antony Polukhin 30 Jan '15

30 Jan '15

Hi, Looks like Boost.UUID library is not maintained. Could someone take care of that library. Especially I'm interested in applying a pull request to fix 9407 <https://svn.boost.org/trac/boost/ticket/9407> issue ( https://github.com/boostorg/uuid/pull/2) Pull request has been already reviewed by Andrey Semashev and significantly improved. -- Best regards, Antony Polukhin

3 9

[Filesystem] problem with tutorial documentation
by Tom Yonkman 30 Jan '15

30 Jan '15

On the http://www.boost.org/doc/libs/1_57_0/libs/filesystem/doc/tutorial.html page, the text after the tut4.cpp code box appears to be obsolete as it doesn't match up with the current code in tut3.cpp and tut4.cpp. Tom Yonkman

2 1

[predef] Announce: Build time configuration for Predef defs.
by Rene Rivera 29 Jan '15

29 Jan '15

Following on the concept by Peter Dimov of using the BBv2 config feature combined with tests I'm pleased to announce that Predef now has a similar feature. In the develop branch of Predef you can now do the following: import ../libs/predef/check/predef : require : predef-require ; run macos_only_test.cpp : : : [ predef-require "BOOST_OS_MACOS" ] ; run vc15_only_test.cpp : : : [ predef-require "BOOST_COMP_MSVC >= 15.0.0" ] ; The expression(s) to check can use any of the definitions that Predef has. The general for is: "<DEF> <OP> <VERSION>". Where <OP> is any of the usual C/C++ relational operators. And <VERSION> is a partial or complete triplet of integers. You can specify multiple checked expressions that are all required. Also part of this is a more general "check" rule that allows for custom build requirements. For example: import ../libs/predef/check/predef : require check : predef-require predef-check ; run macos_only_test.cpp : : : [ predef-require "BOOST_OS_MACOS" ] ; run vc15_only_test.cpp : : : [ predef-check "BOOST_COMP_MSVC >= 15.0.0" : <define>THIS_IS_MSVC : <build>no ] ; I'll put this into master as soon as I have appropriate documentation. Enjoy. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

4 12

Wiki, website, and stuff..
by Rene Rivera 29 Jan '15

29 Jan '15

I was contemplating editing the release schedule documentation < https://svn.boost.org/trac/boost/wiki/ReleaseSchedule> and thinking if it would be better to start moving such documentation away from the Trac wiki. And I think it is a good idea to move that documentation elsewhere. Especially if it's some place where it's easier to manager the editing permissions and contributions. So I was thinking about what options we had. What I'm aware of as choices are: * Another project in Github just for wiki like documentation. * Using the website project wiki for it. * Adding it directly to the website given how easy it is to edit online now. Although not so easy to preview because of the way the web site works. * A github pages site of some sort. Are there other options? Any opinions on the above options? -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

4 4

List of boost headers in boost/ (was RE: preprocess operation problems)
by Fletcher, John P 29 Jan '15

29 Jan '15

I have been involved in a discussion about the problem of keeping uptodate the header files in the top level boost/ which only get updated if they are links to the corresponding file in the boost/libs/ subdirectory which they refer to, if there is one. To give an idea of the size of the problem of headers in boost which are not links, attached is a list of all the *.hpp files in the current boost/ on develop. Only a very small number of them are links. Some of them may only contain links to headers in other directories and these will be being updated, but some of the top level headers are substantial files in themselves. These files are not being updated from when I set up the local git repository. This means that if the underlying file changes, the two get out of step. This has happened in the case of boost/integer_fwd.hpp as discussed in the other thread. My interest is to be able to maintain and update the particular library I have agreed to maintain, Boost Phoenix. That has many dependencies not only of its own but also the tools e.g. test and preprocess, which I need to use from time to time. I hope we can evolve a situation where it is clear to a maintainer what is needed to keep a consistent working environment. I know that is not easy because of the way tools, such as compilers and indeed the C++ standard itself, keep on changing. We do need a working platform which we can understand and work with. I think some of the present problems are arising because of very reasonable attempts to make boost more consistent. Some of the changes of configuration are causing problems not forseen, because of the wide interdependence of the boost libraries. John Fletcher

5 5

preprocess operation problems
by Fletcher, John P 29 Jan '15

29 Jan '15

I run with all the boost libraries on develop. Today the preprocess operation will not run unless I patch the file boost/integer/common_factor_ct.hpp with the following code after the includes. #ifdef BOOST_NO_INTEGRAL_INT64_T typedef unsigned long static_gcd_type; #else typedef boost::uintmax_t static_gcd_type; #endif The compiler errors had indicated that this definition was missing. I have not traced the change which caused this problem, and I have not run preprocess for some time so don't know what happened and when. I can now run with gcc 4.6 John Fletcher

4 14

Template Instantiation Profiler with Callgrind Output (KCacheGrind)
by Mikael Persson 29 Jan '15

29 Jan '15

Hi boost developers and users, I just wanted to announce a recent development in my little pet-project, which is Templight: a template instantiation profiling tool based on Clang. I think that many of you would be interested in experimenting with it because many boost libraries are great examples of template-heavy libraries and many maintainers, developers and users might be interested in gathering data and diagnosing the real compilation costs (in time and memory) of various components of Boost. Templight is a Clang-based profiler that can act as a drop-in replacement (e.g., in cmake) for the clang compiler, with the addition of generating a complete trace of the template instantiation history with associated time and memory (optional) costs. This allows you to see not only how deeply recursive certain template instantiations are, but also identify which instantiations the compiler spends the most time or memory on. It is basically to meta-programming what a run-time profiler is to ordinary code. The templight profiler itself has reached a fairly stable state. It works at least under Linux and Windows (through "templight-cl.exe", which is a drop-in replacement for "clang-cl.exe", which is compatible with MSVC "cl.exe"), but probably works wherever clang works. Which means that you are welcome to try it. I have also used it successfully to build a few cmake-based projects (by setting CC and CXX environment variables to point to templight). Templight is currently also used in the back-end of the "metashell" project as well (an interactive shell interpreter and debugger for C++ template meta-programs). You can build the templight profiler against the clang source (with a patch + some added code), as it instructs on the github readme: https://github.com/mikael-s-persson/templight But most recently, I have created a separate set of tools to convert templight trace files to other formats. The most awesome of these outputs is the "callgrind" output, which produces a "meta-"call-graph, that is similar to (and in the same format as) call-graphs generated by run-time profiling tools like callgrind, but the profiling data is, of course, related to the compilation costs (time / memory). That conversion tool is available here: https://github.com/mikael-s-persson/templight-tools With that, you can open the converted templight trace files in the visualization tool KCacheGrind, which is great (works both on unix-like systems and Windows, thanks to Qt5). Here is a screenshot of that for one of Boost.Container's example programs: https://raw.githubusercontent.com/mikael-s-persson/templight-tools/master/i… I really hope that some of you will give this a try. I'm really hoping that it will be useful to you, and that you can provide feedback and feature requests. I couldn't think of any better target audience for this tool. Cheers, Mikael. -- Sven Mikael Persson, M.Sc.(Tech.) PhD Candidate and Vanier CGS Scholar, Department of Mechanical Engineering, McGill University,

2 3

[config] [detail] Macro BOOST_WORKAROUND
by Andrzej Krzemienski 28 Jan '15

28 Jan '15

Hi Everyone, I have a couple of concerns regarding macro BOOST_WORKAROUND. 1. Is usage thereof recommended? 2. Why is it documented in Boost.Config but defined in Boost.Detail? 3. Should it not belong to Boost.Config? 4. Why should I use it rather than manual if (BOOST_INTEL < 551) ? Now, that it is in Boost.Detail, I have to make a dependency on Boost.Detail, and indirectly on Boost.MPL because other components in Boost.Detail do. Regards, &rzej

4 4

[test] Who had the emulation of Test written using gtest?
by Niall Douglas 28 Jan '15

28 Jan '15

Sometime during the past few weeks someone mentioned they had written out a set of Boost.Test macros which converted Boost.Test unit test suites into Google Test without needing to modify the Boost.Test using unit test suite. Can whoever that was make themselves known to me please? It would save having to replicate your effort here ... thanks in advance. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

1 0

Re: [boost] [filesystem, regex, asio] These three libraries successfully ported to Windows Phone 8.1
by Moshe Rubin 28 Jan '15

28 Jan '15

On January 27, 2015 09:55 GMT, Paul A. Bristow wrote: >>> And thank you very much for the improved WinRT support. >> >> My pleasure. It was an education for me (in the positive sense of the >> word!) participating in porting Boost. I will only rest on my laurels >> once the port authorized by the crew and back in the repository <g>. > > I'm pleased to see that Windows Phone developers will now be able to use these Boost libraries. When we went looking for Boost ports for Windows Phone 8, we had a sinking feeling because no one had ported any of the libraries to WinRT. Steven Gates of Microsoft took the first step, and was a great encouragement to me and my company. I'm glad to be able to return the favor to the Boost project, as we have benefited very much from this excellent collection of libraries. > I'm also curious to know if you have tried to port the Boost.Math library? > > Although it contains a lot of esoteric mathy stuff that are unlikely to be mainstream on a phone > app, there are also some very simple-to-use statistics stuff that will/should be widely applicable. > > Have you tried this yet? Are there any obstacles that you can foresee? We did not need Boost.Math in our product so I did not look into building it. I'm happy to say that I just now built it for Windows Phone 8.1 on a Visual Studio 12 2013 system and it compiles and creates the resulting libs like a pro: <command> b2 toolset=msvc-12.0 windows-api=phone architecture=arm link=static --with-math variant=debug debug-store=database debug-symbols=on pch=off cxxflags=-ZW stage </command> Libraries created: (*) libboost_math_tr1-vc120-mt-gd-1_58.lib (*) libboost_math_tr1f-vc120-mt-gd-1_58.lib (*) libboost_math_c99-vc120-mt-gd-1_58.lib (*) libboost_math_c99f-vc120-mt-gd-1_58.lib The only warning message received, and there are many of these, is LNK4264: <snippet> msvc.archive bin.v2\libs\math\build\...\libboost_math_tr1-vc120-mt-gd-1_58.lib bin.v2\libs\math\build\...\sph_neumann.obj : warning LNK4264: archiving object file compiled with /ZW into a static library; note that when authoring Windows Runtime types it is not recommended to link with a static library that contains Windows Runtime metadata bin.v2\libs\math\build\...\sph_legendre.obj : warning LNK4264: archiving object file compiled with /ZW into a static library; note that when authoring Windows Runtime types it is not recommended to link with a static library that contains Windows Runtime metadata bin.v2\libs\math\build\...\sph_bessel.obj : warning LNK4264: archiving object file compiled with /ZW into a static library; note that when authoring Windows Runtime types it is not recommended to link with a static library that contains Windows Runtime metadata . . . bin.v2\libs\math\build\...\beta.obj : warning LNK4264: archiving object file compiled with /ZW into a static library; note that when authoring Windows Runtime types it is not recommended to link with a static library that contains Windows Runtime metadata bin.v2\libs\math\build\...\assoc_legendre.obj : warning LNK4264: archiving object file compiled with /ZW into a static library; note that when authoring Windows Runtime types it is not recommended to link with a static library that contains Windows Runtime metadata bin.v2\libs\math\build\...\assoc_laguerre.obj : warning LNK4264: archiving object file compiled with /ZW into a static library; note that when authoring Windows Runtime types it is not recommended to link with a static library that contains Windows Runtime metadata common.copy stage\lib\libboost_math_tr1-vc120-mt-gd-1_58.lib bin.v2\libs\math\build\...\libboost_math_tr1-vc120-mt-gd-1_58.lib 1 file(s) copied. </snippet> I encountered many of these warnings when building my ported libraries. The online documentation seems to indicate that this is a recommendation. I can tell you that the ported libraries, with these warnings, all function correctly with no problems. In short, it looks like Boost.Math compiles as-is for Windows Phone 8.1. Moshe

2 1

Re: [boost] [filesystem, regex, asio] These three libraries successfully ported to Windows Phone 8.1
by Moshe Rubin 28 Jan '15

28 Jan '15

On 28 Jan 2015 at 02:04:22 GMT, Niall Douglas wrote: > And once again, my apologies for earlier. It is no excuse, but that > particular day I had the misfortune of combining codeine and a lot of > cough medicine due to a heavy flu. This affected my mind. I was quite > appalled with myself when I read what I had written to you the next > day, very embarrassing, I was clearly off in a grim imagination land > and had completely underestimated its effects on my wits. > > As a token of making good on my earlier behaviours, do feel free to > email me off list to review your pull requests for any problems, > either before or after you submit them. And thank you once again for > making the effort, it is hugely appreciated here. Rest assured, I harbor no ill will at all. Quite the contrary, notwithstanding the text written, it was obvious you were a battle-seasoned professional and knowledgeable software engineer, one worth listening to. As a newbie to the Boost mailing list, I have gained invaluable information from you and others that will stand me in good stead. The ones to feel sorry for are those involved in the Linux kernel -- Linus Torvalds most certainly does not apologize for his comments! <g> I appreciate your candor, a welcome trait in the professional world. I'm currently working on verifying the changes using the regression test suite, and cleaning up the changes based on the comments you posted the other day. Thank you for your kind offer to eyeball my pull requests before or after submitting them. I will certainly feel free to take you up on your offer. Moshe

1 0

[filesystem, regex, asio] These three libraries successfully ported to Windows Phone 8.1
by Moshe Rubin 28 Jan '15

28 Jan '15

After the helpful advice I received in this mailing list and other forums, I'm happy to report that the three Boost libraries, filesystem, regex, and asio have been successfully ported to Windows Phone 8.1. Our corporate product is back up and running on Windows Phone 8.1 devices. I assume there are others who will be happy to download the new Boost code for use in their WP 8.1 apps. These libraries will hopefully join those already ported by Steven Gates of Microsoft [http://blogs.msdn.com/b/vcblog/archive/2014/07/18/using-boost-libraries-in-…] I am therefore beginning the process of verifying the port using the Boost regression test suite (I have to decide how to get them to run under Windows Phone 8.1). When the code has passed the regression suite I will issue a pull request against the GitHub repository. Thanks again to everyone in this list for their helpful comments and suggestions, Moshe Rubin Technology Manager Hyperlync Technologies Ltd. Jerusalem, Israel

4 5

Re: [boost] [filesystem, regex, asio] These three libraries successfully ported to Windows Phone 8.1
by Moshe Rubin 28 Jan '15

28 Jan '15

On 26 Jan 2015 15:51, Niall Douglas wrote: >> When the code has passed the regression suite I will issue a pull >> request against the GitHub repository. > Some tips for creating a successful pull request: > > 1. Avoid #ifdef spam. Write thunk emulations of missing APIs where possible. Here's an example for GetTickCount64(): > https://github.com/boostorg/thread/blob/master/include/boost/thread/wi > n32/thread_primitives.hpp#L290. Remember Boost still supports Windows XP and exclusively targets an XP level Win32 API. Use GetProcAddress for newer APIs. > > 2. Avoid using macros to implement functionality. > > 3. Don't forget to modify the documentation where needed to support the changes. > > 4. It might sound obvious, but make sure the unit test suite still passes on Windows XP in default build settings on all of MSVC-8, > mingw32 and mingw-w64. You'd be surprised how often pull requests don't because they use some Vista or later API, or an API not supported by mingw32. If a pull request doesn't instantly go all green on all supported platforms it tends to not be merged and get put > off till much later (sometimes forever). > > Right now cygwin support is broken at least in thread, but other libraries are probably a lot better, so test that too. > > 5. Consider additional unit tests where appropriate. In this situation I'd doubt you'd need them. These are excellent points, obviously the product of your own "battles" with modifying the Boost source base. Many thanks for sharing them, and now is the perfect time to learn them. > And thank you very much for the improved WinRT support. My pleasure. It was an education for me (in the positive sense of the word!) participating in porting Boost. I will only rest on my laurels once the port authorized by the crew and back in the repository <g>. Moshe

3 2

[release] Release schedule changes..
by Rene Rivera 27 Jan '15

27 Jan '15

After some discussion in the Boost Release Team we've decided on an ongoing schedule for releases. Taking into account the realities of how long it takes for authors and the release team to work on a release we've decided to move to *three* releases a year. The targets for the releases will now be: * Spring release on the second Wednesday of April. * Summer release on the second Wednesday of August. * Fall/Winter release on the second Wednesday of December. There will be no January release. This will allow for the fact that most people are on extended holidays during Winter. It will also allow for people to work on larger changes that require more testing time during the longer Winter period. We are also moving to Wednesday release to allow the release managers non-weekend time to work before and after the release. Please consult the Boost calendar for specific dates and merge schedule for the next release. Thanks, the Boost Release Team. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

2 1

Boost modular: Build without version number suffixes
by Robert Dailey 27 Jan '15

27 Jan '15

When I build modular boost on Linux Mint 17, I get SO files named like so: libboost_date_time.so.1.57.0 with a corresponding symlink without the version number: libboost_date_time.so I'd like it to build without the version number because when I rename the base file to remove the version, code links fine but during runtime it tries to load the SO with the version number at the end. I don't know how to fix that, so I assume the fix is to build boost without the version numbers. Any help is appreciated.

5 8

[doc][build]
by Damian Vicino 27 Jan '15

27 Jan '15

Hi, I noticed the boost.build site links to documentations are broken in http://www.boost.org/doc/libs/1_57_0/tools/build/index.html <http://www.boost.org/doc/libs/1_57_0/tools/build/index.html>: http://www.boost.org/doc/libs/doc/html/bbv2.html <http://www.boost.org/doc/libs/doc/html/bbv2.html> http://www.boost.org/doc/libs/1_57_0/tools/build/doc/userman.pdf <http://www.boost.org/doc/libs/1_57_0/tools/build/doc/userman.pdf> both return 404. I got there following links in installation documentation.

1 0

[endian] [bikeshed] Conversion function naming discussion
by Beman Dawes 26 Jan '15

26 Jan '15

Naming is always a bike shed issue. I'm starting a separate thread for those who don't care can easily ignore it. The current names I'm least comfortable with are the conversion function names in the endian sub-namespace: big_to_native big_to_native_inplace native_to_big native_to_big_inplace little_to_native little_to_native_inplace native_to_little native_to_little_inplace conditional_reverse conditional_reverse_inplace These are quite explicit, but are a bit too long and awkward for my taste. I'd be willing to change these names if someone can come up with replacements that are shorter and less awkward, but still reasonable explicit. --Beman

4 5

Boost 1.58 schedule available?
by Barend Gehrels 26 Jan '15

26 Jan '15

Hi, Boost 1.57 was released last November 3, so it is probably about the time to merge to master again? Is there already a schedule available? Thanks, Barend

13 36

RFC Expression Validity Asserts
by Matt Calabrese 26 Jan '15

26 Jan '15

I've found it useful, especially in tests, to easily be able to do expression validity checking via SFINAE in a static assert. In other words, it's frequently useful to want to quickly test to make sure that a particular expression does or does not compile, similar in some ways to a concepts-lite usage pattern. The general idea is that you want to static assert that, given a series of object declarations of a specific type, a specified expression or series of expressions that deal with those objects would or would not cause substitution to fail had the object types been dependent on a template parameter. It internally relies on a macro that is invoked as such: ////////// IS_VALID_EXPR( (int) a, (float) b, // etc.. (a + b) (a - b) // etc. ) ////////// The above macro invocation results in an expression that is a constexpr bool which is true iff substitution would not fail. With the above macro, one can do, for instance: static_assert(IS_VALID_EXPR((const int) a, ++a), "Some error message."); I've found this pattern so common that I've created a macro that takes such a series of declarations and expressions and automatically produces a simple static_assert, outputting the declarations and the expression that did not compile. A slimmed down version of this macro can be toyed with via the link below (this slim version allows only one declaration and one expression per macro): http://ideone.com/RHd6FM Briefly, using the macro as such: STATIC_ASSERT_VALID ( (const int) a, ++a ); is able to produce a very human-readable error message: prog.cpp:58:1: error: static assertion failed: ******************** Given: const int a; The following expression was expected to compile but did not: ++a ******************** There is a similar macro for verifying that an expression does not compile, which I find is much more useful in practice. Notable is that the validity macro is an expression -- no statement or other declarations are introduced -- and the static assert macro produces a single static_assert. This means that you can use the assertion macro in the normal scopes that any static_assert can be used (namespace scope, class scope, function scope...). One limitation is that because it uses lambdas behind the scenes, the context in which the validity macro may be used is slightly restricted (I.E. it can't be used in an un-evaluated context). Is this something people would generally find useful? If it is considered generally useful, I don't think it's really worthy of its own library, so where would it go? Years ago I probably would have just assumed utility, but I'm not really sure where it would go in the modern boost structure. The slim version can easily have no dependencies, though the more general solution ideally depends on Boost.Preprocessor. The macros themselves require C++14, though slightly less-useful forms (ones that introduce additional declarations) could be made that would work in C++11. -- -Matt Calabrese

5 14

Templight Installation - watch your version of svn
by Fletcher, John P 26 Jan '15

26 Jan '15

I have just been installing Templight and have hit a problem. Templight installation involves installing Clang and then applying a patch to it. Older versions of svn (before 1.7) do not have the svn patch command which is used on the installation. Unfortunately Ubuntu 12.04 has version 1.6.17 installed and does not offer an update. The solution to this has been to upgrade svn to a later version from WANdisco (see http://www.wandisco.com/subversion/download) After the upgrade, the patch command will still not run if the downloads of LLVM and Clang were done with the old version of svn. So the best thing is to upgrade svn before starting. Of course I did not know this at the time. I am sending this to save someone else the same trouble. Best wishes John

1 0

[Test][Thread] Regression since 9 December?
by Vicente J. Botet Escriba 26 Jan '15

26 Jan '15

Hi, I'm getting a regression on all the Boost.Thread tests using Boost.Test to fail after this commit https://github.com/boostorg/test/commit/1eaffb96ceec82882a4e947c99735a37271…. See http://www.boost.org/development/tests/develop/developer/output/Sandia-clan…. |../../../boost/system/config.hpp:34:3: erreur: #error Must not define both BOOST_SYSTEM_DYN_LINK and BOOST_SYSTEM_STATIC_LINK # error Must not define both BOOST_SYSTEM_DYN_LINK and BOOST_SYSTEM_STATIC_LINK | When I comment the added lines everything works correctly as before. The Boost.Thread jamfile contains | <library>/boost/test//boost_unit_test_framework/<link>static | If I change it to | <library>/boost/test//boost_unit_test_framework | I get an error |darwin.link ../../../bin.v2/libs/thread/test/test_thread.test/darwin-4.9.1/debug/threading-multi/test_thread Undefined symbols for architecture x86_64: "_main", referenced from: start in crt1.10.6.o ld: symbol(s) not found for architecture x86_64 collect2: erreur: ld a retourné 1 code d'état d'exécution "/usr/gcc-4.9.1/bin/g++-4.9.1" -o "../../../bin.v2/libs/thread/test/test_thread.test/darwin-4.9.1/debug/threading-multi/test_thread" "../../../bin.v2/libs/thread/test/test_thread.test/darwin-4.9.1/debug/threading-multi/test_thread.o" "../../../bin.v2/libs/thread/test/test_thread.test/darwin-4.9.1/debug/threading-multi/winrt_init.o" "../../../bin.v2/libs/test/build/darwin-4.9.1/debug/threading-multi/libboost_unit_test_framework.dylib" "../../../bin.v2/libs/timer/build/darwin-4.9.1/debug/threading-multi/libboost_timer.dylib" "../../../bin.v2/libs/chrono/build/darwin-4.9.1/debug/threading-multi/libboost_chrono.dylib" "../../../bin.v2/libs/thread/build/darwin-4.9.1/debug/threading-multi/libboost_thread.dylib" "../../../bin.v2/libs/system/build/darwin-4.9.1/debug/threading-multi/libboost_system.dylib" -g | Do others observe the same? Do you have an idea how this can be fixed? Best, Vicente

8 24

Boost build failure on master
by Michael Caisse 25 Jan '15

25 Jan '15

I normally just compile and test Spirit/Fusion tests using the super project layout. That works fine; however, I'm setting up Bamboo build artifacts for all of Boost to enable slicker testing. As a result, I'm just trying to build all of Boost after a checkout. I admit that I've never found this to work properly. I'm following what I think are the standard instructions [1]: (lets keep it simple with linux for now) git clone --recursive git@github.com:boostorg/boost.git cd boost ./bootstrap.sh ./b2 headers ./b2 The result: error: Name clash for '<pstage/lib>libboost_system.so.1.58.0' error: error: Tried to build the target twice, with property sets having error: these incompabile properties: error: error: - none error: - <address-model>64 <architecture>x86 error: error: Please make sure to have consistent requirements for these error: properties everywhere in your project, especially for install error: targets. Ideas? Thanks! Michael 1. <https://svn.boost.org/trac/boost/wiki/TryModBoost#InstallingModularBoost> -- Michael Caisse ciere consulting ciere.com

3 4

[thread] Timed waits in Boost.Thread potentially fundamentally broken on Windows (possibly rest of Boost too)
by Niall Douglas 25 Jan '15

25 Jan '15

Dear all, CC: Stephan @ Microsoft - Stephan I'd love to know what the MSVC STL does below so we have the option of matching your behaviour. During investigating this bug report for Boost.Thread (https://svn.boost.org/trac/boost/ticket/9856) I have discovered a very worrying situation: it would appear that potentially all timed waits in Boost.Thread, and potentially in other parts of Boost, are broken on Windows Vista and later and have been for some years. The problem is in correct handling of timeouts. If one does this: mutex mtx; condition_variable cond; unique_lock<mutex> lk(mtx); assert(cv_status::timeout == cond.wait_for(lk, chrono::seconds(1))); ... one would reasonably expect occasional failures on POSIX due to spurious wakeups. It turns out that this also spuriously fails on Windows, which is a surprise probably to many as Windows hides signal handling (actually APCs) inside its Win32 APIs and automatically restarts the operation after interruption. There is, therefore, the potential that quite a lot of code written to use Boost.Thread on Windows makes the hard assumption that the assert above will never fail. The reason why Windows spuriously fails above isn't due to spurious wakeups, it is in fact due to changes in the Vista kernel scheduler as documented at https://technet.microsoft.com/en-us/magazine/2007.02.vistakernel.aspx. In essence, if you now ask Windows to go sleep for X milliseconds, Windows Vista onwards will in fact sleep for anywhere between zero and X+N milliseconds where N is some arbitrarily long value. In other words, timeouts in Windows are purely advisory, and are freely ignored by the Windows kernel from Vista onwards. You can test this for yourself using this little program which reduces the #9856 bug report to its Win32 API essentials: #include <windows.h> #include <stdio.h> #include <chrono> int main(void) { ULONG ulDelay_ms = 20; HANDLE hSemaphoreDelay = CreateSemaphore(NULL, 0, 1, NULL); for (size_t n = 0; n < 50; n++) { while (1) { auto begin = std::chrono::high_resolution_clock::now(); ULONG hr = WaitForSingleObject(hSemaphoreDelay, ulDelay_ms); auto end = std::chrono::high_resolution_clock::now(); auto diff = end - begin; if (hr == WAIT_ABANDONED) printf("Wait Abandoned "); else if (hr == WAIT_TIMEOUT) printf("Timed out "); else printf("Signaled "); DWORD lTDelta = std::chrono::duration_cast<std::chrono::milliseconds>(diff).count(); printf("Target Wait Interval: %u Real Wait Interval: %u (%u)\n", ulDelay_ms, lTDelta, diff.count()); if (lTDelta >= ulDelay_ms) break; } printf("\n"); } CloseHandle(hSemaphoreDelay); return 0; } As you'll see, actual time waited is anywhere between zero and 20 + N milliseconds where actual time waited is sometimes a whole integer multiple of the Windows kernel granularity (15 ms) or some fraction of that granularity. Most of the time he tries to hit what you asked for, but you get no guarantees. More detail about how and why Windows Vista onwards does this can be found at http://forum.sysinternals.com/bug-in-waitable-timers_topic16229.html. This raises the question about what to do with Boost.Thread. We have the following options: Option 1: Timed waits are allowed to spuriously fail by the standard, so we mark this as wontfix and move on. Anyone using the predicate timed waits has never seen a problem here anyway. Option 2: We loop waiting until steady_clock (really QueryPerformanceCounter under Boost) shows the requested timeout has passed. Problem: This wastes battery power and generates needless wakeups. A more intelligent implementation would ask Windows for the thread quanta and transform timeouts to match the Vista kernel scheduler in combination with always using deadline scheduling, but this would slow down the timed waits implementation. Option 3: We adjust Boost.Thread to return timeouts when Windows returns a timed out status code, even if the actual time waited is considerably lower than the time requested. Problem: some code written for POSIX where when you ask for a timeout you always get it may misbehave in this situation. Boost commmunity, I turn it over to you for advice! Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

4 16

Review Wizard Status Report for January 2015
by Ron Garcia 24 Jan '15

24 Jan '15

============================================== Review Wizard Status Report for January 2015 ============================================== News ==== 1. Boost 1.56 Released November 2014. New Libraries: none 2. Sort Accepted. November 2014. 3. Compute Accepted. December 2014. 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 integrated into Boost Git: * Contract - accepted September 2012; author: Lorenzo Caminiti. * Sort - accepted November 2014: author: . * Compute - accepted December 2014: author: . The following libraries have been accepted and submitted to Boost Git, but have not yet appeared in a release: * Convert - accepted June 2014; author: Vladimir Batov. The following libraries have been accepted provisionally to Boost, but have not been submitted for mini-review and full acceptance: * Endian - accepted provisionally September 2011; author Beman Dawes. * Fiber - accepted provisionally January 2014; author Oliver Kowalke. 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) * Sorting (M) * Quaternions, Vectors, Matrices (M) * Block Pointer (M) * Singularity (M) * Extended Complex Numbers (M) * Metaparse (M) * Boost.Range Extensions * Nowide (M) * Array (M) * STL Extensions (M) * Countertree (M) * Process (M) * Asynchronous File I/O (M) * Application (M) * Edit Distance (M) * Mixin (M) * Dependency Injection (M) * DLL (M) ``(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. 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. 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. Edit Distance ------------- :Author: Erik Erlandson :Review Manager: Needed :Download: https://github.com/erikerlandson/algorithm/tree/edit_distance/sequence :Description: The edit distance is the length of the shortest (or least-cost) edit script from one sequence to another, where an edit script is defined as a sequence of insertion, deletion and (optionally) substitution operations. The function implementing the edit distance is named edit_distance. This function will return the edit distance between two sequences, where sequences may be any valid range object supporting forward iteration. The edit_distance function will also, if requested, return the edit script. Mixin ----- :Author: Borislav Stanimirov :Download: https://github.com/iboB/boost.mixin :Documentation: http://ibob.github.io/boost.mixin/ :Review Manager: Needed :Description: Boost.Mixin is a library that allows the composition and modifications of polymorphic types at run time. Types and objects are constructed out of building blocks called mixins. The library uses the type boost::mixin::object as a placeholder, whose instances can be extended with existing classes (mixins), thus providing a particular instance with the functionality of all those types. Accessing the newly formed type's interface is made through messages: stand-alone functions generated by the library, which can be thought of as methods. This is given while also having full abstraction between the interface and the definition of types. An existing feature in another language similar to Boost.Mixin and also an inspiration for the library are the mixins in Ruby. The library also has similarities with the pattern entity-component-system. Dependency Injection -------------------- :Author: :Download: https://github.com/krzysztof-jusiak/di :Documentation: http://krzysztof-jusiak.github.io/di/boost/libs/di/doc/html :Incubator: http://rrsd.com/blincubator.com/bi_library/di-dependency-injection/?gform_p… :Review Manager: Needed :Description: Boost.DI is a dependency injection library improving manual dependency injection by simplifying object instantiation with automatic dependencies injection. Using Boost.DI has many advantages over manual dependency injection. * Reduce boilerplate code (No factories, no objects creation in specific order) * Reduce cost of maintenance effort (Constructor signature change won't affect di configuration) * Reduce testing effort * Give better control of what and how is created (Policies, Providers) * Give better understanding about objects hierarchy (UML Dumper) DLL --- :Author: Antony Polukhin :Download: https://github.com/apolukhin/Boost.DLL :Documentation: http://apolukhin.github.io/Boost.DLL/index.html :Review Manager: Needed :Description: This library was designed to simplify plugin development using C++ in a portable cross-platform manner. Library provides a portable across platforms way to: * load libraries * import any native functions and variables * make alias names for C++ mangled functions and symbols * query libraries for sections and exported symbols * self loading and self querying * getting program and module location by exported symbol Libraries under development =========================== See The Boost Library Incubator Project at http://blincubator.com for discussion of libraries currently under development.

6 10

clang-3.6 thread sanitizer complains on shared_ptr operations
by Gaetano Mendola 24 Jan '15

24 Jan '15

I'm using clang 3.6 with boost 1.54 $ clang-3.6 --version Ubuntu clang version 3.6.0-svn225356-1~exp1 (trunk) (based on LLVM 3.6.0) Target: x86_64-pc-linux-gnu Thread model: posix Compiling the code here: http://pastebin.com/zh0SPz5n $ clang++-3.6 -g main.cpp -lboost_system -lboost_thread -fsanitize=thread I get at runtime: ================== WARNING: ThreadSanitizer: data race (pid=5592) Write of size 8 at 0x7d080000cfe8 by thread T2 (mutexes: write M18): #0 operator delete(void*) <null> (a.out+0x00000045febb) #1 ~sp_counted_impl_p /usr/include/boost/smart_ptr/detail/sp_counted_impl.hpp:53 (a.out+0x0000004d15c9) #2 boost::detail::sp_counted_base::destroy() /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:126 (a.out+0x0000004cb77c) #3 boost::detail::sp_counted_base::weak_release() /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:160 (a.out+0x0000004c773f) #4 boost::detail::sp_counted_base::release() /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:147 (a.out+0x0000004c75e8) #5 ~shared_count /usr/include/boost/smart_ptr/detail/shared_count.hpp:371 (a.out+0x0000004c7550) #6 ~shared_ptr /usr/include/boost/smart_ptr/shared_ptr.hpp:722 (a.out+0x0000004cef59) #7 boost::shared_ptr<int>::operator=(boost::shared_ptr<int> const&) /usr/include/boost/smart_ptr/shared_ptr.hpp:507 (a.out+0x0000004cf1b7) #8 Consumer::consume(boost::shared_ptr<int>) /home/kalman/boost_sp_test/main.cpp:9 (a.out+0x0000004ced61) #9 Producer::operator()() /home/kalman/boost_sp_test/main.cpp:32 (a.out+0x0000004ceaba) #10 boost::detail::thread_data<boost::reference_wrapper<Producer> >::run() /usr/include/boost/thread/detail/thread.hpp:137 (a.out+0x0000004cc29e) #11 boost::this_thread::interruption_requested() <null> (libboost_thread.so.1.54.0+0x00000000ba49) Previous read of size 4 at 0x7d080000cfe8 by thread T1: #0 boost::detail::sp_counted_base::use_count() const /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:166 (a.out+0x0000004cb33e) #1 boost::detail::shared_count::use_count() const /usr/include/boost/smart_ptr/detail/shared_count.hpp:423 (a.out+0x0000004cf040) #2 boost::shared_ptr<int>::use_count() const /usr/include/boost/smart_ptr/shared_ptr.hpp:681 (a.out+0x0000004cefb9) #3 Consumer::operator()() /home/kalman/boost_sp_test/main.cpp:19 (a.out+0x0000004d4a29) #4 boost::detail::thread_data<boost::reference_wrapper<Consumer> >::run() /usr/include/boost/thread/detail/thread.hpp:137 (a.out+0x0000004d497e) #5 boost::this_thread::interruption_requested() <null> (libboost_thread.so.1.54.0+0x00000000ba49) Mutex M18 (0x7fff01719338) created at: #0 pthread_mutex_init <null> (a.out+0x0000004641e0) #1 mutex /usr/include/boost/thread/pthread/mutex.hpp:100 (a.out+0x0000004d1867) #2 Consumer /home/kalman/boost_sp_test/main.cpp:5 (a.out+0x0000004c6238) #3 main /home/kalman/boost_sp_test/main.cpp:41 (a.out+0x0000004c5903) Thread T2 (tid=5595, running) created by main thread at: #0 pthread_create <null> (a.out+0x000000462db1) #1 boost::thread::start_thread_noexcept() <null> (libboost_thread.so.1.54.0+0x00000000b3b8) #2 thread<boost::reference_wrapper<Producer> > /usr/include/boost/thread/detail/thread.hpp:302 (a.out+0x0000004c6639) #3 main /home/kalman/boost_sp_test/main.cpp:45 (a.out+0x0000004c59bd) Thread T1 (tid=5594, running) created by main thread at: #0 pthread_create <null> (a.out+0x000000462db1) #1 boost::thread::start_thread_noexcept() <null> (libboost_thread.so.1.54.0+0x00000000b3b8) #2 thread<boost::reference_wrapper<Consumer> > /usr/include/boost/thread/detail/thread.hpp:302 (a.out+0x0000004c6479) #3 main /home/kalman/boost_sp_test/main.cpp:44 (a.out+0x0000004c5968) SUMMARY: ThreadSanitizer: data race ??:0 operator delete(void*) ================== I believe this is a false alarm indeed the two threads are working on their own shared_ptr copy and thePtr shared pointer write/read in the two threads is protected with a mutex. I will open a ticket with clang folks if you recognize that is a false alarm, unless they are right and we have issue in shared_ptr implementation. Regards Gaetano -- cpp-today.blogspot.it --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com

4 16

Debugging optimisation unstable code - Stack and other tools
by Fletcher, John P 24 Jan '15

24 Jan '15

I am working to get the bugs out of Phoenix and have a situation where some tests are optimisation unstable - they run on Clang 3.5 with -O1 but not -O2 and on gcc 4.9.0 with -O0 but not -O1. The higher optimisation gives an erroneous return value. I am looking for tools to work with this. I have found one called Stack (http://css.csail.mit.edu/stack/) I have built it but it only has instructions for whole projects rather than individual tests. It is hard to search for because the word 'stack' has lots of other meanings. Has anyone else used this or any other tools to solve this sort of problem? It is worth noting that some of the tests run fine on develop testing. That leads me to wonder if the level of optimisation used there is documented anywhere. Thanks John

4 5

Best boost documentation
by Damian Vicino 23 Jan '15

23 Jan '15

Hi, I’m preparing a library to be proposed and I’m adapting the documentation I had to be more Boost-like. I saw there is different writing styles in the documentation. Something I’m specially interested is in the document structure, I saw some start with a tutorial, others with an overview of the concepts, others just go straight to the internals. I’m wondering if there is a preferred style or document structure to use. Best regards, Damian

3 2

[config] [regression] Regression test failures due to compiler bugs -- your advice needed
by Andrzej Krzemienski 23 Jan '15

23 Jan '15

Hi Everyone, I need the advice from the experts, on what is the recommended way to handle the following situation with regression tests. A number of tests of Boost.Optional fail. (see here: http://www.boost.org/development/tests/develop/developer/optional.html) These are the failures in optional<T&> (optional references), because quite a lot of compilers implement reference binding in a non-standard-conforming manner. (For details of these bugs see here: http://www.boost.org/doc/libs/develop/libs/optional/doc/html/boost_optional… ). The question is, how these testing failures should be reflected in regression testing configuration, so that they do not appear as bugs in the implementation of Boost.Optional? 1. I hear that marking explicit failures is not recommended, and build config based on Boost.Config should be preferred. Also, the markup will not work because from the toolset name alone I cannot make the decision whether to mark the explicit failure or not. 2. On the other hand, I hear that Boost.config should not be used to detect any bug in a compiler that is relevant only to a single Boost library. These two pieces of advice appear contradictory in my case. I would like to abide to the recommendations in Boost, but in this case it appears that I am stuck. Is there any recommendation in such case for Boost developers? Regards, &rzej

5 14

Boost.Sort - new library documentation
by Paul A. Bristow 23 Jan '15

23 Jan '15

Is there anything more that should be done to ensure that Boost.Sort new library documentation is added to the build system. It uses Quickbook, Doxygen and Autoindex. So does anything need adding to modular-boost\doc\Jamfile.v2 ? Perhaps, if I have understood this comment correctly: # Note that when refering to libraries that use auto-index we must process all the way to # docbook before including here. We must also ensure that auto-index uses it's own index # generation, otherwise we get one big index that's repeated in each library. Xslt's index # generation is also so slow that it's impractical for a build this large (takes ~ 9 hrs # to build with just 3 indexed libraries). Hence we refer to these libraries as for example: # # ../libs/interprocess/doc//standalone/<format>docbook then this needs adding ## Build the various generated docs (Doxygen and QuickBook)... <dependency>../libs/sort/doc//standalone/<format>docbook ## Add path references to the QuickBook generated docs... <implicit-dependency>../libs/sort/doc//standalone/<format>docbook but I am not clear if this is right, so I am not providing a pull request. I'm also unclear who should/will do this. Thanks Paul PS I suspect that I will also need this for Boost.Integer update soon. --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830

3 3

Re: [boost] updated Boost.Test devel->master: documentation needs
by Dave Gomboc 22 Jan '15

22 Jan '15

Gennadiy Rozental <rogeeff <at> gmail.com> writes: > Dave Gomboc <dave_gomboc <at> acm.org> writes: > > > I'll volunteer to write up a section on the production use of > > Boost.Test. I will, however, need source material in order to do so. > > Hi Dave, > > Thank you for your proposal. This section is really not something, which is > a showstopper for the move. Can I interest you in something which is? Well, I have not received any source material to date, so what I had in mind isn't going to fly anyway. I'll contact you privately after Feb. 15 (I am not realistically available to contribute sooner than that). Dave

1 0

Re: [boost] [type_traits] Rewrite and dependency free version
by Dave Gomboc 22 Jan '15

22 Jan '15

On 1/15/2015 3:12PM, Edward Diener wrote: > Trying gcc-3.4.2 it has the same result as gcc-3.4.5 using master and > Version2 branches. > > Trying gcc-3.3.3 it complains: > > "cc1plus.exe: error: unrecognized option `-Wextra'" > > for every file whether using master or version2. > > Whether type_traits should compile with these old gcc-3 versions is up > to you. Older versions of gcc (including the unofficial 2.96 versions that are still being used in 2015, by the way) will accept -W, but not know about -Wextra (the newer name for -W). However, do not confuse -W with -w. I have actually been able to implement things like integral_constant directly that compile and work on gcc 2.96. The main workaround required is to split up the template specialization into two lines: create an int const some_name = <some compile-time calculable value>, then perform the template specialization on a second line of code using ... ::value = some_name. So, supporting gcc 3.x should be a breeze. ;-) Dave

1 0

[config] defining __has_extension in suffix.hpp?
by Peter Dimov 22 Jan '15

22 Jan '15

It's useful to have #ifndef __has_feature #define __has_feature(x) 0 #endif #ifndef __has_extension #define __has_extension __has_feature #endif in suffix.hpp so that one can then use __has_extension(foo) everywhere without fear. Otherwise, even #if defined(__clang__) && defined(__has_extension) && __has_extension(foo) is a preprocessor error when __has_extension is not defined (which it isn't when not on Clang.)

4 4

[regression] master regression results do not show up
by Andrzej Krzemienski 22 Jan '15

22 Jan '15

Just try it: http://www.boost.org/development/tests/master/developer/summary.html Regards, &rzej

2 1

[config] <atomic> disabled on clang-3.6?
by Peter Dimov 22 Jan '15

22 Jan '15

libstdcpp3.hpp contains: #if defined(__clang_major__) && ((__clang_major__ < 3) || ((__clang_major__ == 3) && (__clang_minor__ < 7))) // As of clang-3.6, libstdc++ header <atomic> throws up errors with clang: # define BOOST_NO_CXX11_HDR_ATOMIC #endif but in the sibling thread about issues with clang-3.6 and thread sanitizer, SmartPtr has been reported to work with -DBOOST_SP_USE_STD_ATOMIC, which uses <atomic>. The reported g++ version is 4.9.2: g++ (Ubuntu 4.9.2-0ubuntu1~14.04) 4.9.2 and Clang is: Ubuntu clang version 3.6.0-svn225356-1~exp1 (trunk) (based on LLVM 3.6.0)

1 0

[type_traits][general] Best practice for inline namespaces?
by John Maddock 21 Jan '15

21 Jan '15

I was thinking of adding inline namespace support (ie lib versioning) to type_traits, but what's the best practice for naming the inline namespace? I was thinking of going with some mangled version of BOOST_VERSION which would effectively change the namespace with each release. That feels like it's probably right to me: old versions of any traits would then be archived in boost::tt105600:: or whatever version the change happened. Comments? Thanks, John.

9 12

[compute] Some remarks
by Thomas Heller 21 Jan '15

21 Jan '15

Hey list, These are just a few remarks I wanted to share that I made during the compute review phase. Unfortunately, I don't have the time to write a full review. As I mostly skimmed over everything so take it with a grain of salt. First of all, I really like the general idea of Boost.Compute. That is, I like the idea of having a proper API for OpenCL capable devices and I like the idea of having parallel algorithms. With that being said, i think it is a waste of opportunities to have the two tied together so closely especially considering N4104 with the combination of different execution policies which would allow for a wonderful API for using different parallelization backends (where boost.compute could be the reference implementation or some such). Additionally, I think that the author and other reviewers are running in circles when it comes to synchronization. IMHO, the event alone is enough and perfectly fine. An OpenCL event has interesting similarities to std::future<void>, and the clEnqueue functions to std::async. I'd consider the command queue however similar to std::thread (and threads should be considered harmful...). With that being said, a event should be perfectly fine to express synchronization points. Together with executors, it would even fit into the more higher level stdlib parallel algorithms. It would be very nice to get rid of a publicly exposed event class though and have one future to rule them all (one can dream...). But having a future and event in Boost.compute is, IMHO, not a good idea. Cheers, Thomas

15 70

[Boost.DI] Formal review request
by Krzysztof Jusiak 20 Jan '15

20 Jan '15

Dear Boost, I'd like to request a formal review of Boost.DI. Description: Boost.DI is C++14 header only, type safe library providing compile time, macro free constructor dependency injection. - Reduces boilerplate code - Reduces cost of maintenance effort - Reduces testing effort - Gives better control of what and how is created - Gives better understanding about objects hierarchy Source Code: https://github.com/krzysztof-jusiak/di Documentation: http://krzysztof-jusiak.github.io/di/boost/libs/di/doc/html Boost Library Incubator: http://rrsd.com/blincubator.com/bi_library/di-dependency-injection/?gform_p… Interest: http://lists.boost.org/Archives/boost/2014/07/215487.php Thanks, Kris

2 2

Clang 3.4 failing to compile boost 1.57 headers
by Robert Dailey 19 Jan '15

19 Jan '15

I'm including <boost/format.hpp> and getting this error from Clang 3.4 on Ubuntu 12: In file included from /home/fe/frontend/Core/ThirdParty/boost/include/boost/format.hpp:38: In file included from /home/fe/frontend/Core/ThirdParty/boost/include/boost/format/internals.hpp:23: In file included from /home/fe/frontend/Core/ThirdParty/boost/include/boost/format/alt_sstream.hpp:21: In file included from /home/fe/frontend/Core/ThirdParty/boost/include/boost/shared_ptr.hpp:17: In file included from /home/fe/frontend/Core/ThirdParty/boost/include/boost/smart_ptr/shared_ptr.hpp:28: In file included from /home/fe/frontend/Core/ThirdParty/boost/include/boost/smart_ptr/detail/shared_count.hpp:30: /home/fe/frontend/Core/ThirdParty/boost/include/boost/smart_ptr/detail/sp_counted_impl.hpp:229:31: error: no type named 'allocator_traits' in namespace 'std' typedef typename std::allocator_traits<A>::template rebind_alloc< this_type > A2; ~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~ Is this a bug or am I missing something? I'm using -std=C++11 flag.

6 20

Testing and toolsets
by Andrzej Krzemienski 19 Jan '15

19 Jan '15

Hi Everyone, Could anyone give me some information on how regression test matrix is supposed to work? I can see that when testers run their tests they specify a toolset; this toolset is reported in test matrix, and based on this toolset name failures in tests can be labeled as expected. Did I get it right? However, the fact that a tester turns C++11 support or not, is not necessarily reflected in the toolset name (some testers indicate it in the toolset name, others don't). On the other hand C++11 being turned on or off can affect the test results. In that case the toolset name alone is not sufficient to make a decision whether I expect a failure or not. Is there some policy for addressing this problem? Am I the only person to be affected? Regards, &rzej

8 13

How to get tests running for new library
by Steven Ross 19 Jan '15

19 Jan '15

I've added the new Sort library: https://github.com/boostorg/sort How do I get automated tests running and generating results at: http://www.boost.org/development/tests/master/developer/math.html ? Also, how do I add Sort to Trac, so I can get bug reports?

5 6

[math][integer] Moving integer utilities out of the math lib.
by John Maddock 19 Jan '15

19 Jan '15

This does look to me like a good idea, but to remain coherent, all of http://www.boost.org/doc/libs/1_57_0/libs/math/doc/html/gcd_lcm.html should move, which means: common_factor.hpp common_factor_rt.hpp common_factor_ct.hpp Plus docs and tests. Further I'd like to see the headers under boost/integer/*.hpp and the namespace changed to boost::integer. For backwards compatibility the boost/math/*.hpp headers should be present also but merely include the new ones and import the symbols into boost::math via using declarations. One SNAFU I see is that boost.integer is a largely unmaintained ragbag of utilities (though often very useful). It would be nice if someone would take responsibility for this library: any takers? It might be the right time too to move the rest of Boost.Integer into boost::integer rather than dumping everything in namespace boost? And finally to provide a "soft landing" for existing users, the Math lib docs should retain a stub page for these utilities that points to the new docs - Paul and I can take care of that one. Does that look like a plan? Anyone care to take it on? Best, John.

8 18

Warning policy? local variable hides (i.e. shadows) global variable
by Beman Dawes 19 Jan '15

19 Jan '15

GCC and Clang have had a warning for years (-Wshadow): "Warn whenever a local variable or type declaration shadows another variable, parameter, type, class member (in C++), or instance variable (in Objective-C) or whenever a built-in function is shadowed. Note that in C++, the compiler warns if a local variable shadows an explicit typedef, but not if it shadows a struct/class/enum." VC++ 2015 (aka 14.0) Preview has now added a similar warning, C4459. For example, "c:\boost\modular\develop\boost\lexical_cast\detail\converter_lexical_streams.hpp(429): warning C4459: declaration of 'n' hides global declaration". The VC++ warning also provides location info so is easy to view both the declarations involved. In this case, the declaration "bool operator<<(short n)" is shadowing a variable name in the unnamed namespace of the calling translation unit. The process of clearing these shadow warnings occasionally finds bugs that are otherwise difficult to detect. Peter Dimov and I have both found bugs in our code in the process of clearing the new C4459 warning. Even though most of the warnings don't actually signify bugs, I'm finding that clearing them makes code clearer and less confusing, particularly code I haven't looked at in a long while. Should Boost have policy to clear these warnings? A lot of the warnings involve function argument names. Should we have a guideline to prevent shadow warnings? A convention for argument names would make it easier to submit pull requests. Possible guidelines: * Prefix function argument names with "a_". Rationale: The "m_" prefix for member names has been a success. * Suffix function argument names with "_". Rationale: Short and less distracting than "m_" prefix. Thoughts? --Beman

12 29

URGENT: Regression testing repo migration..
by Rene Rivera 19 Jan '15

19 Jan '15

I'm going to remove the outdated regression testing code in the boostorg/boost super-repo the weekend of January 24th. Everyone MUST stop using the old scripts immediately as they will disappear in approximately 7 days. *** All testers please migrate to using this run.py NOW <https://raw.githubusercontent.com/boostorg/regression/develop/src/run.py>. *** All report generation please migrate to using the comprehensive build_results_all.sh script NOW: < https://raw.githubusercontent.com/boostorg/regression/develop/xsl_reports/b… >. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

3 2

[iostreams][gzip][zlib] zlib vs gzip, and linking against external libraries
by Aaron Levy 18 Jan '15

18 Jan '15

What is the difference in functionality between gzip and zlib compression? I built Boost iostreams library on Linux after exporting ZLIB_SOURCE and BZIP2_SOURCE environment variables. However when I build a sample program using gzip / bzip2 with IOStreams, I do not need to link to libzlib or libbz2. Is the zlib / bz2 code built into libboost_iostreams in this case? For reference, this is the command line I used to build the iostreams library. ./b2 --with-iostreams --build-dir=../build threading=multi variant=release link=shared runtime-link=shared -- Aaron Levy aaron.levy(a)yandex.com

3 2

Building the entire Boost documentation as Windows HTML help
by Philip Bennefall 18 Jan '15

18 Jan '15

Hi all, Is it possible to build a Windows HTML help file from the Boost documentation? It'd be a nice way of navigating it, and it's a single file so is trivial to move around. Has anyone attempted to do this? Kind regards, Philip Bennefall

1 0

Re: [boost] (correction) Clang 3.4 failing to compile boost 1.57 headers
by Fletcher, John P 18 Jan '15

18 Jan '15

Sorry folks, my value for Clang and gcc 5.0.0 was wrong - it does report 50000 I had a fault in my configuration and it was dropping back to the default 4.6.3 John ________________________________________ From: Boost [boost-bounces(a)lists.boost.org] on behalf of Peter Dimov [lists(a)pdimov.com] Sent: 18 January 2015 18:54 To: boost(a)lists.boost.org Subject: Re: [boost] Clang 3.4 failing to compile boost 1.57 headers Fletcher, John P wrote: > Results are as follows for clang 3.5 > > gcc version gcc reports clang reports > 4.6.3 40603 40700 > 4.8.2 40802 40800 > 4.9.0 40900 40900 > 4.9.2 40902 40900 > 5.0.0 50000 40700 <- actually 50000 > > I can see that there are some serious problems getting the correct > identification with Clang. Looks like unless it recognizes 4.8 or 4.9, it reports 40700 by default, which would make things a bit complicated. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

[uuid] Platform-specific UUID generator (was Re: Issue 9407: please merge fix)
by Klaim - Joël Lamotte 18 Jan '15

18 Jan '15

On Fri, Jan 16, 2015 at 10:49 AM, Antony Polukhin <antoshkka(a)gmail.com> wrote: > Looks like Boost.UUID library is not maintained. This is unfortunate and reminded me this exchange: https://twitter.com/niv_anteru/status/487496938150195200 A platform-specific random generator would apparently be far more efficient (I say apparently because I didn't know there were platform-specific uuid generation until I read this tweet). I reminded this with the fix discussion and made the ticket marked as feature request: https://svn.boost.org/trac/boost/ticket/10939 I'm taking note to try a patch but don't hold your breath. Also, would there be any benefit in having another typedef in C++11 mode which would use the std mersene twister instead of the boost one?

3 4

[filesystem] path.cpp fails to compile under clang/Cygwin
by Peter Dimov 18 Jan '15

18 Jan '15

Fails like this: clang-linux.compile.c++.without-pth ..\..\..\bin.v2\libs\filesystem\build\clang-linux-3.4.2\release\link-static\path.obj ..\..\..\libs\filesystem\src\path.cpp:36:11: fatal error: 'windows_file_codecvt.hpp' file not found # include "windows_file_codecvt.hpp" ^ 1 error generated. "clang++" -c -x c++ -Wno-variadic-macros -Wno-c99-extensions -O3 -Wno-inline -Wall -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -I"..\..\..\include" -o "..\..\..\bin.v2\libs\filesystem\build\clang-linux-3.4.2\release\link-static\path.obj" "..\..\..\libs\filesystem\src\path.cpp" Looks like a clang bug; the file is certainly there, in the same directory as path.cpp.

4 12

How do I copy all source files?
by Robert Dailey 18 Jan '15

18 Jan '15

I do adhoc builds of boost using the boost modular git repo. All libs build just fine, but I can't for the life of me copy the source files. I have tried doing it through FileZilla (SFTP) but it skips a ton of files due to the symlinks. How can I get the complete "boost" header source tree?

2 5

[Phoenix] [MSVC] 8 9 and 10 COMDAT error
by Fletcher, John P 17 Jan '15

17 Jan '15

I am attempting to sort out the bugs and test failures in Boost Phoenix. I have one test (bind_rv_sp_test) which fails at the link stage with the following error on MSVC 8 9 and 10 but not later bind_rv_sp_test.obj : fatal error LNK1179: invalid or corrupt file: duplicate COMDAT '?value@?$result_@P8Y@@AE?AV?$shared_ptr@UX@@@boost@@XZ@?$is_mem_fun_pointer_select@$0A@@detail@boost@@2_NB' I have been researching this error and attempting to find a workaround for Phoenix. Has anyone else working on Boost encountered this error and have any suggestions about it. It does appear to have been around for some years and there are a lot of suggestions but no clear resolution I have found. How important are these compilers, and would it be O.K. to mark this test as expected to fail? I don't have these compilers so for any new tests I am relying on the develop tests to check out experiments. Thank you John

2 2

Re: [boost] [compute]/ Futures Some remarks
by Antonio Colino 16 Jan '15

16 Jan '15

> > On 01/14/2015 10:46 PM, Antonio Colino wrote: > > I have a flawless implementation of this concept I am very proud of. Is any one willing to critique it? > > On 01/14/2015 10:46 PM,?Thomas Heller?wrote: > > Wanna share it? Which concept are you refering to? > > I was hoping to share this lib, if i could generate any interest in a copyable hpc version of packaged_task > On Jan 2015 20:36:40,?Thomas Heller?wrote: > Absolutely! Note that there are already a few out there doing exactly what > you described (HPX and Habanero++ come to my mind here). >On Date: Thu, 15 Jan 2015 21:58:37, Antonio Colino wrote: >What would be the best way to arrange this? Thomas if you are sill interested I am still curious by which method you would prefer to review the code, as it is not yet made public and I would like to have a second opinion before doing so.

1 0

[function] unmerged changes
by Peter Dimov 16 Jan '15

16 Jan '15

Boost.Function's develop branch appears to have accumulated a few changes that aren't in master, to which I've added one more (I neglected to check first). Looking at the test results, nothing there seems out of the ordinary, so these should probably be merged, perhaps without my final commit (which is itself a very low risk, as it merely changes detail:: to boost::detail:: in a few places).

2 1

[test] clang warning
by Peter Dimov 16 Jan '15

16 Jan '15

..\..\../boost/test/impl/debug.ipp:211:21: warning: private field 'm_binary_path_buff' is not used [-Wunused-private-field] char m_binary_path_buff[500+1]; // !! ?? ^ I'm not sure what the purpose of this member is, but according to Clang, it's not used anywhere.

4 4

[units] unmerged changes in develop
by Peter Dimov 16 Jan '15

16 Jan '15

The following changes are in develop but not in master. Should these be merged? They all look fine (and beneficial) to me. C:\Projects\boost-git\boost\libs\units>git log master..develop commit cc97c0f253a250a15f0b2174ec12a338772248b6 Merge: 87778d2 12f0a2e Author: Jürgen Hunold <jhunold(a)gmx.eu> Date: Thu Nov 6 20:44:33 2014 +0100 Merge pull request #14 from mkurdej/fix/doc-information Fix documentation on information system units. commit 87778d23197aeceaccedeea2c3df43f2fa9f9a85 Merge: b40a903 45058c0 Author: Jürgen Hunold <jhunold(a)gmx.eu> Date: Thu Nov 6 20:43:04 2014 +0100 Merge pull request #13 from mkurdej/fix/header-guards Fix header guards and namespace trailing comments. commit 12f0a2eb0a2ac2925fe04d8afb744e7178e37ddc Author: Marek Kurdej <mkurdej(a)users.noreply.github.com> Date: Thu Nov 6 12:32:02 2014 +0100 Fix quickbook warning about deprecated '\n' in generated base_units.qbk. commit 9ba957d7208322bf752d61c7d5401bb358af5f0b Author: Marek Kurdej <mkurdej(a)users.noreply.github.com> Date: Thu Nov 6 12:22:02 2014 +0100 Add doc for boost/units/systems/information.hpp. commit 2042d4d72337d05e1606eb385d5b1b3865739e70 Author: Marek Kurdej <mkurdej(a)users.noreply.github.com> Date: Thu Nov 6 12:14:53 2014 +0100 Fix documentation on information system units (not only base units). commit aaffc7fa6f8c05cff396b6fc71a3ef8b79192330 Author: Marek Kurdej <mkurdej(a)users.noreply.github.com> Date: Wed Nov 5 18:24:23 2014 +0100 Fix documentation on information system units. commit 45058c08f7c2372cef729237a21a87a036245d2d Author: Marek Kurdej <mkurdej(a)users.noreply.github.com> Date: Mon Nov 3 13:59:10 2014 +0100 Fix header guards and namespace trailing comments.

2 4

Integrating Boost.Sort library
by Steven Ross 16 Jan '15

16 Jan '15

I would like to integrate the (recently accepted) Boost.Sort library into the main Boost build process, and provide Paul A. Bristow < pbristow(a)hetp.u-net.com> access to edit the documentation (it doesn't have to be restricted to just the docs). Are there instructions on how to do this? The current code is sitting here: https://github.com/spreadsort/sort

2 3

ASIO does not fully support Windows Runtime (WinRT), and a suggestion for providing support
by Moshe Rubin 16 Jan '15

16 Jan '15

While attempting to port filesystem to Windows Phone 8.1, I encountered some issues with the WinRT portions of ASIO. Examining the Boost code shows that ASIO does not fully support WinRT. Examples are that the acceptor implementation for WinRT #includes the null_socket_service class in socket_acceptor_service.hpp, rendering it unsupported. In addition, there is no counterpart in WinRT to WinSock's select() function, so there is no way to call select() off of a WinRT socket object. I would therefore like to briefly summarize what my company's needs are, what problems I've encountered, and a suggested solution for having ASIO support WinRT. Here are our corporate library's (let's call it CORLIB) needs: (*) Our goal is to build our Boost-based library (i.e., CORLIB) for Windows Phone 8.1. (*) CORLIB refers to Boost sockets in a cross-platform fashion (e.g., using the basic_stream_socket class as an abstraction via boost::asio::ip::tcp::socket). (*) CORLIB uses the boost::asio::ip::tcp::acceptor object in portions of its code. (*) CORLIB also calls the bind() socket function (*) CORLIB uses the BSD/Winsock functions select() and bind(), among other functions, to implement its logic Here are the problems: (*) The socket_acceptor_service class #includes null_socket_service.hpp to implement the acceptor object for WinRT. In other words, the acceptor object is not implemented for WinRT. (*) The winrt_ssocket_service_base class does not implement the listen() function, something that must be implemented to support the acceptor object. (*) The winrt_ssocket_service class implements native_handle_type as Windows::Networking::Sockets::StreamSocket^. There is no WinRT analog for the BSD/WinSock select() function, so CORLIB has no way of performing a select on the StreamSocket object. Since select() is critical to CORLIB, StreamSocket^ is unacceptable. We believe that winrt_ssocket_service must be implemented using WinSock (almost completely supported by Windows Phone 8.1) rather than Windows::Networking::Sockets, because the select() function is unimplementable using the WinRT hierarchy. We therefore propose creating a new socket service class for WinRT (we will refer to this new service class as winrt_winsock_socket_service) . This new service will be similar to reactive_socket_service: the stream_socket_service.hpp include file shows the following: #if defined(BOOST_ASIO_WINDOWS_RUNTIME) # include <boost/asio/detail/winrt_ssocket_service.hpp> #elif defined(BOOST_ASIO_HAS_IOCP) # include <boost/asio/detail/win_iocp_socket_service.hpp> #else # include <boost/asio/detail/reactive_socket_service.hpp> #endif Since we want to return to WinSock-based sockets for WinRT, we therefore want to model the Winsock-based WinRT implementation on reactive_socket_service, making changes for WinRT when necessary. Because Windows Phone 8.1 supports Winsock2, including bind(), listen(), and select(), we should be able to support WinRT via WinSock. This class will not make any use of WinRT's new socket classes.

4 5

Re: [boost] ASIO does not fully support Windows Runtime and a suggestion for providing support
by Moshe Rubin 16 Jan '15

16 Jan '15

>> I highly object to the tone of your response. Bringing up a matter on >> this mailing list related to a Boost library is not a command for anyone >> to do anything. By responding the way you have done you are discouraging >> people with issues from using Boost mailing lists to start a discussion >> about a particular library. > I apologise if I have offended anyone on the list, including you > Edward. My thanks to Edward for standing up for a relatively new poster to this mailing list. There was absolutely no malicious or similar intention in my post, and certainly no "commanding and impatient tone". My intention was to improve ASIO, which is an incredible technological achievement. Our needs for a ported Boost for WinRT, as the needs of many others, are immediate, so I used the methods known to me, including posting to this mailing list. If I had a nickel for every WinRT developer pining for a complete port of Boost for WinRT, I'd probably be a rich man <g>. > However, there is an etiquette when dealing with deficiencies in open > source libraries. You first raise the issue with the library's > maintainers before going onto public lists - and before I replied to > the OP, I checked the github ASIO issue tracker and the Boost issue > tracker and found no mention of the deficiencies. It may be the case > that the OP has spoken to Chris by private email, but his post did > not indicate that. I am willing to learn the ropes and thank you for pointing out the correct procedure. As a matter of fact, I used a two-pronged tactic just in case and sent the same email to Chris in parallel (see his response below). > Furthermore, Chris fairly bluntly stated in the > ASIO release notes which added WinRT support that that support would > be limited, and he went into some detail as to how and why. That > would strongly suggests that the maintainer is well aware of the > limitations, and has a strong idea of what should be done about them > (if anything). Moreover, if he has left out a particular support for > something, he may well have very good reasons for that, including the > cost benefit reason. Indeed, I had not checked the ASIO release notes, and now know that that is most important. Reading them now, I see that Chris limited his port. As a WinRT developer, I know why he decided to do so. > So, go raise it with the maintainer first, and that's probably best > done as I mentioned via the ASIO github issue tracker which Chris > definitely responds quickly to. If the maintainer refuses to support > what you need, *then* come onto this list to see if anyone else is > having the same problem, *then* see if you can put together a > coalition of the willing. However, to be honest, I think the > maintainer will be happy to improve WinRT support, you just need to > prearrange what form he'd prefer it to come in. Here is Chris's courteous reply to me: <quote> Thanks for your email. I was not aware that Windows Phone now supports Winsock. This is great news. However, I am a bit confused by your proposed design. I don't believe we need a new socket service at all. If Windows Phone now supports Winsock then we simply need to prevent BOOST_ASIO_WINDOWS_RUNTIME from being defined - see asio/detail/config.hpp. Then, provided that BOOST_ASIO_WINDOWS *is* defined and BOOST_ASIO_HAS_IOCP is *not*, it will use the existing select()-based reactive_socket_service backend. This backend is already supported on Windows, and was used in the past to support Windows 9x and WinCE. I suggest you start by modifying asio/detail/config.hpp to make those changes, and then see what errors happen after that. There will most likely be other changes needed to work around Windows API functions that are still unsupported on Windows Phone. Cheers, Chris </quote> > And BTW, after you've talked to Chris and gotten green lit by him, > absolutely do ping this list with what you've agreed to do and ask > for feedback on it. The people I'm currently contracting for would be > very interested in improved WinRT support in ASIO. I'm sure so would > others on the asio-users ML. And as ASIO is going to be the > Networking TS, I daresay so would Microsoft, indeed you might even > get some improvements to WinRT to help ASIO along - we have the main > Microsoft engineer who ported Boost to WinRT on this mailing list. So here I have a question: when I've followed up on Chris's suggestions and have ASIO working for ASIO, what should I do next? Return to the mailing list to announce the fact and ask for feed as you suggest, or schedule a GitHub pull request? I have recently been in contact with Steven Gates, who has been very helpful on my quest of porting Boost for WinRT. In conclusion, Niall, I thank you for educating me on the etiquette on Open Source public mailing lists. I trust you've also learned not to pull the trigger too quickly. Moshe

6 5

Regarding Contribution to Boost Library
by Siddharth Agrawal 16 Jan '15

16 Jan '15

Hello all, Myself Siddharth Agrawal, I have been using boost library since 1 year.Now I want to contribute to the development of this library. Can anyone guide me where should I start. I would be grateful for this. Moreover I also want to know the github page of Boost. Regards, Siddharth Agrawal.

3 3

Interest in a FIX Protocol Library?
by Marius Dobrea 16 Jan '15

16 Jan '15

Hello Boost, I have been following the boost email lists for a while now and would like to contribute to Boost too. Since it matches at best my experience it would be probably most beneficial if I contribute to a BOOST/FIX library. FIX comes from the "Financial Information eXchange" Protocol and it represents a standard that is used a lot in the Financial Industry. For more information see the related Web Site: http://www.fixtradingcommunity.org. Firstly I would like to ask the community if there is interest in such a library and if anyone is doing any work on it. It seems to me that although there are a lot of firms and institutions in the world providing software or using FIX there are too few open source C++ libraries for that. Secondly I would like to receive feedback on what functionality would be interesting to be part of this library. For instance it could contain: - basic components that can be used to build bigger blocks: e.g.: raw data iterators, message components, field types; - conversion functions from FIX to C++ types and vice versa; - code generators for Messages, Enums, Constants based on XML specification files; - implementations for various FIX Session types: Tag-Value, FAST, FIXP, user defined messages, etc; - transformers which based on some configuration could convert messages automatically between various FIX versions; - message persistence, etc. FIX is very well documented and as such various functionality could be probably easily split into interesting projects that are to be part of the GSoC. Let me know what you think. Thanks, Marius Dobrea

13 17

[sync] has no master branch?
by Peter Dimov 15 Jan '15

15 Jan '15

The module libs/sync has no master branch, why?

2 6

[timer] clang warning
by Peter Dimov 15 Jan '15

15 Jan '15

..\..\..\include/boost/timer/timer.hpp:44:43: warning: 'long long' is a C++11 extension [-Wc++11-long-long] void clear() { wall = user = system = 0LL; } ^ The fix in this case appears trivial, just remove the LL.

2 1

Unmerged changes in develop
by Peter Dimov 15 Jan '15

15 Jan '15

Many libraries have unmerged changes in their develop branches. Some of those are legitimate, many aren't. What follows is a list of the submodules for which git log master..develop reports something, created by git submodule foreach "git log -n 1 --oneline origin/master..origin/develop || :" and then edited slightly by me. Entering 'libs/accumulators' 2bf02f3 Merge pull request #2 from danieljames/metadata Entering 'libs/algorithm' d473435 Added more general power functionality as requested by Sean Parent. Also added enable_if to make sure the exponent is an integral type. Entering 'libs/array' 0d4fa27 Merge pull request #3 from boostorg/pull_request/remove_hash_fwd Entering 'libs/atomic' 427a757 Merge pull request #4 from jhunold/test_dependency Entering 'libs/bimap' dd4e612 Correct broken links to C++ standard papers. Refs #9212. Entering 'libs/chrono' d7478b9 move from math to integer for gcd(). Entering 'libs/concept_check' bb9257a Remove executable status from a bunch of source files Entering 'libs/config' 06aa40a Remove requirement that BOOST_MSVC_ENABLE_2014_JUN_CTP be defined to get the correct BOOST_NO_CXX11_* macros for VC++ 14.0 (aka 2015). Entering 'libs/container' 6932417 Support types with std::allocator_arg_at with boost::container::scoped_allocator_adaptor Entering 'libs/context' ac1b845 usei consistent use of BOOST_ASSERT Entering 'libs/conversion' 84ab592 Merge pull request #7 from Boris-Rasin/synopsis Entering 'libs/convert' f066fac turning std=c++11 on Entering 'libs/core' 2beeb73 Fixed a typo in the comment. Entering 'libs/coroutine' 9814084 remove feature segmented stack (already defined in boost.context) Entering 'libs/crc' 3de6617 Merge pull request #1 from danieljames/metadata Entering 'libs/date_time' ca30f6a Documentation patch from 'faithandbrave' Entering 'libs/detail' fcaf168 Initial commit if lightweight_test_report.hpp, aimed at making it easier for users to supply sample programs in bug reports. First use will be in filesystem. Entering 'libs/dynamic_bitset' 225064d Patch by Riccardo Marcangelo: Added a pop_back() member function which decreases the size of the bitset by one Entering 'libs/endian' 810f545 Work-in-progress, including various bug fixes and doc updates. Entering 'libs/exception' c1f6b74 Merge pull request #5 from danieljames/metadata Entering 'libs/filesystem' 96d5cdd Remove test_folder. Content is now in branch test-files/utf-8, so that master and develop conform to Boost file naming policy. Entering 'libs/foreach' 3bc8f66 Merge pull request #2 from danieljames/metadata Entering 'libs/format' 5826c68 Fix typo. Patch from kylelutz Entering 'libs/function' 157aaea Merge pull request #4 from apolukhin/rvalue_params Entering 'libs/function_types' caed0a6 Correct broken links to C++ standard papers. Refs #9212. Entering 'libs/functional' a478186 Fix version number in release notes. Entering 'libs/fusion' af1bc25 - disabling test for now (todo later) - removing irrelevant tuple test Entering 'libs/geometry' 9b6be5f [point] assign values differently such that: no warning is given, and explicit can be used for one constructor only Entering 'libs/gil' 1618df0 Merge pull request #12 from danieljames/metadata Entering 'libs/graph' 2573fbb Fix warning on const return by value. Entering 'libs/graph_parallel' 17214e8 Merge pull request #6 from michaelopitz/develop Entering 'libs/io' b3e349c Merge pull request #1 from danieljames/metadata Entering 'libs/iostreams' d702307 Correct broken links to C++ standard papers. Refs #9212. Entering 'libs/iterator' ec7d398 Merge pull request #10 from Flast/pr/ref-to-ref/dr106 Entering 'libs/lambda' 545b6af Merge pull request #1 from jzmaddock/patch-2 Entering 'libs/lockfree' 39cc67a lockfree: spsc_queue compile fix Entering 'libs/logic' b3adfec Merge pull request #2 from apolukhin/develop Entering 'libs/math' 9561623 [Beta/Gamma]Fix concept failures caused by previous commit. Entering 'libs/mpi' b4e8640 Enable new test now that missing source has been added. Entering 'libs/mpl' 6a0f617 Revert "Merge pull request #11 from Lastique/modularization" Entering 'libs/multi_array' 5578fc3 Merge pull request #6 from MarcelRaad/patch-1 Entering 'libs/numeric/conversion' c90517d Merge pull request #3 from danieljames/metadata Entering 'libs/numeric/interval' 538299d Apply https://github.com/boostorg/interval/pull/1 manually; qualify four calls to 'to_int' with 'this->' Entering 'libs/numeric/odeint' d69cba8 Merge pull request #5 from danieljames/metadata Entering 'libs/numeric/ublas' 12f6c6c Merge pull request #16 from danieljames/develop Entering 'libs/optional' a8a6be0 More tests migrated to core/minimal_test Entering 'libs/parameter' 54854d4 Correct broken links to C++ standard papers. Refs #9212. Entering 'libs/phoenix' e168b28 Updated preprocessed files Entering 'libs/predef' 84967e3 Add missing BOOST_PREDEF_MAKE_0X_VVRRPP macro (thanks ro Erik Lindahl for finding it). Entering 'libs/preprocessor' fd135a0 Added BOOST_PP_LIST_SIZE_D to list of re-entrant macros. Entering 'libs/program_options' 0c01e9a Add testing for implicit_values and non-consuming of separate tokens. Entering 'libs/property_map' ba0bed2 Merge pull request #2 from danieljames/metadata Entering 'libs/property_tree' 24125b4 Merge pull request #6 from danieljames/metadata Entering 'libs/proto' 8566061 get lambda example compiling on clang Entering 'libs/ptr_container' 9ed3379 Merge pull request #1 from BenPope/develop Entering 'libs/python' 6b7e0cc Remove all references to now defunct (and removed) header. Entering 'libs/random' a8aed49 Use the right upper bound for the exponent. Entering 'libs/range' 4f3bdbe Merge pull request #24 from steveire/remove-algorithm-dep Entering 'libs/ratio' 591a1e6 Merge pull request #2 from danieljames/fix-json Entering 'libs/regex' 39aa10d Fix for: https://github.com/boostorg/regex/pull/9 Entering 'libs/serialization' 594541b Merge pull request #4 from danieljames/metadata Entering 'libs/signals' 7dc7b47 Merge pull request #4 from danieljames/metadata Entering 'libs/smart_ptr' f65c57d Fix explicit instantiation regression Entering 'libs/spirit' f51566b Merge pull request #75 from mloskot/develop Entering 'libs/statechart' c9cf783 Merge pull request #1 from apolukhin/develop Entering 'libs/static_assert' bb3cc11 Merge pull request #2 from mgaunard/clang_warning_fix Entering 'libs/test' bf1c122 Now just "using" Entering 'libs/thread' 2c028aa fix more erros after Boost.Test commit. Entering 'libs/throw_exception' a9de81a Merge branch 'master' into develop Entering 'libs/timer' f4ec9cc Merge pull request #1 from danieljames/metadata Entering 'libs/tokenizer' 2fa9f44 Merge pull request #4 from Lastique/patch-1 Entering 'libs/tr1' 9f28b87 Merge pull request #2 from danieljames/metadata Entering 'libs/tti' 7b13a81 Merge pull request #1 from danieljames/metadata Entering 'libs/tuple' b54dd80 Merge pull request #6 from K-ballo/boostbook Entering 'libs/type_erasure' e92682a VC12's variadic templates have some bugs. Fall back on the PP implementation for some components. Entering 'libs/type_index' 8558fd6 remove the always failing testing_crossmodule_anonymous_no_rtti test from test suite and add notes for users about emulation limitations testing Entering 'libs/typeof' 4e34737 TypeOf: Fix if/elif chain after msvc 6/7 removal. Entering 'libs/unordered' 68eb654 Merge pull request #4 from tempoz/patch-2 Entering 'libs/uuid' d233193 Fixed compilation. Entering 'libs/variant' e00c75c Continue fixes, pointed out by Adam Wulkiewicz: removed unnecessary reference_content.hpp include, added missing static_assert.hpp include Entering 'libs/wave' bb0adbf Merge pull request #2 from danieljames/metadata Entering 'libs/xpressive' 7377713 Merge pull request #3 from danieljames/metadata Entering 'tools/build' f5b31b3 Block signals to end of exec_cmd. Entering 'tools/quickbook' b93c2a7 Use quickbook 1.7 for documentation.

3 6

[ratio] clang warning
by Peter Dimov 15 Jan '15

15 Jan '15

Ratio gives a warning under Clang: ..\..\..\include/boost/ratio/ratio_fwd.hpp:87:58: warning: 'long long' is a C++11 extension [-Wc++11-long-long] typedef ratio<BOOST_RATIO_INTMAX_C(1000000000000000000), BOOST_RATIO_INTMAX_C(1)> exa; ^ ..\..\..\include/boost/ratio/config.hpp:47:33: note: expanded from macro 'BOOST_RATIO_INTMAX_C' #define BOOST_RATIO_INTMAX_C(a) INTMAX_C(a) ^ ..\..\..\include/boost/cstdint.hpp:66:26: note: expanded from macro 'INTMAX_C' # define INTMAX_C(c) c##LL ^ I'm not sure how this can be avoided though.

2 2

Re: [boost] [compute]/ Futures Some remarks
by Antonio Colino 15 Jan '15

15 Jan '15

> > On 01/14/2015 10:46 PM, Antonio Colino wrote: > > I have a flawless implementation of this concept I am very proud of. Is any one willing to critique it? > > On 01/14/2015 10:46 PM,?Thomas Heller?wrote: > > Wanna share it? Which concept are you refering to? > > I was hoping to share this lib, if i could generate any interest in a copyable hpc version of packaged_task > On Jan 2015 20:36:40,?Thomas Heller?wrote: > Absolutely! Note that there are already a few out there doing exactly what > you described (HPX and Habanero++ come to my mind here). What would be the best way to arrange this?

1 0

Marking explicit failures -- need help
by Andrzej Krzemienski 15 Jan '15

15 Jan '15

Hi All, I would like to make some regression tests as expected to fail in explicit-failures-markup.xml, but I have the following problem. Not sure if this is specific to Optional tests: http://www.boost.org/development/tests/develop/developer/optional.html I have two "columns" with the same toolset label "gcc-4.4.7" from tester "Sandia". On one the test passes, on the other: it fails. This is because on one C++0x is enabled. But I cannot tell it from the toolset label alone, and therefore I cannot make the correct entry in failures-markup.xml: either I mark too much or too little. Does anyone know away around it? Can you mark failures based on something else than toolset name? Regards, Andrzej

1 1

Re: [boost] [compute]/ Futures Some remarks
by Antonio Colino 15 Jan '15

15 Jan '15

On 01/14/2015 10:46 PM, Antonio Colino wrote: > I have a flawless implementation of this concept I am very proud of. Is any one willing to critique it? On 01/14/2015 10:46 PM,?Thomas Heller?wrote: > Wanna share it? Which concept are you refering to? I was hoping to share this lib, if i could generate any interest in a copyable hpc version of packaged_task

2 1

Re: [boost] [compute]/ Futures Some remarks
by Antonio Colino 15 Jan '15

15 Jan '15

On 01/14/2015 10:46 PM, Antonio Colino wrote: > I have a flawless implementation of this concept I am very proud of. Is any one willing to critique it? On 01/14/2015 10:46 PM, Thomas Heller wrote: > Wanna share it? Which concept are you refering to? I was referring to both type traits on lambdas and an implementation of a tasking library that is allocator free, that you can reset function arguments reuse the task, reuse threads, reset arguments on lambdas, copy tasks while running and still always get accurate information. Thread safe and lock free. Basically a scheduler, task implementation that dare i say rivals boost bind and std::packaged_task. As it can bind any set of arguments to a function , reuse the same function to create new states . It is the core of a bigger lib I have been working on that sends these tasks across machine bounds ( hpc ) and onto the gpu.

1 0

Tests that enable <warnings-as-errors>on
by Peter Dimov 15 Jan '15

15 Jan '15

Some test suites, for example Pool and Units, use '<warnings-as-errors>on' in their project requirements, to test for a warning-free compilation. Pool, f.ex. has project : requrements <toolset>gcc:<warnings-as-errors>on <toolset>msvc:<warnings-as-errors>on ; (among others.) This, however, is propagated to dependencies, so that in [ run test_threading.cpp : : : <threading>multi <library>/boost/thread//boost_thread ] Boost.Thread is also built with '<warnings-as-errors>on', which fails. (In addition, some other tests also fail because of warnings.) So I tried to use '<warnings-as-errors>off' only for some tests, but I was unable to come up with a syntax that worked. Putting -<toolset>msvc:<warnings-as-errors>on in the test requirements didn't (no effect). <toolset>msvc:<warnings-as-errors>off didn't (conflict). -<warnings-as-errors>on didn't (no effect). -<warnings-as-errors>on <warnings-as-errors>off didn't (no effect). Is there a way to override the project requirements from the run rule?

2 1

[thread] fails to build on Cygwin with weird errors
by Peter Dimov 15 Jan '15

15 Jan '15

Vicente, I'm trying to get the pool tests up and running (they fail across the board, at least on develop), and one of them requires Thread, which fails to build under g++/Cygwin. The errors are of the kind ..\..\..\libs\thread\src\win32\thread.cpp: In member function 'bool boost::thread::start_thread_noexcept()': ..\..\..\libs\thread\src\win32\thread.cpp:337:127: error: 'struct boost::detail::thread_data_base' has no member named 'id' uintptr_t const new_thread=_beginthreadex(0,0,&thread_start_function,thread_info.get(),CREATE_SUSPENDED,&thread_info->id); which leads me to think that, on Cygwin, you're using the POSIX header with the Win32 source file.

2 2

Re: [boost] [compute]/ Futures Some remarks
by Antonio Colino 15 Jan '15

15 Jan '15

I have a flawless implementation of this concept I am very proud of. Is any one willing to critique it?

2 1

Re: [boost] boost interval arithmetic
by Marc Glisse 14 Jan '15

14 Jan '15

(please keep the conversation on the list) On Wed, 14 Jan 2015, Павел Кудан wrote: > Dear Marc, > > Thank you for your answer, I also tried to contact Mr.Gubenko, have no information about other maintainers. Please, excuse my bad English, I will try to explain in more detail, please, ask if something will be uncertain. I thought the maintainers would be the 3 authors. > Boost interval library was planned as extension of mathematical functions on float/double/double long or other singe numeric values to operations on intervals. The problem is that intervals have some specific. For example, if float value can be either > either < or = some other float value (statement ! (a>b) == (a <= b) is always true), for intervals it is not correct. Intervals can also overlap. That means that it is not possible for pair of overlapping intervals to say certainly which of them are greater than other. It is the intermediate situation, which is impossible with original single float values. > > And boost interval class has comparison operators and user can expect that they will behave in similar way with usual float comparison operators. > > For that reason, the behaviour of that comparison operators was made changeable and depends on some kind of policy, defined by user. Default behaviour is to throw exception when such intermediate situation (not possible for single float values) takes place. > > That was very wise solution, especially useful in very probable case, when some programmer will try to adapt some existing code with float calculation just changing type of value to boost interval. He will get exception in than exceptional situation - when usual float comparison operator is not applicable any more. > > That is OK. > > > > But as well boost interval class defines mathematical functions and operators. And user can expect that they also will behave similarly to usual float comparison operators. But great disappointment and multiple possible errors which is hard to locate is waiting for him here. Because it is not so. Arithmetic operators behave in completely different manner. > > Let's look on of most basic operator =/ and see what it is doing. > > But before let's see what is division of intervals and what is it's result. > > Boost interval class has two function - division_part1() and division_part2(). It is correct as when you divide one interval with another, the result will be single interval or a pair of intervals. The last situation takes place when in statement A / B, interval B cross a zero. That is not normal for intervals to have a pair of intervals as a result of division, but it is exceptional for single float numeric division. > > Now let's get back to /= operator and watch what he will do in such case. > > Let A = [1,2] and B = [-1, 1] > > and let's see what we will get after A /= B and what we should get. > > The true result of division in that case will be a union of pair of intervals [-infinity, -1] and [2, -infinity] Actually, [-inf,-1][1,+inf] > Interval /= operator, naturally, must return one interval. It is, obviously, impossible in this case - to return one of two. Again intermediate situation, not applicable to single float calculations. Again, throwing exception must be a result to let user know that he does not know what he are really doing. The same behaviour, as comparison operators. But it is not so. > > Instead of such natural behaviour, /= operator of boost interval class are doing impossible thing. It silently decides for itself which one of two parts of whole result to return and kill another part of whole solution somewhere under the scene. > > The result of A /= B will be [-infinity, -1]. Not correct result - as it is not complete. One of to parts is missing. Did you really observe that? If so, it is a bug. [1,2]/[-1,1] is supposed to give [-inf,inf] (and it does indeed, in my tests), which certainly contains the right value ;-) If you have a testcase that shows differently, it would be good to open a bug report on trac. > Very very bad operator behaviour. User get not correct result and even does not know that it is so. It will be hard to find when this error is located, and when it will be done, library user will not think that he should know better what he are doing and learn some basics of interval arithmetic - no, he will accuse boost interval as part and boost as whole for bugs in libraries implementation. U nfairly , of course, but who cares. > > > > To correct it, at least, arithmetic operators and functions of interval class must behave similarly to comparison operators - throw exception in situations, not applicable for single float calculations. > > That is what I meant when said: "The difference in behaviour of comparison operators and basic arithmetic operators looks as probable misconception." > > > > I know, it is hard to understand, especially because bad English, but I hope it is important and hope it will help. -- Marc Glisse

2 2

Re: [boost] Futures (was: Re: [compute] Some remarks)
by Antonio Colino 14 Jan '15

14 Jan '15

Concerning std::futures and promises, my thought is wrapping an immutable state in a task, nither future or promise, but with elements of both. Creating a mutex from an asm lock cmpxchg wrapped in c ( available most platforms ) to a shared_ptr gives you a copyable mutex. Not that it matters, but if the state manager ensures a swap every time the arguments are updated, and the state has a ref count destructor, a value storage, function/lambda/member func/functor storage, the effect is an immutable state. once the args are set nothing can change but the execute function or function brackets, a flag in the state ensures that the func will only execute once ( all flags set by single asm instruction xchg, wrapped in c ). this task , or promise if you like, is now copyable, and doesn't require an allocator as the internal state is set by setting the arguments and the state ptr and can be created then. Every time the task/ promise gets copied the shell only exists to point to the state. Having a generic function that wraps any func call in a std::function<void()> using a lambda , works nicely for a basic way to fill a queue generically. In the end you only have two exposed objects. A task and a scheduler. No mutexes, futures, promises, or any locking mechanisms of any kind. The task implementation I'm speaking of also accepts lambdas, and can reset there arguments. The thought is creating the shell (task , promise, whatever) once. Then setting the arguments many times. Each time it would internally create a new state, the user still has to take care of the memory, less the ref count get to zero, but a simple vector does nicely. Since it is all wrapped in the copyable task/promise, it is transparent to the user. So... task(any function in with or without args), task.set_args, scheduler.queTask, and go. The scheduler is just a thread grouping dictated by the user or by the hardware concurrency as a default. The result can be retrieved directly through the task or it can create a future as well or fill an existing one with the original future ref in the state. Don't really need it but... if it must be future/promise. Biggest problem i had was dealing with the lambda and functor case intuitively and cross platform. Functions and member functions were a snap.

1 0

PDF versions of Quickbook generated documentation - Do you like the serif font?
by Paul A. Bristow 14 Jan '15

14 Jan '15

I've noted that for documentation using the Quickbook toolchain, we use a serif font (Times Roman?) for the PDF, but a sans serif for the equivalent HTML version. Is there a reason for this? Should they not be the same font? (So that they look the same?) Which do we prefer? Should we change either or both? Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830

2 2

BOOST_ASIO_SEPARATE_COMPILATION linker error
by Arun.Ramasamy＠high5games.com 14 Jan '15

14 Jan '15

HI, I'm trying to build boost 1.47's asio library with the BOOST_ASIO_SEPARATE_COMPILATION macro in windows 7, 32-bit, VS 2010. With this macro, the asio library can be included and built easily without building all of boost or using bjam. However, I get the following linker error: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system::system_category(void)" (?system_category@system@boost@@YAABVerror_category@12@XZ) referenced in function "public: __thiscall boost::system::error_code::error_code(void)" (??0error_code@system@boost@@QAE@XZ) unresolved external symbol "class boost::system::error_category const & __cdecl boost::system::generic_category(void)" (?generic_category@system@boost@@YAABVerror_category@12@XZ) referenced in function "void __cdecl boost::system::`dynamic initializer for 'posix_category''(void)" (??__Eposix_category@system@boost@@YAXXZ) 1> Basically the functions boost::system::system_category and boost::system::generic_category aren't defined anywhere. I can't find the implementation of these functions in boost source when I tried grepping it. Should I just use bjam to build the asio library. Thanks arun

3 2

Re: [boost] [build] Test marked as compile-fail is now reported as a failure.
by Adam Wulkiewicz 13 Jan '15

13 Jan '15

Hi Vladimir 2015-01-12 7:26 GMT+01:00 Vladimir Prus <vladimir(a)codesourcery.com>: > > Hi Adam, > > On 01/11/2015 10:38 PM, Adam Wulkiewicz wrote: > >> Hi, >> >> Since yesterday one test marked as compile-fail is now reported as a >> failure on the regression tests page. >> >> It's the test: rtree_values_invalid >> on the page: http://www.boost.org/development/tests/develop/ >> developer/geometry-index.html >> >> Surprisingly other tests aren't. >> see e.g.: geographic_custom_point_with_wrong_units >> on the page: http://www.boost.org/development/tests/develop/ >> developer/geometry.html >> > > Why is it surprising that test A fails while test B does not? Are these > exactly identical > tests? > They're both expected to fail to compile. > > They seem to be defined the same way in the Jamfile: >> https://github.com/boostorg/geometry/blob/develop/index/ >> test/rtree/Jamfile.v2 >> https://github.com/boostorg/geometry/blob/develop/test/ >> point_concept/Jamfile.v2 >> > > Could it be that the problem with the actual tested functionality. > AFAIU no because the test is reported as a fail only if it's expected to compile/link/run but it fails to compile/link/run. If the situation is the opposite (expected to fail but doesn't fail) the test is reported as a pass (with dark green background). Otherwise the test should be reported as a "regular" pass. > > AFAIS the oldest run when it failed was of the runner: >> teeks99-03c-Ubuntu12.04-64 on Sat, 10 Jan 2015 02:05:44. >> On Fri, 09 Jan 2015 18:36:55 (teeks99-08b-win2012R2-64on64) everything >> was ok. >> >> Furthermore when run locally it's also reported as a failure. Some time >> ago of course "(failed-as-expected)" message was printed instead. >> Do you have any idea what may be wrong? >> > > Looking at > > http://www.boost.org/development/tests/develop/ > developer/output/BP%20x86_64%20C++11-boost-bin-v2-libs- > geometry-index-test-rtree- rtree_values_invalid-test- > clang-linux-3-5~c14_libc++-debug-debug-symbols-off.html > > It does look indeed that complication is successfull, while it should fail > for the test to pass. If by successful you mean "the compiler output is present" then indeed it isn't. However it's not always the case, see: http://www.boost.org/development/tests/develop/developer/output/BP%20x86_64… http://www.boost.org/development/tests/develop/developer/output/trippels_gc… Though I can't see any error message there, only warnings. But this is not the first time I see something like this on the regression tests page. However the message about trimming of the output is displayed only for the first of the tests mentioned above. > Locally for me, with gcc, the > compilation fails, and the test is deemed passing, so I can't see any > Boost.Build malfunction here. > Yes, the cause may be located elsewhere, in Geometry, Regression, Test, etc. For a clean run I'm now unable to build the tests due to some undefined references but the problem is most likely located elsewhere. > Am I missing something? Or am I? Regards, Adam

3 6

Re: [boost] [Boost-testing] Linux regression test runners - What do devs want?
by Blower, Melanie 13 Jan '15

13 Jan '15

Niklas, How do you compare the results of running the same compiler on Linux and QNX? Do you just eyeball the report on the website, or do you use a script to compare the test results on the filesystem? Thanks and regards, Melanie -----Original Message----- From: Boost-Testing [mailto:boost-testing-bounces@lists.boost.org] On Behalf Of Niklas Angare Sent: Tuesday, January 13, 2015 7:09 AM To: boost-testing(a)lists.boost.org Cc: boost(a)lists.boost.org Subject: Re: [Boost-testing] Linux regression test runners - What do devs want? "Tom Kent" <lists(a)teeks99.com> wrote: > Instead of running lots of different versions, I was thinking about > running various compatibility options of the two main compilers...I've > seen some other test runners with things like libc++, c++11, c++14, > etc. My real question, would developers be better served by these > options than different versions? Would they prefer both with longer > revisit times between each test type? Other thoughts? My runners use gcc 4.4(.2) (in gnu++0x mode) on QNX, and it's useful to be able to compare to the same compiler running on Linux. I'm sure it's the same for other non-Linux environments such as MinGW. Currently there are other runners that match my compiler configuration better than yours do, but you get the idea. Regards, Niklas Angare _______________________________________________ Boost-Testing mailing list Boost-Testing(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-testing

1 0

TravisCI and Coveralls integration instructions
by Antony Polukhin 12 Jan '15

12 Jan '15

Hi all, The following step by step instruction https://svn.boost.org/trac/boost/wiki/TravisCoverals may be useful for those of you who want to: * make sure that tests cover all the code lines * make the README.md more colorful and useful * use additional testing infrastructure Here are some examples of how the results looks like: * https://github.com/boostorg/variant#test-results * https://github.com/boostorg/type_index#test-results P.S.: Shall I add this tutorial to "Guidelines" or to the "Infrastructure" section of the Wiki? -- Best regards, Antony Polukhin

2 1

[boost.fiber] regarding to migration of fibers between threads?!
by Oliver Kowalke 12 Jan '15

12 Jan '15

Hello, boost.fiber was reviewed in January 2014 and now I've finished the requested changes. Unfortunately the migration of fibers between threads is not stable yet, but synchronizing fibers running in different threads works. I'd like to know if fiber migration is absolute necessary to pass the next review or might it be acceptable to finish this feature later. so long, Oliver

2 1

[mixin] Library name
by Matus Chochlik 12 Jan '15

12 Jan '15

On Mon, Jan 12, 2015 at 1:32 PM, Klaim - Joël Lamotte <mjklaim(a)gmail.com> wrote: > On Mon, Jan 12, 2015 at 1:21 PM, Borislav Stanimirov <b.stanimirov(a)abv.bg> > wrote: > > > > > * EntityComponent - not great since it doesn't exactly follow the > > entity-component-system pattern, although it can be said that it allows > the > > construction of entities from components. > > > > > As long as you consider that it is not implementing the ECS pattern, it > shouldn't use this name indeed. > > +1 If the `Mixin` name is 'bad' because it is used to describe something different in C++ then `EntityComponent` is 'bad' for the same reason

1 0

Re: [boost] GSoC Proposal[game dev and boost c++]
by Mudit Sharma 12 Jan '15

12 Jan '15

Respected all, As we all know in game development Rotation and Translation play the most important role..I propose to implement either[whichever is relevant to boost] using boost geomtry(of course) and uBLAS(will make calculations easier)... Can this be taken up as a project for summers?

3 2

[Mixin] Some comments
by Vicente J. Botet Escriba 12 Jan '15

12 Jan '15

Hi, First of all, I want to say that I like your library too much. It is quite close to a library I was working one EntityRoleSubject. You library could be extended to to take in account the subjective programming paradigm (see below). I have some comments/remarks/questions: * I have some doubts about the name mixin. What a mixin has more than a facet or an aspect? Mixins in C++ have a specific mean in the context of CRTP. Why have you chosen the mixin name? * The construction of the mixins in the tutorial is done always with the default constructor. Can we do emplace construction? How can you ensure the invariants of some mixing classes? * The priority of the messages doens't compose well. The user needs to have a global view of the application so that it can assign the correct priority. I have not a better suggestion, but I think that this issue would need more insight. * Respect to subjective programming: it would be great to be able to create subject from an entity so that only the mixins of the subject would play when a reference to this subject is addressed. subject<Mix_1, .... Mix_n> s (o); o.get<Mix_k>() works as expected. o.get<Other>() compile fails if not equal to any Mix_k * The macro bm_this :( * I would like to see what is behind the scenes the different macros in an implementation section. * The entity-mixin relation is not recursive, that is, a mixin can not have associated mixins, or can them? * Can a mixin D inherit from another mixin B? Could the mixing D be retrieved when getting the mixing B? mutate(o).add<D>; o.get<B>()->f() // f been a virtual function on B? * The example of the mixin headphones_player show that the play() implementation makes use of get_sound() provided by other mixins. This dependency is not explicit. I would expect to be able to say that headphones_player depends on another mixing providing the get_sound message. That's all for now.I will come back later when i will read more. A BTW, the reference documentation doesn't contain the add<M>/get<M> mutate functions? Best, Vicente

4 11

[chrono] Dependency on math?
by Beman Dawes 12 Jan '15

12 Jan '15

The latest dependency report shows chrono as having a dependency on math. See http://www.pdimov.com/tmp/report-develop-3b5a9f4/module-overview.html math is really big. In testing bpm, an install of timer (which depends on chrono) slowed noticeably when it got to math. Presumably the build is also much slower, although I haven't tested that yet. Is the math dependency really needed? Thanks, --Beman

7 18

[Mixin] Some comments
by Matus Chochlik 12 Jan '15

12 Jan '15

On Sun, Jan 11, 2015 at 4:02 PM, Klaim - Joël Lamotte <mjklaim(a)gmail.com> wrote: > On Sun, Jan 11, 2015 at 8:41 AM, Matus Chochlik <chochlik(a)gmail.com> > wrote: > [8<] > > > > I've been playing with some ECS designs lately and tried to implement two > > of my own [1],[2] (maybe those are among those you've already seen) (and > > sorry for the shameless plug). Based on what I've seen, if the ECS is to > be > > used according to the usage patterns you usually see in a game (or > > rendering) engine, I believe it is better for the component instances to > be > > stored together, outside of the entities (for locality of reference, > > efficient (re-)allocation, etc.). > > > > > I violently agree. > > > > The entity should IMO be just an unique identifier > > > My experiments so far reach to the same conclusion: it's the most flexible > and potentially efficient approach. > > > > and in both of my > > implementations there is a `manager` class that can be used to > > store/modify/query/remove/etc. the components of an entity. This way > > operations that are common, like execute this function (every iteration > of > > the update loop) on all entities with this set of components can be > > implemented more efficiently. > > > > In my current implementation I call the object > holding all components a "cluster". The Cluster hold one "pool" > of component by type of components. > Currently all the pools are the same type and basically are > augmented flat_maps but I recently realized that a more flexible system > could be implemented by letting the cluster user insert different kinds of > polls > depending on how he wants the component type to be memory managed ( > like a vector or like an actual pool or with allocated nodes?), how > "updates" are processed (in parallel, concurrent, jsut a loop?). > I plan to try this design in the coming months. > Ditto, In my second implementation I've defined an interface for the component storage objects (classes managing instances of components of one type in the manager). The interface is flexible enough to allow local or remote mutable/immutable storages, or storages using an RDBS, a web service, etc., to actually store the component instances. From the users' POV all this is transparent, they manipulate the components uniformly through the manager, they just need to specify what kind of storage should be used when registering the component type in a manager. > > I didn't solve the component-inter-requirements problem though, I'm not > sure > if I should implement this at all, and if yes should it be compile-time > checked > as Vincente suggests? In which case the cluster would have to know > the types it can manage at compile time too, because I see no way for > an entity to be able to be checked at compile time except for a construct > like > the suggested "subject". > I'm not sure what Vincente's use case is, but in game engines the ECS *deliberately* places very few constraints on the components and how they can be combined in an entity. The idea is that the programmer does not have enough knowledge of what the content creators or modders will want to do and statically constraining the components too much requires complete recompilation every time a change is made in the game logic accessing the ECS which is undesirable for the original content creators and usually impossible for modders. Furthermore game engines very often support modification of the ECS through scripting which again could be hindered if constraints were placed on how the components are combined. These concerns IMHO apply also on other applications, like CAD/CAM, etc. using an ECS. [8<] > > > > But having implemented several apps using this approach I find it quite > > limiting in some situations that the group of components is static. > > Sometimes it is useful (for example for debugging) to have the ability to > > add/remove component *types* on-the-fly. [2] allows this but its > > unfinished. > > > I can do that in my implementation indeed, it is helpful. > As said before I think it can be improved by allowing the user to provide > the > container of component for a type, making him chose how to manage them > as long as the container match a specific set of requirement (concept?). > > I use an abstract interface and so far the overhead from virtual function calls is not very dramatic. [8<]

3 2

[build] Test marked as compile-fail is now reported as a failure.
by Adam Wulkiewicz 12 Jan '15

12 Jan '15

Hi, Since yesterday one test marked as compile-fail is now reported as a failure on the regression tests page. It's the test: rtree_values_invalid on the page: http://www.boost.org/development/tests/develop/developer/geometry-index.html Surprisingly other tests aren't. see e.g.: geographic_custom_point_with_wrong_units on the page: http://www.boost.org/development/tests/develop/developer/geometry.html They seem to be defined the same way in the Jamfile: https://github.com/boostorg/geometry/blob/develop/index/test/rtree/Jamfile.… https://github.com/boostorg/geometry/blob/develop/test/point_concept/Jamfil… AFAIS the oldest run when it failed was of the runner: teeks99-03c-Ubuntu12.04-64 on Sat, 10 Jan 2015 02:05:44. On Fri, 09 Jan 2015 18:36:55 (teeks99-08b-win2012R2-64on64) everything was ok. Furthermore when run locally it's also reported as a failure. Some time ago of course "(failed-as-expected)" message was printed instead. Do you have any idea what may be wrong? Regards, Adam

2 1

[filesystem] Problems with UTF-8 paths in GIT.
by Rene Rivera 12 Jan '15

12 Jan '15

This commit < https://github.com/boostorg/filesystem/commit/785d521b54140763dd23ef091a18d…> is causing me some problems with some git clients. In particular the git client in Eclipse errors out with some unsupported / invalid messages. I know why those dir names are the way they are.. But we still are supposed to follow the naming rules we agreed to < http://www.boost.org/development/requirements.html#Directory_structure>. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

2 1

About a Ratio/MPL submodule and removing dependencies from Ratio/Chrono on MPL.
by Vicente J. Botet Escriba 10 Jan '15

10 Jan '15

Hi, Boost.Ratio has a logical submodule providing an extension to the standard see boost::ratio as an MPL type adding struct rational_c_tag : int_<10> {}; This submodule could be moved to the subdirectory of libs/ratio/mpl so that the users of boost::ratio, shouldn't depend on MPL. Boost.Chrono depends already on MPL, but the dependencies are really minor - see below (and can be replaced by StaticAssert and TypeTraits, so that this dependency could be removed also. Do you think removing the dependencies of Boost.Ratio and Boost.Chrono on Boost MPL has value? Best, Vicente P.S. I know that currently TypeTraits depends on MPL, but we expect to resolve this dependency already. |<boost/mpl/assert.hpp>| * from |<boost/chrono/detail/static_assert.hpp>| |<boost/mpl/bool.hpp>| * from |<boost/chrono/detail/static_assert.hpp>| |<boost/mpl/if.hpp>| * from |<boost/chrono/io/duration_get.hpp>| * from |<boost/chrono/io_v1/chrono_io.hpp>| |<boost/mpl/logical.hpp>| * from |<boost/chrono/detail/is_evenly_divisible_by.hpp>| * from |<boost/chrono/duration.hpp>|

3 2

[variant] match()
by Eelis 10 Jan '15

10 Jan '15

Boost.Variant provides access through get() and visitors, but in C++11 we can do so much better! :) For a boost::variant<A,B,C>, the attached small utility function match() lets you write: match(v, [](A & a){ cout << "it's a A!"; } [](B & b){ cout << "oh, a B!"; } [](C & c){ cout << "ah yes, a C!"; }); Return values are supported. I think this really belongs in Boost. It makes variants much more usable. Regards, Eelis P.S. I have not attempted a C++98 implementation. P.S.2. Right after finishing my implementation, I discovered another, /vastly/ more complex implementation of the same thing: https://github.com/exclipy/inline_variant_visitor I'm not sure its complexity gives that implementation any advantages.

9 26

Moving files around
by John Maddock 10 Jan '15

10 Jan '15

Can I just fire a shot across the bows before we all get too carried away moving files around here there and everywhere? *The move has to make logical sense* - reducing dependencies is a worthy goal, but not if it makes stuff harder to maintain and/or harder for the user to find what they're looking for. Let me give you a trivial example: boost/utility/declval.hpp was moved into the type_traits repository to reduce dependencies on utility. OK fair enough. But I see no tests or docs, and the docs at the very least are still in "utility". So now we have a situation where maintenance of that functionality is split over two repositories each with different maintenance teams. That's not good. Perhaps more to the point, if I'm a user and I'm looking for boost/something/whatever.hpp, it had better darn well be in package "something" or I'm going to be pretty annoyed. This applies equally to folks wanting to use "whatever.hpp" as to folks wanting to submit pull requests. In fact if the above doesn't hold I suspect that a) Folks will give up and reinvent smaller utilities for themselves. b) Use an older version of Boost ("I new where everything was there"). c) Not submit bug reports or pull requests cause they can't figure out where they should go. I guess what I'm saying is that while re-factoring is a good idea, it needs a vision to improve "discover-ability" and make Boost's structure more logical, not merely easier for a package manager. Now please do carry on as you were ;) John.

3 2

[functional] How to avoid a dependency on functional?
by Beman Dawes 10 Jan '15

10 Jan '15

Filesystem has a dependency on <boost/functional/hash_fwd.hpp> in order to supply this: inline std::size_t hash_value(const path& x) { # ifdef BOOST_WINDOWS_API std::size_t seed = 0; for(const path::value_type* it = x.c_str(); *it; ++it) hash_combine(seed, *it == '/' ? L'\\' : *it); return seed; # else // BOOST_POSIX_API return hash_range(x.native().begin(), x.native().end()); # endif } The problem with this is that functional is a heavy-weight dependency for such relatively minor feature. See http://www.pdimov.com/tmp/report-develop-3b5a9f4/module-weights.html Is there any recommended way to avoid the functional dependency? Thanks, --Beman

5 14

[Boost.Filesystem] unique_path uses a random number generator from the OS, correct?
by Ben Fritz 09 Jan '15

09 Jan '15

The reference docs for unique_path state: Remarks: Implementations are encouraged to obtain the required randomness via a cryptographically secure pseudo-random number generator, such as one provided by the operating system. I'm confused by the "implementations are encouraged to" text. Isn't Boost.Filesystem the implementation of unique_path? Specifically, it *looks like* this is provided in unique_path.cpp which will use either CryptGenRandom from the Windows API; or /dev/urandom or /dev/random on POSIX systems. This means the random number comes from system/OS utilities, and not Boost itself, correct? -- Ben Fritz

2 1

A proposal for the creation of a new module, Core Type Traits
by Peter Dimov 09 Jan '15

09 Jan '15

This is a more formal statement of the same suggestion I've already given in other threads. Currently, library developers who need type traits functionality face a choice: either to use the TypeTraits library, and make their libraries dependent on MPL, Preprocessor, TypeOf and Utility, or to duplicate its functionality locally. Similarly, developers who want to specialize a type trait on a type of theirs, even a trivial empty struct, need to include the TypeTraits headers for the traits to be specialized, which brings in MPL and Preprocessor on a header-level, and makes their module dependent on TypeTraits and its dependencies listed above. Local replication, as in Boost.Move, rightly attracts charges of code duplication, with the associated potential maintenance problems when the implementations diverge. These two problems could be avoided if we were to have core type traits whose interface consisted solely of a member integral constant called "value", without any other required members or base classes, and which were only allowed to depend on Config or StaticAssert. This solves the second problem because it will then be possible for a developer to specialize a trait, such as is_pod, by using a forward declaration of the form template< class T > struct is_pod; in the appropriate namespace, like boost::core_type_traits, and then adding his specializations: template<> struct is_pod< blank > { BOOST_STATIC_CONSTANT( bool, value = true ); }; without including ANY additional headers. If we look at the current implementation of Boost.TypeTraits, for example is_pointer, we see this: template< typename T > struct is_pointer_impl { BOOST_STATIC_CONSTANT(bool, value = (::boost::type_traits::ice_and< ::boost::detail::is_pointer_helper<typename remove_cv<T>::type>::value , ::boost::type_traits::ice_not< ::boost::is_member_pointer<T>::value >::value >::value) ); }; in namespace detail, and then this: BOOST_TT_AUX_BOOL_TRAIT_DEF1(is_pointer,T,::boost::detail::is_pointer_impl<T>::value) which takes care of everything else. Note that is_pointer_impl is EXACTLY what we need! It is the core implementation of the trait and exposes only ::value and nothing else. The full-featured boost::is_pointer is built on top of that. If detail::is_pointer_impl was called core_type_traits::is_pointer, this would immediately take care of the two problems at the top of this post, while not affecting the users of Boost.TypeTraits in any way. In particular, note that if a developer specializes detail::is_pointer_impl, is_pointer automatically picks up this specialization. Therefore, I propose that a new module, libs/core_type_traits, is created, which: - provides core type traits that only expose a member integral constant called "value" as part of its documented interface and nothing else; - allows these traits to be forward declared, without requiring header inclusion; - is not allowed to depend on anything except Config or StaticAssert; - is the place to which TypeTraits's is_pointer_impls gradually migrate, along with their tests. This - solves the dependency problems some of us are facing, - avoids unnecessary code duplication, - still allows type trait specialization, with clients of both libraries automatically picking up the specialization, - is backward compatible with respect to existing uses of Boost.TypeTraits because the new library will contain the same code and the same tests. Thank you for your attention. :-)

4 8

bpm added to tools/bpm on develop
by Peter Dimov 09 Jan '15

09 Jan '15

I've added bpm, the Boost Package Manager, to tools/bpm on develop. To build it, do b2 tools/bpm/build//install at the Boost root and b2 will build bpm with the default toolset and place it in dist/bin. To try it out, first you might want to review the fs_remove_all function in fs.cpp, or use a drive or filesystem that does not hold valuable files, :-) then make an empty directory, copy bpm(.exe) there, make a text file bpm.conf with the following line: package_path=http://www.pdimov.com/tmp/pkg-develop-1612497/ then do f.ex. "bpm install filesystem". pkg-develop-1612497 is just a sample "release" that I made by running tools\bpm\scripts\package.bat at the root of my source tree, which happened to be at revision 1612497 of develop. It therefore contains Windows line endings (and b2.exe), so it will generally not be suited for installation on non-Windows systems. A POSIX release would need to be prepared from a POSIX source tree and will probably need to install bootstrap.sh instead of b2.exe, with bpm then issuing a message that ./bootstrap.sh needs to be run. I've done my development on Windows so far and have not had time to test on POSIX.

2 3

Road to low-quality-code is paved with good intentions of dropping dependencies
by Antony Polukhin 09 Jan '15

09 Jan '15

Hi all, I've been looking through the latest changes to drop dependencies. Stuff that I saw is very frightening. For example: https://github.com/boostorg/move/blob/develop/include/boost/move/detail/typ… . Every boost release some issues are fixed in intrinsics of TypeTraits and is_move_* is_nothrow_* traits. Copy-pasting code from TypeTraits feels like loading a gun and pointing it on own foot. Another example is a sad story of boost::swap. We can not use Boost.Move here because it will add "a lot of dependencies" to Boost.Core. This leads us to nonoptimal implementation, which is sad. The Solution Almost *all* of the Boost libraries depend on TypeTraits, MPL, Core, Assert, StringRef. Language emulation features implemented in Exception, Move, StaticAssert, TypeIndex should be also widely used. hash_fwd.hpp must be used by almost all the containers and structures. So may be we should think of those libraries as of "base" libraries! I do not mean that they must be moved in a single "base" folder. I'm talking only about dependency reports: those libraries must be treated by the dependency tool as a single one and must have the level 1. Those libraries are "base", because they are the very common part of Boost framework. Not using them is more like a bad decision, reimplementing parts of them is an afwull decision. Threating them as base/common/core/main part of Boost seems reasonable. -- Best regards, Antony Polukhin

15 34

[bpm] Option to skip test dependencies?
by Beman Dawes 09 Jan '15

09 Jan '15

In looking at the Boost Package Manager [bpm] options, there is one omission I suspect users will ask for right away: an option to skip dependencies created by tests and perhaps examples. Is it possible to experiment with some simple strategy, like skipping the dependency check for "test" libraries to see what effect this has? Thanks, --Beman

2 1

ATTN library maintainers: libraries missing metadata files
by Peter Dimov 08 Jan '15

08 Jan '15

The following libraries are currently missing the metadata file meta/libraries.json, which describes the library: libs/algorithm/meta/libraries.json does not exist libs/assign/meta/libraries.json does not exist libs/bimap/meta/libraries.json does not exist libs/compatibility/meta/libraries.json does not exist libs/detail/meta/libraries.json does not exist libs/disjoint_sets/meta/libraries.json does not exist libs/function_types/meta/libraries.json does not exist libs/graph_parallel/meta/libraries.json does not exist libs/icl/meta/libraries.json does not exist libs/iostreams/meta/libraries.json does not exist libs/locale/meta/libraries.json does not exist libs/local_function/meta/libraries.json does not exist libs/numeric/meta/libraries.json does not exist libs/parameter/meta/libraries.json does not exist libs/ptr_container/meta/libraries.json does not exist libs/python/meta/libraries.json does not exist libs/random/meta/libraries.json does not exist libs/range/meta/libraries.json does not exist libs/rational/meta/libraries.json does not exist libs/scope_exit/meta/libraries.json does not exist libs/serialization/meta/libraries.json does not exist libs/statechart/meta/libraries.json does not exist libs/sync/meta/libraries.json does not exist libs/typeof/meta/libraries.json does not exist libs/type_erasure/meta/libraries.json does not exist libs/uuid/meta/libraries.json does not exist libs/winapi/meta/libraries.json does not exist Many of those libraries already have pull requests that contain the file. Please accept them and then merge them to master as well. :-) The file format is documented here: http://www.boost.org/development/library_metadata.html

2 3

Boost.Sort library hierarchy and namespacing
by Steven Ross 08 Jan '15

08 Jan '15

For the Boost.Sort library, I'm planning to add these (non-detail) files: boost/sort/sort.hpp boost/sort/spreadsort/spreadsort.hpp boost/sort/spreadsort/integer_sort.hpp boost/sort/spreadsort/float_sort.hpp boost/sort/spreadsort/string_sort.hpp Should all of these be in the boost::sort namespace? It seems silly to have a boost::sort::spreadsort namespace when there are only 5 publicly-visible functions in it. I actually can't imagine how of these names will conflict with names in other boost libraries, but using a boost::sort namespace appears conventional. Are there any objections or concerns based on this? Once this is done, I'd like to integrate this library into the boost build and testing system for the next appropriate release (I test it currently with modular boost).

2 2

Directory structure not quite right yet?
by Peter Dimov 08 Jan '15

08 Jan '15

Typically, when some library is installed in, say, $LIB, its headers reside in $LIB/include and its .a/.lib files in $LIB/lib. Our libraries, when built, go to $BOOST/stage/lib, which is close enough. But our header directory is just $BOOST, which doesn't seem right, as the whole of Boost is accessible through it. It makes sense, at least to me, to have the headers in $BOOST/include/boost, instead of just $BOOST/boost. The transition to Git would have been a good time to switch to that - there were enough other changes to the structure. I'm not saying that we should switch right away or something like that, but am I the only one to whom such a switch (at some unspecified time in the future) seems a good idea?

12 41

Is TypeOf library maintained?
by Adam Wulkiewicz 08 Jan '15

08 Jan '15

Hi, I'm asking because the most recent change in develop was done in 2013 and the last merge to master (or rather SVN release) was done in 2011. Would it be possible to along with the metadata PR have this trivial fix merged: https://github.com/boostorg/typeof/pull/1 ? It hangs there more than a half year. Thanks, Adam

2 1

New dependency report
by Peter Dimov 08 Jan '15

08 Jan '15

Here: http://www.pdimov.com/tmp/report-develop-3b5a9f4/module-overview.html http://www.pdimov.com/tmp/report-develop-3b5a9f4/module-levels.html and (new) here: http://www.pdimov.com/tmp/report-develop-3b5a9f4/module-weights.html "Weight" is on how many other modules a module depends, both directly and indirectly.

1 0

[Tick] Universal quantified concepts/traits
by Vicente J. Botet Escriba 06 Jan '15

06 Jan '15

Hi, I'm trying to represent the concept of a mathematical Functor (as in Haskell) with Concept Lite. Here is what I want to express: A Functor W is a type constructor for wrappers of another type T providing a function map taking a function (T) -> U and a W<T> and returning a W<U>. Here is how I think that could be done with Concept Lite. If I understand the proposal correctly we need to add the type T and the function parameter to the concept. concept Functor<typename W, typename T, typename F > = requires { using WT = ApplyType<W, T>; // type constructor using U = ResultType<F, T>; using WU = ApplyType<W, U>; Function<F, U, T> && requires (F f, WT wt) { WU { map(f, wt) }; } }; But this is not exactly what I want to conceptualize. The wrapped type T and the function F should be universally quantified, that is, the concept concerns only the type constructor W: Functor<W>. I have a problem introducing the universal quantification of T and F. I don't know how to do it without using again a template. concept Functor<typename W> = template <typename T, typename F> // universal quantification on T and F requires { using WT = ApplyType<W, T>; using U = ResultType<F, T>; using WU = ApplyType<W, U>; Function<F, U, T> && requires (F f, WT wt) { WU { map(f, wt) }; } } }; But this is not valid code, isn't it. Is there something wrong with this kind of concepts? What would be the best way to conceptualize this kind of concepts with the Tick library ? Best, Vicente

3 5

bpm, a tool to install a modular Boost distribution
by Peter Dimov 06 Jan '15

06 Jan '15

One month ago, Stephen Kelly wrote: > git affects the developer workflow, but that thread was about creating > modular releases and downloads, which is a different goal and has a > different set of problems to solve. That's what that thread was about. I > didn't see any desire to have that as a goal in the thread. > > Git doesn't affect users. > > Before and after transition to git, they download all-of-boost.zip from > the boost website. To address this point of his, I've been working at a tool, bpm, that can install a modular Boost distribution. As I've already mentioned in other threads, it works like this: D:\boost-1.60.0>bpm install system bpm: installing module 'system' bpm: installing module 'assert' bpm: installing module 'config' bpm: installing module 'core' bpm: installing module 'predef' bpm: installing module 'build' bpm: the following libraries need to be built: system bpm: (use ./b2 to build) bpm: recreating header links bpm: recreating index That is, when told to install Boost.System, it downloads and installs the 'system' package into ./libs/system, along with all its dependencies, then creates links to the headers (like 'b2 headers') in ./include and an ./index.html file listing the installed libraries. The full syntax is: D:\boost-1.60.0>bpm Usage: bpm [-v] [-q] command [options] [modules] -v: Be verbose -vv: Be more verbose -q: Be quiet bpm install [-n] [+d] [-k] [-a] [-i] [-p] <module> <module>... Installs the specified modules and their dependencies into the current directory. -n: Only output what would be installed +d: Do not install dependencies -k: Do not remove partial installations on error -a: All modules (use instead of a module list) -i: Installed modules -p: Partially installed modules bpm remove [-n] [-f] [-d] [-a] [-p] <package> <package>... Removes the specified packages. (A package, like 'numeric', can contain more than one module.) -n: Only output what would be removed -f: Force removal even when dependents exist -d: Remove dependents as well. Requires -f -a: Remove all packages. Requires -f -p: Remove partially installed packages bpm list [-a] [-i] [-p] [-b] [prefix] Lists modules matching [prefix]. -a: All modules (default when no -b) -i: Installed modules (default when -b) -p: Partially installed modules -b: Modules that require building bpm headers Recreates the header links in the include/ subdirectory of the current directory. bpm index Recreates the file index.html, which lists the installed modules, in the current directory. -- This all works already under Windows. (I haven't finished the POSIX part yet but it should be close.) I could have made a Windows binary available for people to play with, but I'd rather give sources (at first). bpm contains code to do rm -rf <directory>, and if I've made a mistake somewhere, it could cause damage. So, if there is interest and there are no objections, I'd like to put this tool into the Boost repository, in tools/bpm.

5 10

[GIL] runtime assertion error
by Stephan Menzel 06 Jan '15

06 Jan '15

Hello, I was playing with GIL a little and started out with the tutorial. After adapting it a bit I noticed a runtime assertion error here in color_base.hpp +343: template <typename Element, typename Layout, int K> typename element_reference_type<homogeneous_color_base<Element,Layout,K> >::type dynamic_at_c(homogeneous_color_base<Element,Layout,K>& cb, std::size_t i) { assert(i<K); return (gil_reinterpret_cast<Element*>(&cb))[i]; } The example works if I compile in release but I still wanted to bring it up because of an extensive comment above this template that states that this assertion checks for compiler specific behavior and mentions flags that need to be set but not which flags. I believe there might be a bug there. Also, since it's the tutorial, I suppose it should work under most circumstances. I have a sample of the code attached. It's gcc 4.8 here in Linux 64. Nothing fancy. Boost 1.56. Cheers, Stephan

2 4

Library list generated from meta/libraries.json files
by Peter Dimov 06 Jan '15

06 Jan '15

I've put a library list generated from the meta/libraries.json files, at: http://www.pdimov.com/tmp/boost/index.html Library authors may wish to take a look at their library entry and see if they're happy with it. What I've noticed so far is that many libraries are missing the boost-version (First Release) entry, and that Config is missing authors for some reason. The other thing is that the category names in the json files are the internal identifiers, which I've left as-is, as I didn't want to hardcode a mapping. We'll have to decide whether to use the proper names in the json files, or whether to have a separate categories.json with the mapping somewhere. I tend towards the first option.

4 13

[status] explicit-failures-markup.xml edit permissions
by Vladimir Batov 05 Jan '15

05 Jan '15

On some compilers some of my SFINAE-related "convert" regression tests fail. So, I tried to update status/explicit-failures-markup.xml to explicitly mark those test failures rather than masking/disabling them. For understandable reasons I have no permissions to modify the file, so that update of mine was denied. I tried contacting Daniel James as he often helps me with build matters but he is seemingly unavailable. I am hoping someone else might have edit-permissions to the file and be kind enough to add the following code (below) to the file for me? My apologies for such a wide post or if my request is misdirected. Your help in the matter is much appreciated. Thanks, Vladimir.  <library name="convert"> <test name="convert_test_has_begin"> <mark-failure> <toolset name="msvc-8.0*"/> <toolset name="msvc-9.0*"/> <toolset name="msvc-10.0*"/> <toolset name="msvc-11.0*"/> <note author="Vladimir Batov"> The relevant SFINAE support is broken in MSVC up to version 11. </note> </mark-failure> </test> </library>

3 2

[functional] Is anyone maintaining it?
by Andrzej Krzemienski 05 Jan '15

05 Jan '15

Hi Everyone, I can see that the pull request I submitted at https://github.com/boostorg/functional almost three months ago has not been acted upon. Is the library still maintained? Regards, &rzej

2 1

[test] Problems with UTF-8 paths in GIT.
by Rene Rivera 05 Jan '15

05 Jan '15

This commit < https://github.com/boostorg/filesystem/commit/785d521b54140763dd23ef091a18d…> is causing me some problems with some git clients. In particular the git client in Eclipse errors out with some unsupported / invalid messages. I know why those dir names are the way they are.. But we still are supposed to follow the naming rules we agreed to < http://www.boost.org/development/requirements.html#Directory_structure>. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

3 3

[filesystem] Problems with UTF-8 paths in GIT.
by Rene Rivera 05 Jan '15

05 Jan '15

Sorry.. I used the wrong tag :-( Now using the correct tag. On Mon, Jan 5, 2015 at 11:27 AM, Gennadiy Rozental <rogeeff(a)gmail.com> wrote: > Rene Rivera <grafikrobot <at> gmail.com> writes: > > Sorry, I might be missing something: what does this have to do with [test]? > > Gennadiy > > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost > -- -- 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

[githelp] Delete/hide branch..
by Rene Rivera 05 Jan '15

05 Jan '15

In cleaning up the "regression" subrepo.. I'm wanting to delete or hide the master branch as it: has horribly outdated code, and I'm only going to ever edit the develop branch. How do I delete or hide a branch? -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

3 2

[build,quickbook] complete doxygen output
by Gennadiy Rozental 05 Jan '15

05 Jan '15

> Maybe you can ask a separate thread, describing > what you want, so that Boost.Book experts notice it more easily? Hi, Per Vlad suggestion I am creating a separate thread about this. It should probably go into documentation list as well, but I am not sure how to do this in gmane interface > I would like to help, but Boost.Build only runs doxygen and then invokes > various XSLT tarnsforms. Everything else is either doxygen itself, or > Boost.Book, where I can only make trivial tweaks. What I am after is alternative rule, which will not try to make quickbook like output out of doxygen, but instead just leave it alone. So I need to run doxygen place the output somewhere and somehow point my quickbook based docs to that output. How would the Boost.Build rule look like? > What do you mean by 'bind' here? I want to bind references to class/function/module names to entries in generated doxygen docs. I am fine with some quickbook template I can apply, but automation would be even better. Gennadiy

2 1

libraries.json missing boost-version, update-version
by Peter Dimov 05 Jan '15

05 Jan '15

I notice that the library list at the website has a "First Release"entry for each library; these apparently come from the tag <boost-version> in libraries.xml, which also has an <update-version>. The meta/libraries.json files, however, appear to have no such data. Is this intentional?

2 1

[build] Tests automatically create header links, but library builds do not
by Peter Dimov 05 Jan '15

05 Jan '15

If I remove my boost/ directory, and attempt to build, for example, atomic, by going into libs/atomic/build and invoking b2, it fails due to a missing header: D:\tmp2\libs\atomic\build>b2 toolset=msvc-8.0 ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_8.0_vcvarsall_x86.cmd ...updated 1 target... ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_8.0_vcvarsall_x86_amd64.cmd ...updated 1 target... Performing configuration checks - symlinks supported : no - junctions supported : yes - hardlinks supported : yes ...found 208 targets... ...updating 5 targets... common.mkdir ..\..\..\bin.v2\libs\atomic\build\msvc-8.0\debug\threading-multi compile-c-c++ ..\..\..\bin.v2\libs\atomic\build\msvc-8.0\debug\threading-multi\lockpool.obj lockpool.cpp ..\..\..\boost/atomic/detail/ops_msvc_x86.hpp(20) : fatal error C1083: Cannot open include file: 'boost/type_traits/make_signed.hpp': No such file or directory [...] Same if I do b2 --with-atomic from root. However, if I go into, say, libs/smart_ptr/test and invoke b2 there, it works: D:\tmp2\libs\smart_ptr\test>b2 toolset=msvc-8.0 ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_8.0_vcvarsa ll_x86.cmd ...updated 1 target... ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_8.0_vcvarsa ll_x86_amd64.cmd ...updated 1 target... Performing configuration checks - symlinks supported : no - junctions supported : yes - hardlinks supported : yes ...patience... ...found 1722 targets... ...updating 1253 targets... common.mkdir ..\..\..\bin.v2\libs\smart_ptr common.mkdir ..\..\..\bin.v2\libs\smart_ptr\test common.mkdir ..\..\..\bin.v2\libs\smart_ptr\test\yield_k_test~mt.test common.mkdir ..\..\..\bin.v2\libs\smart_ptr\test\yield_k_test~mt.test\msvc-8.0 common.mkdir ..\..\..\bin.v2\libs\smart_ptr\test\yield_k_test~mt.test\msvc-8.0\debug common.mkdir ..\..\..\bin.v2\libs\smart_ptr\test\yield_k_test~mt.test\msvc-8.0\debug\threading-multi mklink-or-dir ..\..\..\boost\smart_ptr Junction created for ..\..\..\boost\smart_ptr <<===>> ..\include\boost\smart_ptr link.hardlink ..\..\..\boost\predef.h Hardlink created for ..\..\..\boost\predef.h <<===>> ..\..\predef\include\boost\predef.h [...] Why is that? My first thought was that this was due to the fact that I was missing libs/Jamfile.v2 (I do various "clean" installations as an experiment to see what's needed and what isn't), but I put it back there and it doesn't help.

4 15

Linux regression test runners - What do devs want?
by Tom Kent 05 Jan '15

05 Jan '15

I've been pondering this recently, but a forced upgrade of my azure VMs last night is pressing the issue...and I wanted to solicit feedback before I go and set things back up... I've currently been running three testing machines for linux, with several testers on each, (windows is completely separate, and I'm happy with how that is running)...here was my past strategy: teeks99-03 - develop - lots of compiler versions (all I could get to run on ubuntu 12.04: gcc-4.4-4.8, clang-3.0-3.4) teeks99-04 - develop - only two compilers, with fast turnaround times (gcc-4.8, clang-3.4) teeks99-05 - master - lots of compiler versions (all I could get to run on ubuntu 12.04: gcc-4.4-4.8, clang-3.0-3.4) I can try to set things up like this again, but there are two reasons I was thinking about changing: 1) It seems that a lot of the gcc/clang versions have the same pass/fail results as the other versions of that compiler, so we're not adding a ton (though we may be adding the crucial points where a compiler change breaks something...is this something that devs have seen in practice?) 2) The new version of my runners (Ubuntu 14.04) doesn't easily support the old gcc versions, it would take a lot of effort to get some of the old ones running. Clang is even worse...it is much more difficult to get even two versions running side by side now. Instead of running lots of different versions, I was thinking about running various compatibility options of the two main compilers...I've seen some other test runners with things like libc++, c++11, c++14, etc. My real question, would developers be better served by these options than different versions? Would they prefer both with longer revisit times between each test type? Other thoughts? Tom

6 5

gcc.archive fails under Windows/Cygwin
by Peter Dimov 05 Jan '15

05 Jan '15

Fails like this: gcc.archive ..\..\..\bin.v2\libs\system\build\gcc-4.8.3\release\link-static\libboost_system-gcc48-1_58.a The system cannot find the path specified. The system cannot find the path specified. "/usr/i686-pc-cygwin/bin/ar.exe" rc "..\..\..\bin.v2\libs\system\build\gcc-4.8.3\release\link-static\libboost_system-gcc48-1_58.a" "..\..\..\bin.v2\libs\system\build\gcc-4.8.3\release\link-static\error_code.o" "/usr/i686-pc-cygwin/bin/ranlib.exe" "..\..\..\bin.v2\libs\system\build\gcc-4.8.3\release\link-static\libboost_system-gcc48-1_58.a" ...failed gcc.archive ..\..\..\bin.v2\libs\system\build\gcc-4.8.3\release\link-static\libboost_system-gcc48-1_58.a...

1 0

Help required to start contributing to Boost.
by Ameya Prabhu 03 Jan '15

03 Jan '15

Hello, I am new to Boost. I'm fairly well at C++ and am programming since the last 6 months. I would like to contribute to its development. Can someone please help me out? I had a look at the website but I am unable to find bugs that are suitable for beginners. Thanks!

5 4

[move] traits file problem causing many test failures.
by Fletcher, John P 03 Jan '15

03 Jan '15

There is a problem on the develop tests which was not there yesterday. In file included from ../libs/phoenix/test/regression/bug4853.cpp:16: In file included from ../boost/range/adaptor/transformed.hpp:15: In file included from ../boost/range/detail/default_constructible_unary_fn.hpp:13: In file included from ../boost/optional/optional.hpp:48: In file included from ../boost/move/utility.hpp:25: ../boost/move/traits.hpp:27:10: fatal error: 'boost/move/detail/type_traits.hpp' file not found #include <boost/move/detail/type_traits.hpp> ^ 1 error generated. I hope this can be sorted out soon. Happy New Year John

2 2

[build] msvc.write_setup-script always called for msvc-12.0
by Peter Dimov 02 Jan '15

02 Jan '15

When I do (for example) C:\Projects\boost-git\boost\tools\boostdep\build>b2 toolset=msvc-8.0 I get ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_12.0_vcvarsall_x86.cmd ...updated 1 target... ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_12.0_vcvarsall_x86_amd64.cmd ...updated 1 target... ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_8.0_vcvarsall_x86.cmd ...updated 1 target... ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_8.0_vcvarsall_x86_amd64.cmd ...updated 1 target... which correctly generates the setup scripts for the specified msvc-8.0, but also unconditionally generates the setup scripts for msvc-12.0, which are not needed at this time. This msvc-12.0 generation occurs even if I use a non-msvc toolset, or even just do b2 --show-libraries. C:\Projects\boost-git\boost>b2 --show-libraries ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_12.0_vcvarsall_x86.cmd ...updated 1 target... ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_12.0_vcvarsall_x86_amd64.cmd ...updated 1 target... The following libraries require building: - atomic - chrono [...]

1 0

[filesystem] Junction support on Windows?
by Peter Dimov 02 Jan '15

02 Jan '15

Filesystem provides support for hard and symbolic links, but on Windows, hard links do not work on directories and symbolic links do not work for the majority of users because they require elevation by default. That is why, for example, "b2 headers" was changed to also use junctions, if possible. But if I, for another example, want to replicate "b2 headers" from a C++ program using Filesystem, I can't, because it offers no junction support. Should create_directory_symlink be enhanced to create a junction, if CreateSymbolicLink is not available or fails with ERROR_ACCESS_DENIED?

2 2

[filesystem] resize_file_api leaks a HANDLE
by Peter Dimov 02 Jan '15

02 Jan '15

... when SetFilePointerEx or SetEndOfFile fails. BOOL resize_file_api(const wchar_t* p, boost::uintmax_t size) { HANDLE handle = CreateFileW(p, GENERIC_WRITE, 0, 0, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, 0); LARGE_INTEGER sz; sz.QuadPart = size; return handle != INVALID_HANDLE_VALUE && ::SetFilePointerEx(handle, sz, 0, FILE_BEGIN) && ::SetEndOfFile(handle) && ::CloseHandle(handle); }

3 2

updated Boost.Test devel->master: documentation needs
by Dave Gomboc 02 Jan '15

02 Jan '15

> What left in docs: > > * general reformating of existing pages and separation to "user's guide" and "advanced usage scenarios" (I am working on this) > * BOOST_TEST tool, including figuring out what to do with old testing tools description and reference > * data driven test cases (Raffi works on this) > * decorators support (Andrzej volunteered to help with this) > * run by name/label description. Including multitude of new syntax options > * figure out doxigen issues > * figure out new format for examples > * few minor issues with Boost.Logos > * investigate Boost.pp style left side menu (optional) > * interaction testing (optional) > * production use of Boost.Test (optional) > * anything else missing from above (hopefully nothing big) > > Any takers? > Gennadiy Thanks for posting this list, Gennadiy. I'll volunteer to write up a section on the production use of Boost.Test. I will, however, need source material in order to do so. Boosters, have you ever or do you now use either Boost.Test or an alternative testing framework in a production-like manner? - with more complicated or less common build systems - when regression testing across multiple versions of dependent libraries - when regression testing across multiple toolchains and/or platforms - as part of deployments within virtualized containers - et cetera If so, could you please describe your setup, either here on-list or privately to myself? I will collect the responses received, and from them, prepare documentation so that people new to Boost.Test can get started with setting up production-quality regression testing environments. Dave

2 1

[compute] Review
by Yiannis Papadopoulos 01 Jan '15

01 Jan '15

Hi, This is my review of Boost.Compute: 1. What is your evaluation of the design? It seems logical to me. It is effectively a wrapper around OpenCL that provides implementations of higher-level algorithms, and allows interoperability with OpenCL and OpenGL. The Boost.Compute name is a bit misleading, as Boost.Compute supports only OpenCL-enabled devices. 2. What is your evaluation of the implementation? There is some code duplication (e.g. type traits) and various other bits and pieces that can be moved to existing Boost components. I think there should be some effort spent towards that. It seems that performance is on par with Thrust. However, there are other libraries out there (e.g Bolt) and multiple devices, so there has to be a more extensive experimental evaluation to say decidedly that it is a good implementation. 3. What is your evaluation of the documentation? Overall, it is pretty good. Given the complexity of the accelerator programming model, a few more elaborate examples in the tutorial would be welcome. 4. What is your evaluation of the potential usefulness of the library? This is difficult to answer. A lot of work has been put in this library and it seems the way to go. The interfaces are clean, the code looks solid and the developer willing. However, there is limited vendor support, there are not enough benchmarks and there are other alternatives that they have both. Given that Boost.Compute is targeted to users that know a thing or two about performance, I don't know how they can be convinced to consider using Boost.Compute against Bolt or Thrust. 5. Did you try to use the library? With what compiler? Did you have any problems? I did using an AMD 7850 on Linux with gcc 4.8. The few examples I tried, compiled and ran fine. 6. How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? I went over the documentation, I glanced over the code and ran a few examples. 7. Are you knowledgeable about the problem domain? I'm in the HPC field. I have extensive experience with MPI, OpenMP, pthreads, and less with TBB, CUDA and OpenCL. 8. Do you think the library should be accepted as a Boost library? This will be a maybe. It is a well-written library with a few minor issues that can be resolved. However, why would someone use Boost.Compute against what is out there? Average users can resort to Bolt or Thrust. Power users will probably always try to hand-tune their OpenCL or CUDA algorithm. How can we test it and prove its performance? Regards, Yiannis

5 7

[compute] Review results
by Antony Polukhin 01 Jan '15

01 Jan '15

Hi all, Extended review period for Boost.Compute library has ended. Here are the review votes for inclusion (+ means include, - means do not include, +/- means conditional include or "probably include, not quite sure"): + Denis Demidov + Sebastian Schaetz + Pavan Yalamanchili - Gruenke,Matt (+ if more backends will be supported) + Asbjørn (mini-review/comments from a library user) + Thomas M (a lot of suggestions) + Paul A. Bristow + Belcourt, Kenneth + John Bytheway +/- Yiannis Papadopoulos (there's already Bolt/Thrust for beginner and pure OpenCL for pros) +/- Vicente J. Botet Escriba (better docs and more performance tests) +/- Jason Newton (there was no explicit answer to the question "shuld be this library accepted into Boost?" but the review was positive in general) To sum up: Compute library becomes part of the Boost. Great thanks to all for the reviews and comments! Huge work was done and the issues raised are essential for library success. P.S.: Happy new year everyone! P.P.S.: Hope I did not miss some review! In case of any error, please let me know! -- Best regards, Antony Polukhin

1 0

[compute] review
by Vicente J. Botet Escriba 01 Jan '15

01 Jan '15

Hi, I have no time to do a complete review. Anyway here it is my minimal review *1. What is your evaluation of the design?** *** I would prefer that the algorithms take as first parameter the queue (which could be abstracted to an asynchronous executor). The performances let think that there is no interest in using the library for containers having less than 10^4/10^5 elements. Even if this is considered a low level library, the documentation should show how a library writer could make use of the provided interface to provide a higher one. I would prefer that the library make use of std::future or boost::future class instead of adding an additional one. Do the author tried to make use of the existing futures? if yes, which problems were found? I'm missing a range interface to most of the algorithms. I suspect that as this is a C++03 library it doesn't take advantages of some interesting C++11+/C++14 features. It is not clear which operations are synchronous, which ones could block, ... In order to get the native OpenCl handle I suggest to name the function get_native_handle instead of get. *2. What is your evaluation of the implementation?* I've not see at the implementation. *3. What is your evaluation of the documentation?* The documentation lacks of some core tutorials. I was unable to have an idea of what a context is, what can be done with a command_queue, what is a Kernel, a pipe, ...? Does it mean that the user must know OpenCL? The reference documentation should follow he C++ standard way, including pre-conditions, effects, synchronization, throws clauses. I would appreciate a description of the algorithms used, how the parallelism is used? is this completely managed by OpenCL or do the library something else? *4. What is your evaluation of the potential usefulness of the library?** *** This is essentially an optimization library. It should be quite useful, but the performances results don't probe it. *5. Did you try to use the library? With what compiler? Did you have any problems?** * No.* *** *6. How much effort did you put into your evaluation? A glance? A quick reading? In-depth study?** *** A glance. *7. Are you knowledgeable about the problem domain?* Yes and not. I don't know about OpenCL, but I'm aware of the current parallel proposals. *8. Do you think the library should be accepted as a Boost library? ** * As I have not taken too much time I'm unable to say that this library should not be included in Boost. So I vote to include it conditionally, subject to: * I would need some performances that probe the library is better than using standard STL containers in most of the cases. * The documentation should be completed with more tutorials and a better reference documentation. Best, Vicente

4 4

[compute] review
by Gruenke,Matt 31 Dec '14

31 Dec '14

> 1. What is your evaluation of the design? I agree with other comments made about synchronization. The design should be more explicit about what's asynchronous, and ideally utilize only one mechanism for synchronization. One approach that would have made this clearer is if high-level operations were actually objects that got posted to the command_queue. Regarding synchronization, I'm a also bit concerned about the performance impact of synchronizing on all copies to host memory. Overuse of synchronization can easily result in performance deterioration. On this point, I think it might be worth limiting host memory usable with algorithms, to containers that perform implicit synchronization to actual use (or destruction) of results. Give users the choice between that or performing explicit copies to raw types. Also, I agree with Thomas M that it'd be useful for operations to return events. That said, if you told me it doubled the overhead involved in dispatching operations, I'd suggest to make it optional through overloads or via a mechanism in the command_queue itself. > 2. What is your evaluation of the implementation? It seems a bit heavy to be header-only. I'd agree with Andrey Semashev, regarding thread safety, except I think it shouldn't be an option at all. That said, not all operations on all objects need be thread safe. I think the Boost.ASIO documentation provides a good example of how to express different thread safety limitations. Now, I haven't examined the use of thread-local storage, but do you feel there's a strong case to be made for the thread safety it's providing (especially, given that you seem to feel it's non-essential)? I'm a bit concerned about the use of type names ending in '_', such as float4_. Is this consistent with Boost conventions? I've only seen that used in other Boost libraries to denote class member variables. I didn't notice any unit tests specifically intended to verify exception-safety. I'd want to know that had been thoroughly vetted, before I'd consider using Boost.Compute in production code. Finally, based on the docs, it seems there's a bug in boost::compute::command_queue::enqueue_copy_image_to_buffer() and boost::compute::command_queue::enqueue_copy_buffer_to_image(). The region and origin parameters should be arrays, in the 2D and 3D cases. If this discrepancy is intentional, it should be noted. I haven't exhaustively reviewed the reference docs, so there might be other issues of this sort. > 3. What is your evaluation of the documentation? It needs more and better-documented tutorials (and I'm including the "Advanced Topics", here). Some of the reference pages could use more details, as well, especially concerning synchronization and exception usage. Regarding exceptions, there should be discussion of specifically what is invalidated by which kinds of errors. If any errors are non-recoverable, this should also be called out and perhaps derived from a different or additional baseclass (not a bad use case for multiple inheritance, actually). I agree with Mathias Gaunard that it would be helpful to discuss computational complexity, device memory requirements, and the various methods used to implement some of the algorithms. You could continue to omit these details on the simple algorithms, though. > 4. What is your evaluation of the potential usefulness of the library? This is my biggest misgiving, by far. In the very near future, I expect developers will opt for either SYCL (https://www.khronos.org/opencl/sycl) or Bolt (https://github.com/HSA-Libraries/Bolt) SYCL provides a modern, standard C++11 wrapper around OpenCL, with better concurrency control and support for integrating kernels inline. Bolt provides many of the same higher-level abstractions found in Boost.Compute, but with forthcoming support for HSA. To have the kind of lasting relevance and broad applicability to which all Boost libraries should aspire, I think Boost.Compute should be architected to support multiple backends. Though OpenCL support is currently ascendant, it's far from universal and is already flagging on some platforms (Nvidia, not the least). And HSA provides a foundation on which alternatives are actively being built. Most importantly, there exist multitudes of multi-core and multiprocessor systems which lack OpenCL support. It would be eminently useful to support these with such backends as thread pool, OpenMP, etc. And backends could be added to support new technologies, as they mature. > 5. Did you try to use the library? With what compiler? Did you have any problems? I downloaded and inspected the sources and some examples. I didn't have any questions or concerns that would be addressed by experimentation. > 6. How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? Review of the documentation, some sources, some examples, and a refresher on SYCL & Bolt. I also read all of the reviews and replies sent thus far. > 7. Are you knowledgeable about the problem domain? I've been developing production code for parallel and heterogeneous computing platforms for the majority of the last 16 years. I've followed OpenCL since version 1.0 was finalized. I've also submitted bug reports and minor patches for Khronos' official C++ OpenCL interface. > 8. Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Not in its current state. The primary issue is that it's too OpenCL-centric. It should support more backends, even if these are just compile-time options. This is crucial for both current and lasting relevance. Beyond that, better concurrency control is crucial for optimum performance. If done well, it could even help further reduce usage errors. Matt ________________________________ This e-mail contains privileged and confidential information intended for the use of the addressees named above. If you are not the intended recipient of this e-mail, you are hereby notified that you must not disseminate, copy or take any action in respect of any information contained in it. If you have received this e-mail in error, please notify the sender immediately by e-mail and immediately destroy this e-mail and its attachments.

13 63

Boost.Build files at superproject root
by Peter Dimov 31 Dec '14

31 Dec '14

Currently, the Boost root contains the following files: boost-build.jam boostcpp.jam boostcpp.py bootstrap.bat bootstrap.sh Jamroot which are part of Boost.Build and so their rightful place is in the submodule. Would it be possible to move them there, and leave only minimal forwarding shims (that would never need to change) in the superproject?

3 5

[compute] Review
by John Bytheway 31 Dec '14

31 Dec '14

Here's my review. 1. What is your evaluation of the design? The design of building on OpenCL seems sound, for the reasons Kyle has explained. The fact that it has real users is very encouraging. I don't really like the name (I was unable to guess what the library was about from the name), but it's not worth changing at this point. I am worried about the compile-time configuration with macros. I would hope that BOOST_COMPUTE_HAVE_THREAD_LOCAL could be read from Boost.Config. For the two features which require linking against other Boost libraries, my instinct would be to have them on by default, rather than off by default (that should be easier if and when Boost.Compute is part of the Boost distribution). It would be very nice to have range versions of all the algorithms. I find myself using the boost::range algorithms much more than the std:: ones these days. Similarly, it would be good to provide the safer 4-iterator versions of equal, is_permutation, mismatch (and any I've forgotten) as were added to C++14. Some minor things: - Consider renaming boost::compute::lambda to be consistent with one of the other placeholder-containing namespaces from std or Boost. (You can keep the old name as an alias for backwards-compatibility). - Why the default of .25 as the bernoulli_distribution parameter? - Did you consider using Boost.Predef for your version macro? 2. What is your evaluation of the implementation? Only looked at a couple of things while trying to understand the docs. 3. What is your evaluation of the documentation? Overall, not too bad. More tutorial would be good. In particular, something using some of the standard algorithms. Some concerns: - All the header links off <http://kylelutz.github.io/compute/boost_compute/reference.html> are broken. - All or most of the things in "See also" sections look like they ought to be links but aren't. - For all your function parameter documentation, the list of parameters seems to be sorted alphabetically by parameter name rather than in the order they are passed to the function. This is really weird... - As others have mentioned, some kind of complexity estimate or promise for the algorithms is very important. In particular it would be good to understand how much parallelism they take advantage of and how they ought to scale with device compute capability. - The warning about accumulate being slow for floats should be much more prominent. - <http://kylelutz.github.io/compute/boost/compute/copy.html> mentions copying from e.g. a std::list to a compute::vector. It would be nice if it gave some kind of indication as to how efficient we can expect such an operation to be. In particular, I guess it ought to do some kind of buffering on the host? - The way I normally copy into vectors is call v.reserve(...) and then copy to std::back_inserter(v). I tried that with a compute::vector and unsurprisingly it was very inefficient. I see you already warned about this in the push_back docs, but perhaps it should also be highlighted in the documentation of compute::copy. - Is there no version of inclusive/exclusive_scan or iota using an arbitrary associative operator? - <http://kylelutz.github.io/compute/boost/compute/includes.html> it's unclear whether the subrange has to be contiguous. - min_element and max_element should cross-reference minmax_element. - What source of randomness does random_shuffle use? - Why does reduce return its result through an OutputIterator? - <http://kylelutz.github.io/compute/boost/compute/remove.html> Does this really remove things or use std::remove semantics? You should clarify and document the return value. (Same with remove_if, unique) - I can see how sort_by_key might be useful, and I'm slightly surprised that there's no stable_sort_by_key (which seems like it would be more useful than stable_sort). Any particular reason? - The boost/compute/types headers docs seem to be broken or missing. In particular I couldn't find reference documentation for float4_ et al. - I was interested to see allocators, but the docs seem uninformative: <http://kylelutz.github.io/compute/boost/compute/pinned_allocator.html> - Given the confusion with std::future, you might want to clarify whether compute::future's destructor blocks. - Also, <http://kylelutz.github.io/compute/BOOST_COMPUTE_CLOSURE.html> doesn't explain what format the lists (arguments and capture) should be in. Preprocessor functions often take lists in other formats, such as a Boost.PP Sequence <http://www.boost.org/doc/libs/1_57_0/libs/preprocessor/doc/data/sequences.h…>, and your example only has one-element lists, so it's not enough to clarify this point. (To be clear: I'm not suggesting you should use Boost.PP sequences, merely that you should make it clear in the docs whether you are). - <http://kylelutz.github.io/compute/BOOST_COMPUTE_CL_CALLBACK.html> is empty, as is <http://kylelutz.github.io/compute/BOOST_COMPUTE_MAX_ARITY.html> - <http://kylelutz.github.io/compute/boost/compute/valarray.html> - presumably compute::valarray has overloaded arithmetic operators? Are they mentioned anywhere? - <http://kylelutz.github.io/compute/boost/compute/vector.html> the unusual behaviour of vector's size_t constructor (not initializing the elements) should be warned more prominently. - <http://kylelutz.github.io/compute/boost/compute/device.html> the documentation of the enum type in the synopsis seems to be messed up. Similarly memory_object. - <http://kylelutz.github.io/compute/boost/compute/function.html> I'm puzzled by this interface. What's the name for? Would one ever use this constructor rather than e.g. make_function_from_source? - <http://kylelutz.github.io/compute/boost/compute/field.html> My reading of this is that when you get the type wrong you are guaranteed some kind of meaningful error report, and not just undefined behaviour; is that right? Perhaps you should clarify. - I can't guess what atomic_min and atomic_max do. - The right arrow ('next') link from <http://kylelutz.github.io/compute/boost/compute/atomic_xor.html> is broken (looks like the docs for the placeholders don't work). - The iterators should state what iterator category they have. - I can't guess what svm_ptr is for. Later I discovered svm_alloc and svm_free. Is there an RAII way to manage these things? - What does default_device do if there are no devices? Do the various environment variables mentioned have any kind of precedence? (Probably linking to the corresponding OpenCL docs is sufficient for such questions). Do they have to be exact matches? Are they case-sensitive? - What does find_device do if the requested device does not exist? - Can you give examples for type_definition? My guess was that it did the thing which type_name later turned out to do... - BOOST_COMPUTE_ADAPT_STRUCT should state that it must be used at global scope (i.e. not within a function or other namespace). - Congratulations for getting compile-time detection of internal padding into BOOST_COMPUTE_ADAPT_STRUCT :). You might want to mention in the docs that this will be detected, so people don't worry too much. - It looks like the performance tests don't include the time for copying data to (and, where applicable, from) the device. You should mention this on the Performance page. - You should probably add C++AMP to your things compared with in the FAQ. 4. What is your evaluation of the potential usefulness of the library? High. I've wanted something like this in the past and not found this. 5. Did you try to use the library? With what compiler? Did you have any problems? I used it with g++ 4.8.2 in C++1y mode. Some quick tests seemed to work OK, and indeed I was able to sort some large vectors of scalars faster using boost::compute::sort than std::sort, which is nice. I was pleased to see that 64-bit integers were handled fine. 6. How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? Couple of hours reading and trying simple examples. 7. Are you knowledgeable about the problem domain? I have done a couple of small projects with CUDA, and am generally knowledgeable, but with no previous OpenCL experience. 8. Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Yes. OpenCL seems to have fairly broad acceptance, but is rather difficult to use safely and with C++-isms. This library fills a useful niche. In an ideal world it will eventually be rendered obsolete by things like parallelism entering the standard library, but I doubt that will happen soon if at all. This provides a good solution now, and we shouldn't dismiss it simply because something sparkly is approaching, which may or may not turn out to be awesome and widely adopted. This library has clearly been a lot of work. Congratulations on making it this far, I hope the review is not too stressful :). John Bytheway

3 12

[system] Problem with boost::system::system_category() under QNX Momentics
by Piotr Orzechowski 31 Dec '14

31 Dec '14

At the beginning I must assure You that I've tried almost every solution from similar topics , still they didn't solve my issue. I'm building binaries from Boost 1.57 using **MinGW**. Boost libraries I'm using: *thread* and *system* build without any errors. I was trying: > toolset=gcc --target-os=qnxnto and toolset=gcc --target-os=qnx, both didn't work. I'm including correctly both libraries: > -lboost_system-mgw48-mt-d-1_57 -lboost_thread-mgw48-mt-d-1_57 after using: > `#define BOOST_SYSTEM_NO_DEPRECATED` I got rid of `boost::system::generic_category()` error, still I can't get rid of: > boost::system::system_category() I'm working in **QNX Momentics**. I'm totally out of ideas, I'm really looking forward for any help I can get.

2 2

Define to test for deprecated std::auto_ptr
by Fletcher, John P 31 Dec '14

31 Dec '14

I have some tests which are throwing up std::auto_ptr as deprecated with C++11. Is there a define that can be tested for in user code so that I can switch to std::unique_ptr when it is available? Something like this: #ifdef BOOST_NO_CXX11_UNIQUEPTR // use auto_ptr #else // use unique_ptr #endif Is there a general flag for C++11 or C++14 or is it all done on particular features? Thanks John

3 5

[compute] CL_QUEUE_OUT_OF_ORDER_EXEC_MODE_ENABLE
by Gruenke,Matt 31 Dec '14

31 Dec '14

I assumed there was some behind-the-scenes mechanism to maintain order of higher level operations, but I hadn't dug around to find them. I thought maybe there was an event object embedded in the device memory containers, used to track any pending writes to them, that could be added to the wait list of subsequent operations. But I don't see anything like this. So, will enabling out-of-order execution will break the higher level operations? Or am I missing something? Matt ________________________________ This e-mail contains privileged and confidential information intended for the use of the addressees named above. If you are not the intended recipient of this e-mail, you are hereby notified that you must not disseminate, copy or take any action in respect of any information contained in it. If you have received this e-mail in error, please notify the sender immediately by e-mail and immediately destroy this e-mail and its attachments.

3 6

[compute] Review period starts today December 15, 2014, ends on December 24, 2014
by Antony Polukhin 31 Dec '14

31 Dec '14

Dear All, Review of the Compute library starts today on Mon 25st of December 2014 and will last for ten days. The Compute library provides a C++ interface to multi-core GPGPU and CPU computing platforms based on OpenCL. The project is hosted on GitHub at https://github.com/kylelutz/compute. Docs are available at http://kylelutz.github.io/compute/ Sources could be downloaded as a ZIP archive via https://github.com/kylelutz/compute/archive/master.zip Some pre-official reviews could be found in Boost Library Incubator: http://rrsd.com/blincubator.com/reviews/?library_id=669 Please, answer the following questions in your review: 1. What is your evaluation of the design? 2. What is your evaluation of the implementation? 3. What is your evaluation of the documentation? 4. What is your evaluation of the potential usefulness of the library? 5. Did you try to use the library? With what compiler? Did you have any problems? 6. How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? 7. Are you knowledgeable about the problem domain? And finally, every review should answer this question: 8. Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. -- Best regards, Antony Polukhin

7 8

[compute] Review comments
by Asbjørn 30 Dec '14

30 Dec '14

Hi, not a proper review, just some comments from a library user based on studying documentation and writing a couple of simple programs using Boost.Compute on Intel's and NVIDIA's OpenCL implementations (i7 CPU and GTX970 GPU respectively). I used MSVC2013 for the tests. Some of these comments I've shared previously on this list, but I'm repeating them here for completeness. I have some background in heterogeneous development and OpenCL in particular, but I'm no expert. I found Boost.Compute easy to pick up and providing a nice C++ layer, with a nice mix of low and high level. Comments in no particular order: 1) As a library user and one who's not a C++ guru by any means, the error messages thrown up when passing incorrect parameters can be quite confusing. For example, first time I tried to use Boost.Compute I managed to not pass the ouput iterator parameter to transform(), so that the lambda expression ended up in that position instead. This resulted in several very confusing errors inside result_of.hpp, with no errors anywhere near my or Boost.Compute source code. It would be nice if the compilation could fail in more informative manners. 2) I did miss async versions of the algorithms, so it's possible to chain together multiple calls. Even though all the data sits on the compute device, the overhead of waiting for each operation to finish before queuing the next can make the compute gains completely irrelevant. 3) I think relevant calls should have a non-throwing form returning an error code, ala Boost.ASIO. 4) Threading has been mentioned in this list. At the very least the documentation should be updated to clearly state the thread safety of each call/class, ala Boost.ASIO. Beyond that I would like to be able to share a context between several threads, each which could contain their own queue and device. 5) If thread safety or similar important features requires a compiled part, I wouldn't mind Boost.Compute being non-header-only. Though if possible making it optional like other Boost libraries do would be great. 6) The tests, and preferably the performance tests as well, should have some way of testing all devices across all platforms. Currently they only test the default device on the default platform it seems. This is insufficient IMHO. 7) I'd like some way of defining user functions either as lambda expressions, raw OpenCL-C code via make_function_from_source or both, which can be used in lambda expressions for say transform(). Something like function<int (int)> sqr = _1 * _1; transform(inp.begin(), inp.end(), out.begin(), sqr(2 * _1 + 1)), queue); Overall I think Boost.Compute can be useful right now for some use-cases, and it has good potential to be significantly more useful with a bit more work. Just my 2 øre. Cheers - Asbjørn

4 5

[filesystem] imbue_utf8
by Peter Dimov 30 Dec '14

30 Dec '14

Since nowadays it's very common for programs to use UTF-8 for path encoding everywhere, I suggest that in addition to path::imbue( loc ), there should be path::imbue_utf8(), which imbues a UTF-8 codecvt facet. Since this is the default on Mac OS X, the implementation is already present, but the user has no way to get to it.

1 0

[config] Macro for detecting thread_local storage support
by Kyle Lutz 30 Dec '14

30 Dec '14

I have looked but been unable to find any macro in Boost.Config for detecting compiler support for the C++11 thread_local storage specifier. Does such functionality exist? I would like to use something like this to automatically detect compiler support for thread_local for use by the proposed Boost.Compute library. Currently I rely on the users defining BOOST_COMPUTE_HAVE_THREAD_LOCAL in order to enable support. Hopefully there is a better way? -kyle

2 1

Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
by Dave Gomboc 30 Dec '14

30 Dec '14

I get the digests, so I'm quoting from a number of different emails on this thread in this message. > > Both contain a fix for this. On stack overflow the proposed fix is > > literally a single line change. > > The issue is addressed in devel branch with somewhat better fix > long long time ago. It is important that tickets be updated to reflect such information. > > If there are issues fixed in develop branch, it would help a lot > > to inform users by updating the tickets accordingly. > > Here is a blanket update message: at this point all the issues with > Boost.Test are fixed on devel branch ;). This doesn't help people who filed a ticket (perhaps years ago) but don't happen to catch this email. > > This has been a problem for about 5 years and these simple fixes don't > > make it into the library. > > This is going to be released as part of the effort of merging devel into > master. Now, when this happens depends only on docs upgrade. It seems that in addition to documentation upgrades/improvements there is at least also the issue of identifying all Boost.Test-related tickets that are currently outstanding, verifying that the issue raised within them is indeed resolved within the development branch (rather than just assuming this is true), and updating the ticket to reflect that the problem has been resolved in the development branch (though it should not be closed yet until a new Boost release comes out with the fix in place). > All in all "devel to master upgrade" is one target I really want to reach > and is what I plan to concentrate my effort on. You are still welcome to > help with this if you are up to it. Excellent! If it has really been five years (or even if it has been only one full year) since this last happened, then may I suggest that this should be your sole target for Boost.Test until this task is accomplished, that your target should be prior to the next major release of Boost, and that obtaining assistance be an important part of your plan to accomplishing this task within this timeframe? To that end, could you please provide for the Boost community a detailed outline of exactly what remains to be done in order for the merge of the latest Boost.Test to master to be completed? Please be clear about exactly what others can help with, and in the cases where you think nobody else can help you, why that is so. Please do so here on the mailing list rather than ask people to contact you privately about it, so that more people will know what remains to be done and may be willing to lend a hand so it can get done. > > 1. What are the reason(s) why-list_content is not (yet) > > added to the release? Is there any schedule for its release? > > I need to document all these new features to release new Boost.Test Can you provide a list of these new features alphabetically by name with a one-sentence description? Boosters can sign up for writing documentation paragraphs, can contribute them here, and you can collect and use them. > > Yes. I fully agree with this statement. I hope to get back to this list > > with more concrete schedule soon. And if you are interested to push this > > even sooner - please feel free to help. > > That's great news. I know a vast amount of work has gone into develop > and we'll all benefit when it finally gets merged into master. Yes, I'm > happy to support this effort as best I can. Feel free to contact me > off-list. Rather than contact people off-list, I urge you to get all of the outstanding work into the open and use this mailing list for co-ordination not only so that people can contribute without overlapping their effort needlessly, but so that the current status is visible to all of us. That last point is rather important: I know of projects that have chosen alternative testing frameworks simply because of the lack of visibility re: Boost.Test. > Thanks for working hard to move this forward. Boost.Test has always been > a critical library and as a result somewhat of a thankless task to > maintain given the constant risk of breakage across Boost as a whole. > Thanks for persevering. I absolutely concur with this. Your efforts are appreciated, Gennady! You've been shouldering the entire burden for too long. I think that by publicly coordinating and leading the remaining effort to get the latest Boost.Test onto master, you'll be able to achieve this goal more quickly. Dave

3 3

[filesystem] Request for help with unresolved tickets
by Beman Dawes 29 Dec '14

29 Dec '14

Boost.Filesystem has roughly 140 unresolved tickets, and far too many are more that a year old. Some are up to four years old. That's horrible, and entirely my fault. I really dislike processing most bug reports, so leave them until I have nothing else to do, which is roughly never. But a few bug reports are actually fun to process. These are the ones that provide a little test program that unambiguously illustrates the problem and includes full information about the compiler, platform, version of boost, etc. To encourage more such dream tickets, I've added a little bug reporting framework with docs to filesystem's develop branch. It depends on a new header (boost/detail/lightweight_test_report.hpp) that's been added to the detail library's develop branch. The hope is that this will lead to more test programs that make it easy to reproduce bugs to (1) speed my processing of tickets and (2) ease handing off tickets to other developers for fixes. There are several ways boosters can help: * Review and try out the instructions at http://boostorg.github.io/filesystem/issue_reporting.html. (Don't expect all links to work.) Were you able to easily follow these instructions? What would you like to see added or removed? * Look through the bugs in https://svn.boost.org/trac/boost/report/53, pick one you think would benefit from a test program, and add a test program as described in http://boostorg.github.io/filesystem/issue_reporting.html. (Do a git pull on develop branch of detail and filesystem libraries first.) Were you able to easily follow these instructions? What would you like to see added or removed? Thanks, --Beman

3 2

[multiprecision] [detail] [number_base.hpp] Ambiguous partial specialization for canonical_imp
by Sergey Sprogis 29 Dec '14

29 Dec '14

It looks like boost/multiprecision/detail/number_base.hpp header in one of the later trunk versions has ambiguous partial specialization problem which Oracle Studio 12.4 C++ compiler detects. It can be also detected by gcc-4.8.2 as small 35 lines independent test case below made from this header shows. gcc -c -std=c++11 t.cc # gcc-4.8.2 compilation t.cc:17:62: error: ambiguous class template instantiation for 'struct canonical_imp<number<cpp_dec_float<50u>, (expression_template_option)1u>, cpp_dec_float<50u>, int_<3> >' CC -c -std=c++11 t.cc # Oracle Studio 12.4 C++ compilation "t.cc", line 17: Error: Ambiguous partial specialization for canonical_imp<Val, Backend, Tag><number<cpp_dec_float<50, int, void>, 1>, cpp_dec_float<50, int, void>, int_<3>>, canonical_imp<Val, Backend, int_<3>> and canonical_imp<number<B, 1>, Backend, Tag>. t.cc ================================== template< bool B> struct enable_if_c{ typedef bool type; }; template< int N > struct int_{}; enum expression_template_option {et_on=1}; template <class Backend, expression_template_option ExpressionTemplates> class number; template <class Val, class Backend, class Tag> struct canonical_imp { typedef int type; }; template <class B,class Backend,class Tag> struct canonical_imp<number<B,et_on>,Backend,Tag> { typedef B type; }; template <class Val, class Backend> struct canonical_imp<Val,Backend,int_<3>>{ typedef Val type; }; template <class Val, class Backend> struct canonical { typedef typename canonical_imp<Val, Backend, int_<3>>::type type; }; template<typename From, typename To> struct is_restricted_conversion { typedef bool type; }; template <class Backend, expression_template_option ExpressionTemplates> class number { public: number() {} template <class V> number(const V& v,typename enable_if_c<!is_restricted_conversion<typename canonical<V,Backend>::type,Backend>::value>::type * =0){} }; template <unsigned Digits10, class ExponentType = int, class Allocator = void> class cpp_dec_float; template <unsigned Digits10, class ExponentType, class Allocator> class cpp_dec_float { public: cpp_dec_float() {} }; template <class RealType> void instantiate(RealType) {} typedef number<cpp_dec_float<50>, et_on> test_type; void foo() { instantiate(test_type()); } =============================== Any suggestions how to fix this? Thanks, Sergey

2 2

[githelp] Pulling to arbitrary branch?
by Rene Rivera 29 Dec '14

29 Dec '14

I have a pull request against one branch (master). But I want to pull it into a different branch (develop). Is that possible? And if so, how? -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

2 5

[filesystem] ISO TS 18822, Technical Specification - File System
by Beman Dawes 29 Dec '14

29 Dec '14

The filesystem TS has been unanimously approved by ISO. 32 countries voted. The document has been forwarded to the ISO Central Secretariat for publication. The current working draft, which is technically the same as the TS but may have editorial corrections, is available at http://cplusplus.github.io/filesystem-ts/working-draft.html Many thanks to all the Boost folks who contributed so much to the Boost library that became the ISO TS! The C++ standards committee Filesystem Study Group will continue to operate, and will issue further TSes as further proposals dictate, and will continue to publish a working paper as issues for the TS are corrected. Happy Boost New Year, --Beman

1 0

What does "install dist-lib" in the inspect Jamfile do?
by Peter Dimov 29 Dec '14

29 Dec '14

I'm looking at Boost.Inspect's Jamfile as an example of how installation is done, and it has: install dist-bin : inspect : <install-type>EXE <location>../../../dist/bin : release ; install dist-lib : inspect : <install-type>LIB <location>../../../dist/lib : release ; The first one I get; it copies inspect.exe to dist/bin. But what does the second one do?

2 1

[core] A better boost::swap
by Antony Polukhin 29 Dec '14

29 Dec '14

Hi all, Ion Gaztañaga implemented a very good swap that used move emulation when possible and has all the features of boost::swap: http://www.boost.org/doc/libs/develop/boost/move/adl_move_swap.hpp I've tried to change default implementation of ::boost::swap to #include <boost/move/adl_move_swap.hpp> namespace boost { template<class T1, class T2> BOOST_GPU_ENABLED void swap(T1& left, T2& right) { ::boost::adl_move_swap(left, right); } } All the tests of the Boost.Swap passed. Ion's solution looks better than existing boost::swap. Are there any reasons not to change the existing implementation of Boost.Swap to Ion's version? -- Best regards, Antony Polukhin

7 9

Dependency Report (was RE: [core] A better boost::swap)
by Fletcher, John P 28 Dec '14

28 Dec '14

________________________________________ >From: Boost [boost-bounces(a)lists.boost.org] on behalf of Peter Dimov [lists(a)pdimov.com] >Sent: 27 December 2014 21:21 >To: boost(a)lists.boost.org >Subject: Re: [boost] [core] A better boost::swap >Andrzej Krzemienski wrote: ... >> http://www.pdimov.com/tmp/report-d5ca5be/module-levels.html >I've generated a new report at >http://www.pdimov.com/tmp/report-b1adfee/module-levels.html That is very interesting and helpful. Is there a location where it can be referenced? Thanks John

2 2

Interactive metaprogramming shells
by Abel Sinkovics 28 Dec '14

28 Dec '14

Hi, I've built interactive shells for preprocessor and template metaprogramming. I've been using them for development and debugging of metaprograms and I think Boost developers could also find them useful. You can type in (metaprogramming) expressions which get evaluated and the result is displayed immediately. For example you can type boost::mpl::push_front<boost::mpl::vector<int, char>, double>::type and you get boost_::mpl::vector<double, int, char> as the result (the boost_ namespace is used because there are some tricks there to make the output more readable). As an example for the preprocessor shell you can type BOOST_PP_REPEAT(3, foo BOOST_PP_TUPLE_EAT(3), ~) and you get foo foo foo as the result. The tools are based on the Boost.Wave library and Clang. You can get them here: Preshell for preprocessor: https://github.com/sabel83/preshell Metashell for template metaprograms: https://github.com/sabel83/metashell You can also try them from your browser here: http://abel.web.elte.hu/shell Feedback is welcome. Regards, Ábel

6 16