Em 14/05/2016 19:30, Egor Pugin escreveu:
> If you set C++11 policy for FB v4, you can use deleted constructors.
> It's method 3 from your link.
> (There were some discussions about C++11 s in the ML.)
It can be done in the NonCopyable class instead of every class, which is
more simple, and a
If you set C++11 policy for FB v4, you can use deleted constructors.
It's method 3 from your link.
(There were some discussions about C++11 s in the ML.)
On 15 May 2016 at 00:59, Adriano dos Santos Fernandes
wrote:
> Hi!
>
> Instead of write private copy constructor and
Hi!
Instead of write private copy constructor and operator=, what about
start using a mixing at least for new code?
It makes easier and much more clear.
Example taken from
http://ariya.ofilabs.com/2015/01/c-class-and-preventing-object-copy.html
class NonCopyable
{
protected: