February 2015 - Boost - lists.preview.boost.org

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 14 Feb '15

14 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 12 Feb '15

12 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 12 Feb '15

12 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