Std::unique_ptr usage?

Std::unique_ptr is non-assignable and non-copyable. You need to use std::move().

Std::unique_ptr is non-assignable and non-copyable. You need to use std::move(); so p1 = std::move(p2); Have a look here for more info.

Here is an article I wrote which answers your questions. I originally wrote this article to present an emulation of unique_ptr. However you can ignore the first few paragraphs dealing with the emulation and just start reading at "Basic Examples".

home.roadrunner.com/~hinnant/unique_ptr0... Edit: I had trouble distilling the above linked article down to something small enough to make a practical answer in this format. However here is my best shot: The reason: Safety in generic code. One can not really make copies of either auto_ptr or unique_ptr.

Consider: template void foo(T t) { T copy_of_t = t; // line 4 assert(copy_of_t == t); } It is not unusual at all for generic code to look like foo above. The assert is probably not actually there, but the assumption that the assert would hold often is there ... implicitly. Indeed, a popular implementation of std::sort had exactly this logic in 1996, which is exactly what prompted the second auto_ptr redesign (which helped, but didn't completely fix the problem).

Thanks for the article :) It is considered good practice on SO to sum up the content of the link though, so that the answer does not lose its value if the link goes dead. – Matthieu M. Apr 11 at 15:45.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.