All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@inktank.com>
To: Noah Watkins <noah.watkins@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
	Gregory Farnum <greg@inktank.com>,
	Gregory Farnum <gregory.farnum@inktank.com>
Subject: Re: feedback on supporting libc++
Date: Tue, 31 Dec 2013 10:59:47 -0800	[thread overview]
Message-ID: <52C31423.20007@inktank.com> (raw)
In-Reply-To: <CA+Hcz5-Gs03049M-o1uEgd1SoTnrkMZfrAVYhLJHD8g+AcRu5Q@mail.gmail.com>

On 12/31/2013 08:59 AM, Noah Watkins wrote:
> Thanks for testing that Josh. Before cleaning up this patch set, I
> have a few questions.
>
> I'm still not clear on how to handle the "std::tr1::shared_ptr <
> ObjListCtx > ctx;" in librados.hpp. If we change this to
> ceph::shared_ptr, then we'll also need to some how ship with the
> translations here:
>
>    https://github.com/ceph/ceph/blob/port/libc%2B%2B/src/include/memory.h

I'd suggest treating it like we did buffer.h and associated headers -
make a symlink to it from include/rados/memory.h, and install a copy of
it with the librados headers.

> It's also not clear that ceph::shared_ptr should be exposed publically
> if there is a thought we might start switching out implementations of
> ceph::shared_ptr via memory.h (e.g. by using boost implementation).

We can't change the actual type used by librados, since AIUI that's
part of the ABI, so if we want to use another type internally we can
make include/rados/memory.h a copy of the original instead of a symlink,
and then change the internal include/memory.h however we like.

Josh

  reply	other threads:[~2013-12-31 18:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 22:51 feedback on supporting libc++ Noah Watkins
2013-10-30 16:13 ` asomers
2013-10-30 19:02 ` Josh Durgin
2013-12-27 23:34   ` Noah Watkins
2013-12-31  1:19     ` Josh Durgin
2013-12-31 16:59       ` Noah Watkins
2013-12-31 18:59         ` Josh Durgin [this message]
2014-01-09 19:54           ` Noah Watkins

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=52C31423.20007@inktank.com \
    --to=josh.durgin@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=greg@inktank.com \
    --cc=gregory.farnum@inktank.com \
    --cc=noah.watkins@inktank.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.