use unique_ptr instead of auto_ptr in c++11 mode

Use unique_ptr instead of auto_ptr in c++11 mode.

Tested with gcc 4.8.1 on linux with -std=gnu+=11 and -std=c++11.

[mostynb, 2014-03-19 23:11:05]

Please take a look...

[Lincoln, 2014-04-08 18:55:17]

Thanks very much for the patch, and sorry for the delay in reviewing it!

https://codereview.appspot.com/78010043/diff/1/src/unique_ptr.h
File src/unique_ptr.h (right):

https://codereview.appspot.com/78010043/diff/1/src/unique_ptr.h#newcode3
src/unique_ptr.h:3: 
Shouldn't this file include <memory> so that the implementation of unique_ptr or
auto_ptr is available to modules that include this?  If it's present here, then
"#include <memory>" can be removed from each of those modules.

https://codereview.appspot.com/78010043/diff/1/src/vcdecoder.cc
File src/vcdecoder.cc (right):

https://codereview.appspot.com/78010043/diff/1/src/vcdecoder.cc#newcode46
src/vcdecoder.cc:46: #include "unique_ptr.h"
Please add in alphabetical order.

[Lincoln, 2014-04-08 18:58:17]

https://codereview.appspot.com/78010043/diff/1/src/unique_ptr.h
File src/unique_ptr.h (right):

https://codereview.appspot.com/78010043/diff/1/src/unique_ptr.h#newcode1
src/unique_ptr.h:1: #ifndef UNIQUE_PTR_H
This needs to start with a comment containing the Apache license block and
describing the purpose of this file.

[mostynb, 2014-04-08 20:58:14]

https://codereview.appspot.com/78010043/diff/1/src/unique_ptr.h
File src/unique_ptr.h (right):

https://codereview.appspot.com/78010043/diff/1/src/unique_ptr.h#newcode1
src/unique_ptr.h:1: #ifndef UNIQUE_PTR_H
On 2014/04/08 18:58:18, Lincoln wrote:
> This needs to start with a comment containing the Apache license block and
> describing the purpose of this file.

Done.

https://codereview.appspot.com/78010043/diff/1/src/unique_ptr.h#newcode3
src/unique_ptr.h:3: 
On 2014/04/08 18:55:17, Lincoln wrote:
> Shouldn't this file include <memory> so that the implementation of unique_ptr
or
> auto_ptr is available to modules that include this?  If it's present here,
then
> "#include <memory>" can be removed from each of those modules.

Done.

https://codereview.appspot.com/78010043/diff/1/src/vcdecoder.cc
File src/vcdecoder.cc (right):

https://codereview.appspot.com/78010043/diff/1/src/vcdecoder.cc#newcode46
src/vcdecoder.cc:46: #include "unique_ptr.h"
On 2014/04/08 18:55:17, Lincoln wrote:
> Please add in alphabetical order.

Done.

[thakis, 2014-04-28 03:01:29]

Lincoln: Ping.

[Lincoln, 2014-05-14 00:00:30]

I'm very sorry for the long delay in responding!  I wanted to double-check about
what format we want to use for copyright statements.

Cheers,
Lincoln

https://codereview.appspot.com/78010043/diff/40001/src/unique_ptr.h
File src/unique_ptr.h (right):

https://codereview.appspot.com/78010043/diff/40001/src/unique_ptr.h#newcode1
src/unique_ptr.h:1: // Copyright 2014 Opera Software ASA. All Rights Reserved.
Mostyn, would you and Opera be willing to use the following copyright statement
instead?
// Copyright 2014 The open-vcdiff Authors. All Rights Reserved.

I have just changed all our source files to use this form in place of the
previous "Copyright ... Google Inc."  That change will be a part of the next
open-vcdiff release.  This is the first time we are accepting an entire file
(however small) from a source other than Google.  The Chromium project uses a
similar format for "The Chromium Authors":
http://www.chromium.org/developers/coding-style

[mostynb, 2014-05-14 08:49:57]

https://codereview.appspot.com/78010043/diff/40001/src/unique_ptr.h
File src/unique_ptr.h (right):

https://codereview.appspot.com/78010043/diff/40001/src/unique_ptr.h#newcode1
src/unique_ptr.h:1: // Copyright 2014 Opera Software ASA. All Rights Reserved.
On 2014/05/14 00:00:30, Lincoln wrote:
> Mostyn, would you and Opera be willing to use the following copyright
statement
> instead?
> // Copyright 2014 The open-vcdiff Authors. All Rights Reserved.
> 
> I have just changed all our source files to use this form in place of the
> previous "Copyright ... Google Inc."  That change will be a part of the next
> open-vcdiff release.  This is the first time we are accepting an entire file
> (however small) from a source other than Google.  The Chromium project uses a
> similar format for "The Chromium Authors":
> http://www.chromium.org/developers/coding-style

Done.

I'm having trouble remembering how to update CL's with gcl/svn, so I submitted a
new CL with this change here (I also added my name to the THANKS file): 
https://codereview.appspot.com/92310046