You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Craig Hansen-Sturm (JIRA)" <ji...@apache.org> on 2014/08/04 20:22:13 UTC
[jira] [Comment Edited] (MESOS-1626) Add support for C++11 (+Boost)
to stout
[ https://issues.apache.org/jira/browse/MESOS-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084982#comment-14084982 ]
Craig Hansen-Sturm edited comment on MESOS-1626 at 8/4/14 6:22 PM:
-------------------------------------------------------------------
Hello Tim ... Greetings and thanks for the reply.
I've since discovered the README in the boost tarball which describes the updating/staging process. The patch + tarball update are now ready for review. I've managed to encapsulate enough of atomic support so that we have a good common implementation between C++11 and boost::atomic (used for non C++11 implementations).
was (Author: craig-mesos):
Hello Tim ... Greetings and thanks for the reply.
I've since discovered the README in the boost tarball which describes the updating/staging process. These patches are ready for review. I've managed to encapsulate enough of atomic support so that we have a good common implementation between C++11 and boost::atomic.
> Add support for C++11 (+Boost) <atomic> to stout
> ------------------------------------------------
>
> Key: MESOS-1626
> URL: https://issues.apache.org/jira/browse/MESOS-1626
> Project: Mesos
> Issue Type: Improvement
> Components: libprocess
> Reporter: Craig Hansen-Sturm
> Assignee: Craig Hansen-Sturm
> Priority: Minor
> Attachments: boost-1.53.0.patch
>
>
> Integrate c++11/atomic into libprocess/stout following the pattern introduced by c++11/memory and c++11/lambda. The primary difference in this case, is that tr1 did not include support for <atomic>, this has to come from boost/atomic which was introduced in v1.53. This task will include a patch to update boost as well.
--
This message was sent by Atlassian JIRA
(v6.2#6252)