class that only instantiate ones

[xenoviaquarta]

so i have a class called Server, i dont need to instantiate it more than one.
i only need one Server server thats it
should i consider making a class of it? or should i just write a functions and global variables in header file? im confused

[Cody0023]

Google "Singleton"

[xenoviaquarta]

Google "Singleton"

i dont think you understand my question. i know about singleton pattern

my question is, does it really make sense to write a class if i will only instantiate it ones?

[DeathLeap]

Did you mean instantiate it 'once' ?

[48T7M4Gy]

Classes have the advantage of formalising data abstraction, encapsulation and hiding and project management and control so why not use it for a single server object when any cost or overhead is minimal and the alternatives are slightly less (at least) functional and that is without cosiderering interact with other possible classes and aspects such as inheritance.

http://programmers.stackexchange.com/questions/213343/is-it-a-bad-idea-to-create-a-class-which-will-only-have-one-instance

[JLBorges]

> does it really make sense to write a class if i will only instantiate it ones?

Usually no; in many cases singleton is an anti-pattern. Use a namespace instead.

Header (.h):

namespace server
{
     // declarations of server functions
};

Implementation (.cpp):

#include "server.h"

namespace // internal linkage, not visible outside 
{
     // server data
     // server helper functions
     // other server implementation details
}

namespace server
{
     // definitions of server functions
}

A singleton object should be used if and only if an object is actually required.
For instance, alternate implementations accessed via a pure polymorphic interface needs to be supported;
overloaded operators would be desirable etc.