public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Trevor Saunders <tbsaunde@tbsaunde.org>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: David Malcolm <dmalcolm@redhat.com>,
	tbsaunde+gcc@tbsaunde.org,	gcc-patches@gcc.gnu.org,
	palves@redhat.com
Subject: Re: [PATCH 1/2] add unique_ptr header
Date: Sat, 05 Aug 2017 05:39:00 -0000	[thread overview]
Message-ID: <20170805053949.cou5rlh6pra5nw7y@ball> (raw)
In-Reply-To: <20170804195550.GA26610@redhat.com>

On Fri, Aug 04, 2017 at 08:55:50PM +0100, Jonathan Wakely wrote:
> On 01/08/17 23:09 -0400, Trevor Saunders wrote:
> > aiui C++03 is C++98 with a few additions to the stl.
> 
> Again, STL != C++ Standard Library.
> 
> C++03 made some important changes to the core language, particularly
> the value-initialization rules.
> 
> Most of the library changes were small bug fixes, and most were to
> locales (which didn't originate in the STL and aren't even templates)
> and iostreams (which didn't originate in the STL).
> 
> There were also changes to std::auto_ptr (also not from the STL) which
> this might rely on (I haven't checked).

I doubt it, as Pedro said in his email it originally copied code from
std::auto_ptr, but it doesn't use the standard libraries definition of
std::auto_ptr anywhere.  However please do feel free to look at the
implementation.

Trev

> 
> 

  reply	other threads:[~2017-08-05  5:39 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31 23:46 [PATCH 0/2] add unique_ptr class tbsaunde+gcc
2017-07-31 23:46 ` [PATCH 2/2] use unique_ptr some tbsaunde+gcc
2017-07-31 23:46 ` [PATCH 1/2] add unique_ptr header tbsaunde+gcc
2017-08-01 14:40   ` David Malcolm
2017-08-02  3:09     ` Trevor Saunders
2017-08-04 19:55       ` Jonathan Wakely
2017-08-05  5:39         ` Trevor Saunders [this message]
2017-10-11 18:52           ` David Malcolm
2017-10-12 14:08             ` Trevor Saunders
2017-10-13  3:05               ` [PATCH] Add gnu::unique_ptr David Malcolm
2017-10-13  9:36                 ` Richard Biener
2017-10-13 12:08                   ` Pedro Alves
2017-10-14  0:35                     ` [PATCH] Implement unique_xmalloc_ptr<T[]> and add more selftests David Malcolm
2017-10-16 10:53                       ` Pedro Alves
2017-10-16 21:04                         ` [committed] Add gnu::unique_ptr David Malcolm
2017-10-19 17:27                           ` Gerald Pfeifer
2017-10-19 17:41                             ` David Malcolm
2017-10-22 11:40                               ` Gerald Pfeifer
2017-08-02  8:14     ` [PATCH 1/2] add unique_ptr header Richard Biener
2017-08-01  0:51 ` [PATCH 0/2] add unique_ptr class David Malcolm
2017-08-04 18:52 ` Jonathan Wakely
2017-08-05  5:36   ` Trevor Saunders
2017-08-07 13:01     ` Jonathan Wakely
2017-08-05 19:05   ` Pedro Alves
2017-08-11 21:30     ` Jonathan Wakely
2017-09-03  1:24       ` Trevor Saunders
2017-09-04  9:31       ` Richard Biener
2017-09-04 10:05         ` Pedro Alves
2017-09-05 16:52     ` Manuel López-Ibáñez
2017-09-05 17:40       ` Pedro Alves
2017-09-06 12:35         ` replace libiberty with gnulib (was: Re: [PATCH 0/2] add unique_ptr class) Manuel López-Ibáñez
2017-08-04 22:43 ` [PATCH 0/2] add unique_ptr class Martin Sebor
2017-08-05  5:32   ` Trevor Saunders

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=20170805053949.cou5rlh6pra5nw7y@ball \
    --to=tbsaunde@tbsaunde.org \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely@redhat.com \
    --cc=palves@redhat.com \
    --cc=tbsaunde+gcc@tbsaunde.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).