[
https://issues.apache.org/jira/browse/MESOS-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803101#comment-13803101
]
Benjamin Mahler commented on MESOS-750:
---------------------------------------
Thanks [~tstclair]! We currently have wrappers for things like shared_ptr so we
should be able to do this fairly easily. Do you have any advice on ABI
compatibility when dealing with our third party libraries living outside our
code?
We'll have to run the [suggested
commands|http://gcc.gnu.org/wiki/Cxx11AbiCompatibility] to see the extent of
the possible issues, but just as an example, it appears to be unsafe if a
std::list is passed or returned through the library and it's not built for
C++11.
{quote}
ABI Changes
`std::list, std::_List_impl, and std::_List_base`
[In gcc-4.7.0 and gcc-4.7.1 only]
New _M_size member, meaning any method that adds or removes nodes or inspects
the size has a new ABI.
This is unsafe if the signatures are exported or if a std::list is passed to or
returned from an exposed function.
{quote}
> Require compilers that support c++11
> ------------------------------------
>
> Key: MESOS-750
> URL: https://issues.apache.org/jira/browse/MESOS-750
> Project: Mesos
> Issue Type: Improvement
> Reporter: Benjamin Mahler
> Labels: technical_debt
> Fix For: 0.16.0
>
>
> Requiring C++11 support will provide substantial benefits to Mesos.
> Most notably, the lack of lambda support has resulted in a proliferation of
> continuation style functions scattered throughout the code. Having lambdas
> will allow us to reduce this clutter and simplify the code.
> This will require carefully documenting how to get Mesos compiling on various
> systems to make this transition easy.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
