- Boost - lists.preview.boost.org

[GIL] 2D Convolution/Correlation Proposal for gsoc 2021
by Gaurav kumar 12 Mar '21

12 Mar '21

Hi, I am Gaurav Kumar; I have been working on the Boost.GIL library for the past month. I would like to work on the 2D convolution/Correlation project. The ideas for the project are as follows: 1. Separable Kernels <http://www.dspguide.com/ch24/3.htm>: Most of the standard kernels (e.g. Gaussian, Sobel) can be separated into 2 or more 1D filters. For a N x N kernel, separating it into two 1D filters, the number of computations required would now be proportional to 2*N instead of N*N for the naive implementation. This implementation would also favor code reusability as this would only require a kernel separating function and driver code for a group of 1D filters. 2. Generic Implementation for 2D convolution: There are more generic kernels that are non-separable (e.g. Laplacian operator). In this case, the naive approach has already been implemented. The main task would be to provide the same set of functions as in the 1D convolution/correlation implementation. One potential idea for optimization of 2D convolution is to use the Im2col <https://www.programmersought.com/article/6306124604/> operation, in which the input image is converted into a row of column vectors, where each column vector represents an image block for which convolution/correlation operation is to be performed. The kernel can also be flattened out in a similar manner, resulting in a 1D array. This results in the convolution operation being reduced to matrix multiplication, which can be handled efficiently by BLAS libraries <https://en.wikipedia.org/wiki/Basic_Linear_Algebra_Subprograms> ( Boost.uBLAS ). Please share any suggestions you would have, related to the ideas presented above, or regarding 2D convolutions in general. I am looking for a mentor to guide me through this project. Best Regards, Gaurav Kumar Github handle: https://github.com/gkumar28

2 1

[release] Boost 1.76.0 Beta 1 Release Candidate 1
by Marshall Clow 12 Mar '21

12 Mar '21

The first release candidates for the 1.76.0 beta release are now available at: <https://dl.bintray.com/boostorg/beta/1.76.0.beta1/source/> The SHA256 checksums are as follows: a222d325cd3c9f66951ec9026eca6ff6f48dd563c9a025911d598d2aca8770ce boost_1_76_0_b1_rc1.tar.bz2 6b90b510a3de38fc30a071ac798da37545fb60a1d6b21aed1130b47c9c598977 boost_1_76_0_b1_rc1.zip b01627bd9ce934b092037da81696bb4482a44e6a31c8791dbed82eafe04b69fa boost_1_76_0_b1_rc1.tar.gz dbef57adbab1d4395d14000f0a2420fc82f87476e10d48359ceff7125a74b77a boost_1_76_0_b1_rc1.7z As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release managers

7 10

Endorsement, review manager sought for Boost.Mysql
by Ruben Perez 12 Mar '21

12 Mar '21

Hi all, I would like to propose a MySQL client library for Boost (under the original name of Boost.Mysql). It is a full implementation of the MySQL client protocol, based on Boost.Asio. It requires C++11. The library is at https://github.com/anarthal/mysql and the documentation is at https://anarthal.github.io/mysql/. Examples under https://anarthal.github.io/mysql/mysql/examples.html. The purpose of this library is to provide a low-level building block for applications or other libraries to interact with MySQL, in the same way Boost.Beast provides a way to interact with HTTP. It complies with Boost.Asio universal asynchronous model, and provides the usual sync and async overloads for every network operation. Some notes: - The scope of this library is limited to MySQL. Its value proposition is implementing the client protocol in an Asio-compliant way. Supporting any database other than MySQL is not in scope of this library. - This library does NOT make use of MySQL libmysqlclient C API. It provides a from-the-ground-up implementation of the MySQL client protocol. Features: - Text queries and server-side prepared statements. - Sync and async functions, following Boost.Asio's universal async model. You may use callbacks, Boost coroutines, futures, C++20 coroutines, or any completion handler that Asio adds support for. - Can be used with any Stream including TCP sockets, UNIX sockets and Boost.Beast TCP streams. - Supports MySQL 5.x, MySQL 8.x and MariaDB.

10 17

[Boost][Describe] Has been ACCEPTED into Boost
by Richard Hodges 12 Mar '21

12 Mar '21

Dear all, I am pleased to announce that we have received 13 high quality reviews. There has been no dissent, with every reviewer recommending that Describe be accepted. Reviews that were sent to me privately have been forward to Peter for consideration. If you have submitted a review and I have not responded privately to thank you, then please accept my apology for this oversight. Thank you everyone for taking some of your valuable time to contribute. -- Richard Hodges hodges.r(a)gmail.com office: +442032898513 home: +376841522 mobile: +376380212

