Sockets cannont be a vector

[TestZombie]

I dont know what to do

(click to show/hide)

#include <SFML\Network.hpp>
#include <SFML\System.hpp>

void main()
{
   std::vector<sf::TcpSocket> socket;
   socket.resize(1);
}

this throws this error in vs2015

Severity   Code   Description   Project   File   Line   Suppression State
Error   C2280   'sf::TcpSocket::TcpSocket(const sf::TcpSocket &)': attempting to reference a deleted function   Test   c:\program files (x86)\microsoft visual studio 14.0\vc\include\xmemory0   655   

[Ixrec]

That error message is telling you that sf::TcpSocket lacks a copy constructor. Many SFML classes deliberately lack copy constructors because semantically it just doesn't make any sense to copy things like keyboards or mice or network connections (see the sf::NonCopyable documentation for a list of all the other non-copyable SFML classes).

The issue you've run into, which is a general C++ thing and not unique to SFML, is that std::vector can only store copyable types (or in C++11, moveable types). This is correct, because many of the typical std::vector operations require copying (or moving) the contained objects, so it would be wrong to let you compile this.

Depending on what you want to do with sockets, you can either use a raw array as your container, or you can have your container hold smart pointers to sf::TcpSockets instead of the sf::TcpSockets themselves.

[TestZombie]

Thanks!

[namosca]

Hey!

I dont know if you want a vector just because you want to store your objects in an organized way, or just because you want to resize the vector, but an std::list will work fine assuming your most wanted need is to store your objects in an organized way.

It just worked for me:

std::list<sf::TcpSocket> connectionList;
connectionList.emplace_back();// This creates a new socket, directly inside the list

For resizing, this looks dangerous to me to resize without knowing what will happen to the clients connected to your sockets, but this function is also avaiable in list. You can watch all a list can do here on this link:

http://www.cplusplus.com/reference/list/list/

Have a nice time!

[Ixrec]

For completeness, what namosca said is true of any "node-based container" (i.e. a container implemented with "nodes" that hold one item alongside pointers to other nodes). That includes std::list, std::map, std::set, and so on. These containers do not require the items they contain to be copyable because they never copy an item after it's been inserted, no matter what methods you call on them, which is why they work with non-copyable classes like sf::TcpSocket.

The downside of a node-based container is that it can't guarantee contiguous memory like a std::array or std::vector can, and there's the storage and runtime costs of chasing a bunch of pointers. But for many purposes you won't even notice that. It was silly of me not to mention this option in the last post.