C++ design pattern Singleton
1. Function: Ensure that a class has only one instance. 3. Advantages and Disadvantages The Singleton mode appears as a replacement for "global variables". Therefore, it has the characteristics of a global variable: it is globally visible and runs throughout the entire life cycle of the application. It also has properties that global variables do not have: there can only be one object instance of the same type. 4. Implement the Singleton definition in the textbook as follows:
class Singleton
{
public:
static Singleton* Instance() ;
PRotected:
Singleton() {}
private:
static Singleton *_instance ;
Singleton(const Singleton& ) ;
Singleton& Operator=(const Singleton&) ;
} ; Singleton* Singleton::_instance = NULL ; Singleton* Singleton::Instance()
{
(_instance == NULL) ? _instance = new Singleton() : 0 ; //lazy initialization
return _instance ;
} (1) Because it returns a pointer, in order to prevent users from calling the delete function, static Singleton *_instance; can be changed to define static Singleton _instance in Instance(). This is obviously safer, and it also has the characteristics of lazy initialization (that is, it is created only when accessed for the first time).
(2) Suppose you need to derive a subclass from Singleton, and the subclass also needs to have the same properties, which can only create one instance. I think this is difficult to do. The fundamental reason is that the Instance() function is not a virtual function and does not have polymorphic properties. A common method is to move the Instance() function into a subclass. At this time, you can only use static Singleton *_instance, but not static Singleton _instance. Unless you also move _instance to the subclass, no matter what you do, Not elegant. Another way is to use templates. The specific method to use can only be weighed according to the actual situation.
5. Sample code (1) Without subclass namespace DesignPattern_Singleton
{ class Singleton
{
public:
static Singleton* Instance() { static Singleton _instance; return &_instance; }
protected:
Singleton() {}
private:
Singleton(const Singleton&) ;
Singleton& operator=(const Singleton&) ;
} ;
} Client code:
{
using namespace DesignPattern_Singleton ;
Singleton *p = Singleton::Instance() ;
.. ....
} (2) When there are subclasses
Method 1:
namespace DesignPattern_Singleton
{
// class Singleton
class Singleton
{
protected:
Singleton() {}
static Singleton *_instance;
private :
Singleton(const Singleton&) ;
Singleton& operator=(const Singleton&) ;
} ;
Singleton* Singleton::_instance = NULL ; // class ConcreteSingleton
class ConcreteSingleton : public Singleton
{
public:
static Singleton* Instance () ;
protected:
ConcreteSingleton() {}
} ; Singleton* ConcreteSingleton::Instance()
{
(_instance == NULL) ? _instance = new ConcreteSingleton() : 0 ;
return _instance ;
}
} Client code:
{
using namespace DesignPattern_Singleton;
Singleton *p = ConcreteSingleton::Instance();
} Method 2:
namespace DesignPattern_Singleton
{
// class Singleton
class Singleton
{
protected:
Singleton() {}
private:
Singleton(const Singleton&) ;
Singleton& operator=(const Singleton&) ;
} ; // class ConcreteSingleton
class ConcreteSingleton : public Singleton
{
public:
static Singleton* Instance() { static ConcreteSingleton _instance ; return &_instance ; }
protected:
ConcreteSingleton() {}
} ;
} Client code:
{
using namespace DesignPattern_Singleton ;
Singleton *p = ConcreteSingleton::Instance() ;
} Method three:
namespace DesignPattern_Singleton
{
template < class T >
class Singleton
{
public:
static T* Instance() { static T _instance ; return &_instance ; }
protected:
Singleton() {}
private:
Singleton( const Singleton &) ;
Singleton& operator=(const Singleton&) ;
} ; class ConcreteSingleton : public Singleton< ConcreteSingleton > {} ;
} Client code
{
using namespace DesignPattern_Singleton ; ConcreteSingleton *p = ConcreteSingleton::Instance( ) ;
}
The above is the content of Singleton in C++ design pattern. For more related articles, please pay attention to the PHP Chinese website (www.php.cn)!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

In the Java framework, the difference between design patterns and architectural patterns is that design patterns define abstract solutions to common problems in software design, focusing on the interaction between classes and objects, such as factory patterns. Architectural patterns define the relationship between system structures and modules, focusing on the organization and interaction of system components, such as layered architecture.

The decorator pattern is a structural design pattern that allows dynamic addition of object functionality without modifying the original class. It is implemented through the collaboration of abstract components, concrete components, abstract decorators and concrete decorators, and can flexibly expand class functions to meet changing needs. In this example, milk and mocha decorators are added to Espresso for a total price of $2.29, demonstrating the power of the decorator pattern in dynamically modifying the behavior of objects.

1. Factory pattern: Separate object creation and business logic, and create objects of specified types through factory classes. 2. Observer pattern: allows subject objects to notify observer objects of their state changes, achieving loose coupling and observer pattern.

Design patterns solve code maintenance challenges by providing reusable and extensible solutions: Observer Pattern: Allows objects to subscribe to events and receive notifications when they occur. Factory Pattern: Provides a centralized way to create objects without relying on concrete classes. Singleton pattern: ensures that a class has only one instance, which is used to create globally accessible objects.

TDD is used to write high-quality PHP code. The steps include: writing test cases, describing the expected functionality and making them fail. Write code so that only the test cases pass without excessive optimization or detailed design. After the test cases pass, optimize and refactor the code to improve readability, maintainability, and scalability.

The Adapter pattern is a structural design pattern that allows incompatible objects to work together. It converts one interface into another so that the objects can interact smoothly. The object adapter implements the adapter pattern by creating an adapter object containing the adapted object and implementing the target interface. In a practical case, through the adapter mode, the client (such as MediaPlayer) can play advanced format media (such as VLC), although it itself only supports ordinary media formats (such as MP3).

The Guice framework applies a number of design patterns, including: Singleton pattern: ensuring that a class has only one instance through the @Singleton annotation. Factory method pattern: Create a factory method through the @Provides annotation and obtain the object instance during dependency injection. Strategy mode: Encapsulate the algorithm into different strategy classes and specify the specific strategy through the @Named annotation.

The advantages of using design patterns in Java frameworks include: enhanced code readability, maintainability, and scalability. Disadvantages include complexity, performance overhead, and steep learning curve due to overuse. Practical case: Proxy mode is used to lazy load objects. Use design patterns wisely to take advantage of their advantages and minimize their disadvantages.
