From: Benjamin Kosnik <benjamin.kosnik@gmail.com>
To: "Jonathan Wakely" <jwakely.gcc@gmail.com>
Cc: libstdc++ <libstdc++@gcc.gnu.org>, gcc-patches@gcc.gnu.org
Subject: Re: [patch] Improving shared_ptr for C++0x
Date: Wed, 14 Nov 2007 01:37:00 -0000 [thread overview]
Message-ID: <20071113181314.1af9194c@concorde.artheist.org> (raw)
In-Reply-To: <4348dea50711131546n63e7f83brc8bfd1b15e6fab6c@mail.gmail.com>
> New tests and docs on the implementation choices are included. There
> are a few places where further work could be done, see the new HTML
> file for details. That doc is also available at
> http://www.kayari.org/doc/c++/shared_ptr.html to save you reading the
> HTML. I haven't linked to the new doc from any existing pages yet as
> the C++0x status is still experimental and I don't know where these
> sort of implementation notes will fit in Benjamin's new doc plan.
Just to answer this last part.
Status for C++0x stuff should go in
docs/html/17_intro/c++0x_status.html. You can put the paper numbers as
links in the notes sections if you'd like. It would be great if you
could correct this document WRT shared_ptr and related items.
FYI, this document is not complete currently. Instead,
it's the tr1_status.html document "ported" to the C++0x draft. I believe
appendix C to be wrong, for instance, but most of the other bits are
fine.
It doesn't actually track (at the moment) anything after tr1, ie
variadic templates, move semantics, or anything here:
http://gcc.gnu.org/projects/cxx0x.html
This needs to be fixed, obviously, but I figure it can be done
incrementally. To be quite honest, I'm not quite sure of the state of
the move semantics work myself, so I didn't want to attempt it.
;)
-benjamin
next prev parent reply other threads:[~2007-11-14 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 1:25 Jonathan Wakely
2007-11-14 1:37 ` Benjamin Kosnik [this message]
2007-11-14 19:07 ` Benjamin Kosnik
2007-11-15 10:11 ` Jonathan Wakely
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=20071113181314.1af9194c@concorde.artheist.org \
--to=benjamin.kosnik@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=libstdc++@gcc.gnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).