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

[GSoC] Boost.multiprecision project
by Flórián Deé 22 Apr '13

22 Apr '13

Hello, I'm Florián Deé from Hungary, studying at Budapest University of Technology and Economics. I'm really interested in the Boost.Multiprecision project for GSoC 2013. A little background on myself, I'm an undergraduate software engineering student mostly into C and C++, with interests in low level programming and maths. I'm currently working on a project as an outsider member of the dorm's Coder team (a poker framework for AIs), and I'm also a "consultant" for students with their C/C++/Maths assignments (mostly calculus and linear algebra). As a result, I don't really have much free time till the exams, but I've planned, seen, written and debugged lots of different projects with different coding styles. Going through the project description, I think my skill set and interests would fit in nicely, with the exception of fast Fourier transforms, which I'm only mildly familiar with, but I'd gladly read any needed extra material till summer. So I kindly seek your guidance to help me go about my application for the GSoC 2013. Looking forward to your reply. Regards, Flórián

2 1

[ublas] bugfix for matrix operation /
by Mario Mulansky 22 Apr '13

22 Apr '13

Hi, I wanted to add an elementwise divide operations for ublas matrices using operator / Unfortunately, there is operator/ defined for matrix and integral types which hides any other operator definition (matrix_expression.hpp l. 3388) and thus makes it impossible to add this functionality. I would like to add an enable_if statement there that checks if the second argument is convertible to matrix::value_type, as is done for other operators. Who would be responsible for this small change? I can provide the according patch, it's almost trivial. Mario

4 7

[gsoc-2013] Physics Library Abstraction Layer
by Preston Hamlin 22 Apr '13

22 Apr '13

I am working on putting together a draft proposal for the project. Is there a preferred format desired? I was going to use a PDF since they are quite portable. I am somewhat confused as to the scope of the project, due to the previous posts in this thread. Is the library to be built upon a specific physics library (PhysX for instance) by utilizing existing code in the respective SDK to abstract away much of the object management? Or is it meant to be built from the ground up to create generic objects, which can then be translated into an arbitrary format for an existing library? Thank-you, -Preston

2 3

library to support async/await pattern
by Valentin Milea 21 Apr '13

21 Apr '13

