Back to General and Gameplay Programming

Making Singleton pattern clearer.

ANSI2000 · 2002-01-04T03:17:52

Ok, I understand the Singleton pattern when it should be used and how to implement it, but am not to sure ho wto implement it within the rest of my application and classes. Let''s say I have a class called Logs. This class will write to file for loging purposes. class Logs { public: static Logs getInstance(); // If Logs is NULL, create new instance and return it, if not return already created instance. void init(char *pLogsLocation, char *pFileName); // Set the location and file name where the logs should be set. void writeLog(char *pMessage); // Write a message to the log ~Logs() // Destructor private: Logs(); // Constructor static Logs myLogs; char logsLocation[128], fileName[128]; } Do init(), logsLocation[128], fileName[128] have to be static? Also how would I instanciate, intilaize the logs class to be used within my application and other classes. Woudl I have to declare and Logs object per class and instatiate each one by using getInstance? And will I have to call init() over and over again, am asuming init has to be called only once... void main() { Logs myLogs = Logs::getInstance() myLogs.init("c:\\logs", "logfile.txt"); MyClass myClass; myClass.init(); } class MyClass { public: init() { myLogs = Logs::getInstance(); myLogs.init("bla", "bla"); // Should this be done? } private: Logs myLogs; }