DesignPatterns_Singleton

///
// Singleton Pattern
// - Ensure a class only has one instance, and provide a global point 
//   of access to it.
//
// Author  : ZAsia
// Data    : 15/05/07
// Warning : In practice, declaration and implementation should be 
//           separated(in .h and .cpp).
///

#include 
   
   
    
    
using namespace std;

// Singleton
// - defines an Instance operation that lets clients access its unique
//   instance. Instance is a class operation(that is, a static member
//   member function in C++).
// - may be responsible for creating its own unique instance.
class Singleton
{
public:
	static Singleton *Instance()
	{
		if (_instance == nullptr)
		{
			_instance = new Singleton();
		}
		return _instance;
	}
protected:
	Singleton() { cout << "Singleton..." << endl; }
private:
	static Singleton *_instance;
};

Singleton *Singleton::_instance = nullptr;

// Collaborations
// - Clients access a Singleton instance solely through Singleton's
//   Instance operation.
int main()
{
	Singleton *singletonObj = Singleton::Instance();

	if (singletonObj != nullptr)
	{
		delete singletonObj;
		singletonObj = nullptr;
	}

	return 0;
}


// 1. Controlled access to sole instance. Because the Sinleton class
//    encapsulates its sole instance, it can hvae strict control over
//    how and when clients access it.
//    Notice that the constructor is protected. A client that tries to
//    instantiate Singleton directly will get an error at compile-time.
//    This ensures that only one instance can ever get created.
// 2. Reduced name space. The Singleton pattern is an improvement over
//    global variables. It avoids pollting the name space with global
//    variables that store sole instances.

   
   
  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
If you have ever bought any programming books, you might have noticed that there are two types of them: books that are too short to understand the topic and books that are too long making it inevitable that you get bored. We've tried hard to avoid both of these categories with Design Patterns Explained Simply. This book is fast and simple way to get the idea behind each of the 29 popular design patterns. The book is not tied to any specific programming language and will be good for you as long as you have a basic knowledge of OOP. Most chapters are available on the website, so you can check out the simplicity of the language in the book and the way materials are presented. Why should I read this book? It's simple. It's written in clear and simple language that makes it easy to read and understand. It's short. Yes, there are no useless demos or huge code listings — just clear and easy-to-understand descriptions with many graphical examples. When you finish reading this book, you'll have good reason to go to your boss and ask him for apromotion. Why? Because using design patterns will allow you to get your tasks done twice as fast, to write better code and to create efficient and reliable software architecture. How do I become a programming ninja? The main difference between a ninja and a novice is the knowledge of secret coding tricks, as well as the awareness of most pitfalls and the ability to avoid them. Design patterns were created as a bible for avoiding problems related to software design. Doesn’t that make it a true ninja’s handbook? Table of Contents Creational patterns Abstract Factory Builder Factory Method Object Pool Prototype Singleton Structural patterns Adapter Bridge Composite Decorator Facade Flyweight Private Class Data Proxy Behavioral patterns Chain of Responsibility Command Interpreter Iterator Mediator Memento Null Object Observer State Strategy Template Method Visitor
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值