3 2

[interprocess][managed_shared_memory] Memory allocation of managed shared memories
by Grimm, Matthias 12 Mar '21

12 Mar '21

Hi, I have a question regarding the interprocess library and the use of shared memories. When creating a boost::interprocess::managed_shared_memory it seems to be necessary to take some additional space into account. In my case the following approach works well: managed_shm = new ip::managed_shared_memory(ip::create_only, "shm_id", (vec_elems + 110) * (number_of_samples + 1)); Following this it seems to be necessary to always have one additional element. If I remove the additional element (vec_elems + 110) * (number_of_samples) an exception is thrown: boost::interprocess::bad_alloc. This is also the case if I change to (vec_elems) * (number_of_samples + 1) Does anybody know why it is necessary to have this additional space allocated? What is the exact minimum size to avoid the exception? The additional memory may become a problem if the size of the vector elements is large. Attached you'll find some example code. Any help on this topic would be appreciated.

1 0

GSoC'21
by Manan Sharma 12 Mar '21

12 Mar '21

Hey, My name is Manan Sharma, I went through the project ideas for the GSoC'21 and the Multiprecision project really caught my eye. So I would like to contribute to this project but do not know where to start. I have basic knowledge of C++ like Template Programming. So I would appreciate it if anyone could tell me how to get started. Looking forward to contributing to the project. Yours sincerely, Manan Sharma Phone No.: +91 9711306818 Email Id.: manan180796(a)gmail.com

2 1

Queries regarding Contributing to boost open source library
by Tirtharaj Sen 12 Mar '21

12 Mar '21

Hello, I'm Tirtharaj Sen I wanted to know that I will start to contribute to boost open source library from today , so will can I make proposals for GSOC 2021 to the organisation or am I a bit late to start to contribute. I would also like to mention that I want to be associated with the organisation even after the GSOC is over. So does it require a 3 months of contribution history? Will be obliged if I get help from yours's side Thank you

2 1

Does anyone use mp11 with VS2013?
by Peter Dimov 11 Mar '21

11 Mar '21

Does anyone here use mp11 with Visual Studio 2013? (msvc-12.0) 2013 kind of supports C++11 but only barely, and I keep bumping into its bugs and limitations, so I'm considering dropping it and making 2015 the minimum requirement.

1 0

[Boost] [Describe] library submission - last call for reviews from the community
by Richard Hodges 11 Mar '21

11 Mar '21

A friendly reminder that the review period for [Boost.Describe] will finish at the end of tomorrow - 10th March 2021 We've had some excellent feedback already, and would value more. If you can spare a few hours of your valuable time, please consider reviewing this neat little library and posing your results on this mailing list. The invitation is repeated below: The Boost formal review of the Describe starts Monday, taking place from March 1st, 2021 to March 10th, 2021 (inclusive). The library is authored by Peter Dimov. Documentation: https://pdimov.github.io/describe/doc/html/describe.html Source: https://github.com/pdimov/describe The library provides a simple means of providing reflection for structures and enums in C++. The documentation contains a number of common motivating examples, including: - A universal print function https://pdimov.github.io/describe/doc/html/describe.html#example_print_func… - JSON serialisation https://pdimov.github.io/describe/doc/html/describe.html#example_to_json Please provide in your review information you think is valuable to understand your choice to ACCEPT or REJECT including Describe as a Boost library. Please be explicit about your decision (ACCEPT or REJECT). Some other questions you might want to consider answering: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With which compiler(s)? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? More information about the Boost Formal Review Process can be found at: http://www.boost.org/community/reviews.html The review is open to anyone who is prepared to put in the work of evaluating and reviewing the library. Prior experience in contributing to Boost reviews is not a requirement. Thank you for your efforts in the Boost community. They are very much appreciated. Richard Hodges - review manager of the proposed Boost.Describe library Peter is often available in the CppLang Slack #boost channel should you require any clarification not covered by the documentation, as am I. Please submit your review to the Boost mailing list: boost(a)lists.boost.org -- Richard Hodges hodges.r(a)gmail.com office: +442032898513 home: +376841522 mobile: +376380212

3 6

[release] Reminder about 1.75.0 release notes
by Marshall Clow 11 Mar '21

11 Mar '21

The master branch is closing on Wednesday for the 1.75.0 release. If you have information that should go into the release notes, now’s the time to add it. Create a PR against https://github.com/boostorg/website/blob/master/feed/history/boost_1_75_0.q… <https://github.com/boostorg/website/blob/master/feed/history/boost_1_75_0.q…> — Marshall

2 3