All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Elsayed <eternaleye@gmail.com>
To: ceph-devel@vger.kernel.org
Cc: ceph-users@lists.ceph.com
Subject: Re: C++11 and librados C++
Date: Tue, 04 Aug 2015 09:56:46 -0700	[thread overview]
Message-ID: <mpqqse$8ri$3@ger.gmane.org> (raw)
In-Reply-To: alpine.DEB.2.00.1508040550250.22099@cobra.newdream.net

Sage Weil wrote:

> On Tue, 4 Aug 2015, Wido den Hollander wrote:
>> On 03-08-15 22:25, Samuel Just wrote:
>> > It seems like it's about time for us to make the jump to C++11.  This
>> > is probably going to have an impact on users of the librados C++
>> > bindings.  It seems like such users would have to recompile code using
>> > the librados C++ libraries after upgrading the librados library
>> > version.  Is that reasonable?  What do people expect here?
>> 
>> Well, some people use Qemu build by their distro, but they use librados
>> / librbd from ceph.com
>> 
>> So if they suddenly have to rebuild Qemu that would hurt them I think.
> 
> Qemu fortunately is using the C bindings, so it would not be affected.
> It is only the C++ ABI (or lack thereof) that is problematic.
> 
> What users of the C++ bindings are there out there?

One thing I think is worth noting: GCC 5 represents an ABI break for C++11 
http://developerblog.redhat.com/2015/02/05/gcc5-and-the-c11-abi/

Thus, some serious care is needed to avoid compat hazards when using C++11.


      reply	other threads:[~2015-08-04 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 20:25 C++11 and librados C++ Samuel Just
2015-08-04 10:46 ` Wido den Hollander
2015-08-04 12:51   ` Sage Weil
2015-08-04 16:56     ` Alex Elsayed [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='mpqqse$8ri$3@ger.gmane.org' \
    --to=eternaleye@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph-users@lists.ceph.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.