Hi everyone,
The review of Boost.Align by Glen Fernandes is scheduled from Friday, April 11th to April 20th.
Source:
http://github.com/glenfe/align
Documentation:
http://glenfe.github.io/align
Description:
This library provides function align for implementations which do not have the C++11 standard library align function available.It
provides allocation functions aligned_alloc and aligned_free as their
functionality is not yet available in the C++ standard library. They use
platform specific functions, if available, or use standard library
functions in conjunction with align.It
provides C++ allocators, class templates aligned_allocator and
aligned_allocator_adaptor, which respect alignment. The first uses
aligned_alloc and aligned_free while the second uses the allocator in
conjunction with align.It also provides function is_aligned to test the alignment of a pointer.
Rationale:
C++11
added the ability to specify increased alignment (over-alignment) for
class types. Unfortunately, ::operator new allocation functions, new
expressions, and the default allocator, std::allocator, do not support
dynamic memory allocation of over-aligned data.
The aligned_alloc function can be used in place of ::operator new to specify the alignment of the memory allocated.The aligned_allocator class template can be used in place of std::allocator as an alignment-aware default allocator.The aligned_allocator_adaptor class template can be used to adapt any allocator into an alignment-aware allocator.
Notes:
The functionality provided by this library addresses needs
in existing Boost libraries as well. Boost.SmartPtr has its own
implementation of align, and Boost.Log and Boost.Interprocess have their
own implementations of aligned_alloc and aligned_free.
Boost List Discussion:
http://lists.boost.org/Archives/boost/2014/02/211723.php
Review Manager:
Ahmed Charles
Dear Boost Community,
The Google Summer of Code 2014 proposals for Boost are in, and we
would deeply appreciate the community's help in ranking the proposals
according to merit before the 1st of April.
To vote, the process is easy:
1. Go to this page
https://www.google-melange.com/gsoc/homepage/google/gsoc2014 and
click the "Log in" button under Mentors and Administrators.
2. Now click "Create Profile" on the same page. Note that even if you
registered last year, you must register again in 2014. Fill in the
form. Note that after submitting it drops you at "Edit Profile",
which is confusing.
3. Click "My Dashboard", then "Connect with organisations".
4. Choose "Boost C++ Libraries".
5. In the message box, write this: "I am a member of the Boost
community and the email(s) I normally post to boost mailing lists
with is <email>" filling in the email address(es) you normally use to
post to boost mailing lists. This lets us verify that you are indeed
a long standing member of the Boost community.
6. Once we approve your request, you will get an email with the
subject "Welcome as organisation member". You can now return to the
Dashboard on the GSoC website where there will be a new item
"Proposals".
7. Work your way through as many of the 42 proposals as you can. You
can score them using the stars at the bottom of each proposal page,
taking care to read any comments by the mentors and students if
present. PLEASE try to rank some of the lowest scored proposals,
every year we get a lot of people who only rank the top five and
don't bother with the rest. Try to score on the basis of (i) proposal
quality and your best estimate of the student's capability (ii) if
the student came early to the mailing lists to ask for help writing
the proposal (the mentors who helped them with their proposals have
usually indicated this in the private comments) (iii)
usefulness/appropriateness of the feature or work being proposed.
Remember a good GSoC is more about getting promising new engineers
into Boost and C++ than necessarily getting code to pass Boost peer
review in a single summer.
8. Optional: If a proposal looks especially great to you and you feel
able to mentor a student this year, please slide the "wish to mentor"
button. Just because a proposal already has willing mentors does NOT
mean you should not add yourself - we have at least two mentors with
many attached very highly ranked proposals and we really don't want
to have to reject an outstanding proposal just because we can't find
the mentors for it as no mentor can realistically mentor more than
two projects simultaneously.
As you know, Google Summer of Code is usually worth $35,000 - $50,000
to Boost each year, and a successful GSoC raises our visibility and
reputation in the wider open source community. Our thanks to you in
advance for taking the time to vote.
Niall Douglas
Boris Schäling
---
Boost C++ Libraries Google Summer of Code 2014 admin
https://svn.boost.org/trac/boost/wiki/SoC2014