Is there interest for a coroutine-based library to make asynchronous APIs easier to deal with? Typically, for each task there is cruft: chaining callbacks, managing intermediate state and error codes (since exceptions don't fit this model). The code flow get inverted and becomes difficult to follow. Recent versions of F# and C# solve this problem. They implement an await operator that effectively suspends the executing method until a task completes. The compiler takes care of transforming subsequent code into a continuation. Everything runs on the main thread, with asynchronous methods spending most time awaiting. N3328 proposes resumable functions of this kind in C++. For an immediate solution we could leverage the Boost.Context/Coroutine library. The resulting code may look like this: try { task = do_a_async(...) // yield until task done task.await(); } catch (const some_exception& e) { // exceptions arrive in awaiting context } // normal code flow for (auto& task : tasks1) { task.await(); } taskAny = await_any(tasks2); taskAny.await(); ... There needs to be a representation for Awaitable tasks (similar to std::future but non-blocking). The other requirement is to have a Scheduler (run loop) in order to weave between coroutines. Benefits: - normal code flow: plain conditionals, loops, exceptions, RAII - algorithm state tracked on coroutine stack - async tasks are composable - any async API can be wrapped Cons: - must wrap async APIs (e.g. Boost.Asio) - needs std::exception_ptr to dispatch exceptions - stackful coroutines are sometimes difficult to debug I wrote an open-source library that does this: https://github.com/vmilea/CppAwait. It's far from Boost style but the concept looks sane. For a comparison between async patterns please see: https://github.com/vmilea/CppAwait/blob/master/Examples/ex_stockClient.cpp Making a Boost version would involve serious redesign. So is this worth pursuing? Thanks!

5 9

Re: [boost] GSoC: More mentors?
by Christopher Kormanyos 21 Apr '13

21 Apr '13

> From Monday on students can apply for GSoC projects. > Mentors can already apply at > <https://google-melange.appspot.com/gsoc/homepage/google/gsoc2013>. > So far we have four possible mentors (for uBLAS, odeint, > graph and benchmark). Are there others who would like > to mentor? Then please pick a project from > <https://svn.boost.org/trac/boost/wiki/SoC2013> or propose > your own. > Thank you, Boris Hello, Christopher Kormanyos (who is me) just signed up as a potential mentor for the GSoC projects with Boost.Math and Boost.Multiprecision. We have already had contact with some good candidates. Thank you. Sincerely, Chris.

1 0

GSOC - Boost.uBLAS interest
by deck léa 21 Apr '13

21 Apr '13

Hi Boost C++ Team ! My name is Lea Deck, I'm French and I study in fourth year in computer science (security in computer science), but I really like mathematics. So I look for projects that mix the two. I would be interesting in adding new mathematics properties to your uBLAS libraries, like Hadamard, Toeplitz and Block matrices, the generation of matrices, Strassen multiplications and possibly new algorithms. You also alluded to the Bernoulli numbers, but I don't see any mention in the list of new features. Is the project still available? If so, should its implementation also contain the Bernoulli polynomials? About the question of optimisation, I have some skills in Cuda (GPU) and OpenMP and so in parallelization of code. So I am able to produce a correct parallelized code. Also, my knowledge of C++ is beginning to spread to the use of C++11 ( including unordered structure map). One last question, what do you mean by "Pretty display" in your list of new features? My CV is available here <http://dla.immortal-pc.info/>. ( http://dla.immortal-pc.info/) Thank you for taking the time to read my e-mail, and I look forward to receive a response from you. With regards, DECK Léa

1 0

[GSoC 2013] SVN?
by Vicente J. Botet Escriba 21 Apr '13

21 Apr '13

Hi, would all the GSoC projects be stored under SVN? Best, Vicente

3 5

Qustion about GSOC Project
by Hardy Huang 20 Apr '13

20 Apr '13

Hi, there. I am a graduate student in Peking University. I have known Boost library for long. And I used it for several times. This year I wanted to get involved in GSOC, and I was happy when I see Boost in the list, it is my dream and it will be honor to contribute to such a powerful library. Since I am good at algorithm and data structure, knowing that there are some idea projects relative with algorithm and data structure, like radix sort, trie, I want to know something detail about the plan to develop algorithm and data structure. Thanks, I am expecting to receive some useful replies.

4 6

Re: [boost] [config][mpl][type_traits][integer] BOOST_STATIC_CONSTANT should use constexpr
by Vicente J. Botet Escriba 20 Apr '13

20 Apr '13

Le 20/04/13 14:33, Vicente J. Botet Escriba a écrit : > Le 20/04/13 13:18, Antony Polukhin a écrit : >> 2013/4/20 John Maddock<boost.regex(a)virgin.net>: >> <...> >>> No that's correct as is: >>> >>> * if BOOST_NO_INCLASS_MEMBER_INITIALIZATION is defined, then the constant is >>> really an enum and there should be no out-of-line definitions. >>> * if BOOST_NO_INCLASS_MEMBER_INITIALIZATION is *not* defined, then the >>> constant *should* have the out-of-line definition in case it's address is >>> taken/used. >> Oh, now I see, thanks. >> >>> As for the original question, this is such a pervasive breaking change, I >>> think a new macro is inevitable I'm afraid :-( >> New macro will do exactly what the old macro did, but using C++11 >> feature. Code in all Boost libraries will be changed to use new macro. >> So the old macro will be required only for users code that use macro >> and attempts to take address of constant... >> >> To me, it looks less obscuring to have one macro and a note for users >> to use BOOST_CONSTEXPR_OR_CONST for out-of-line definition; than two >> macro (which one shall be used by default?) that do the same thing but >> very slightly differ in details. >> > Just to add some information about some uses > > grep -r BOOST_NO_INCLASS_MEMBER_INITIALIZATION * | wc -l > 113 > grep -r BOOST_STATIC_CONST * | wc -l > 6598 > The figures are a little bit better :) grep -r BOOST_STATIC_CONSTANT * | grep -v svn | wc -l 3030 grep -r BOOST_NO_INCLASS_MEMBER_INITIALIZATION * | grep -v svn | wc -l 57 Best, Vicente

1 0

Trac: Add ref library
by Vicente J. Botet Escriba 20 Apr '13

20 Apr '13

Hi, Boost.Ref is not included as a library on the Trac system. Coul dit be added? Best, Vicente

1 0