Dear Boost,
Google Code In 2014 is nearly upon us, and we need bite sized tasks
and mentors! Google Code In lasts between December and mid-January
and is for 13 to 17 year olds to get involved with open source
projects. Tasks need to be very short, maybe only three hours or so,
but correspondingly the effort required to mentor/check these is very
low. If you maintain a Boost library and could do with help in fixing
up any of those items you keep putting off like replicating bug
reports, fixing documentation errors, or configuring Continuous
Integration, now is the time!
More information is on the GCI ideas page at:
https://svn.boost.org/trac/boost/wiki/gci2014
... where you can add more tasks and also sign yourself up as a
mentor.
We need this page ready by Saturday 8th November, so please try to
get it done before then. Thanks in advance!
Niall
--
ned Productions Limited Consulting
http://www.nedproductions.biz/http://ie.linkedin.com/in/nialldouglas/
On Fri, 31 Oct 2014 12:14:33 +0100, Thorsten Ottosen <tottosen(a)dezide.com>
wrote:
> I'm very happy to see a small chapter on ptr_container.
> It's good that you compare it with container<unique_ptr<T>>.
>
It looks like poly_collection is left out:
http://bannalia.blogspot.com.es/2014/05/fast-polymorphic-collections.html
There was discussion of this container on this list back in August.
> Comment 1: I would prefer examples with unique_ptr to use make_unique.
>
I've compared these two lines:
auto req=::std::unique_ptr<cmw_request>(::new cmw_request(localbuf));
auto req=::std::make_unique<cmw_request>(localbuf);
On clang 3.3, the make_unique version increases the size
of an executable's text segment by 112 bytes. I think I've
tried it on a newer compiler and found similar results.
--
Brian
Ebenezer Enterprises - In G-d we trust.
http://webEbenezer.net
[ Please disregard previous message; apparently I am brain-dead this morning. The uploaded files are correct, though. ]
Release candidate files for 1.57.0 are available at
http://boost.cowic.de/rc/
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.
This helps ensure the candidates build OK before we push them out to SourceForge.
The files (and associated md5s) are:
MD5 (./boost_1_57_0_rc1.7z) = 17c98dd78d6180f553fbefe5a0f57d12
MD5 (./boost_1_57_0_rc1.tar.bz2) = 1be49befbdd9a5ce9def2983ba3e7b76
MD5 (./boost_1_57_0_rc1.tar.gz) = 25f9a8ac28beeb5ab84aa98510305299
MD5 (./boost_1_57_0_rc1.zip) = 5e040e578e3f0ba879da04a1e0cd55ff
Thanks!
-- The release managers
P.S. Release notes are here: http://www.boost.org/users/history/version_1_57_0.html
