Solved C++ overloading operator on an assignment in a constructor using delete TFS 1.2

[CaseyJones]

Can anyone explain to me the purpose of this fragment of code I am really having trouble wrapping my head around it.

        // non-copyable
        Player(const Player&) = delete;
        Player& operator=(const Player&) = delete;

I have a general idea of what is going on here Player is a constructor its argument is a reference to a Player object the overloaded constructor of Player is an assignment with also an argument of a reference to Player which is assigned delete to prevent a default constructor being called.

If I am wrong about its ok as I said I am having a tough time wrapping my head around this. Any help on this matter will be greatly appreciated.

Correction the overloaded constructor of Player has an overloaded assignment operator which is passed a reference of type Player, yes both arguments in each constructor are const's.

One more thing I would like to note there is no definition of the overloaded operator for the constructor defined in player.cpp maybe this is what is throwing me off?

I guess it doesn't need to be defined? As delete is destroying the constructor... this is really frustrating trying to understand.

bump

 

[tarjei]

It means that you remove copy contructor and assign operator i think. I believe it was done to prevent player object from beeing copied.

 

[CaseyJones]

It means that you remove copy contructor and assign operator i think. I believe it was done to prevent player object from beeing copied.

Thanks for the reply but that doesn't really tell me much about the code or the reason why there is no definition for the overloaded operator on this constructor or the use of delete.

Never mind I found a suitable explanation on another site.

 

[godoyxd]

Post the explanation here as it could help others, please.

 

[jo3bingham]

This is a copy constructor:

Player(const Player&);

And this is a copy assignment operator:

Player& operator=(const Player&);

By declaring these functions as deleted (by appending '=deleted;') you are telling the compiler that these functions cannot be used. The purpose is to keep a Player object from being copied and potentially causing memory issues.