Home > Backend Development > C++ > Is Meyers' Lazy Initialized Singleton Implementation Truly a Singleton?

Is Meyers' Lazy Initialized Singleton Implementation Truly a Singleton?

Mary-Kate Olsen
Release: 2024-12-12 17:33:11
Original
200 people have browsed it

Is Meyers' Lazy Initialized Singleton Implementation Truly a Singleton?

Meyers' Singleton Implementation: Unveiling the Singletonness

Question:

How is Meyers' lazy initialized implementation of Singleton in C , as seen below, actually a Singleton pattern?

static Singleton& instance()
{
     static Singleton s;
     return s;
}
Copy after login

Answer:

To understand the Singletonness of Meyers' implementation, it's important to recognize the key characteristic: static storage duration.

In C , local variables declared within a function have static storage duration if they are declared static. This means that only one instance of that variable exists for the entire program, regardless of how many times the function is called.

In Meyers' implementation, the static Singleton s variable has static storage duration. Therefore, only one instance of Singleton can ever be created, enforcing the Singleton pattern.

To provide a clearer understanding, let's break down the code under the hood:

// Global guard variable
static bool __guard = false;

// Static storage for the Singleton
static char __storage[sizeof(Singleton)];

Singleton& Instance() {
  if (!__guard) {
    __guard = true;
    new (__storage) Singleton();
  }
  return *reinterpret_cast<Singleton*>(__storage);
}
Copy after login

This implementation is similar to Meyers' original proposal but includes thread safety mechanisms. The __guard variable ensures that the Singleton is initialized only once, even if accessed concurrently from multiple threads.

Comparison with Other Implementations:

Compared to other Singleton implementations, Meyers' version offers the following pros and cons:

Pros:

  • Simple and effective: Its simplicity makes it easy to understand and implement.
  • Thread-safe: The implementation includes mechanisms to handle concurrent access safely.

Cons:

  • Lazy initialization: The Singleton is created only when it's first requested, which can introduce a performance overhead.
  • Possible destruction issues: As the Singleton is static, it may not be immediately destructed when no longer needed, potentially leading to memory leaks.

Conclusion:

Meyers' lazy initialized Singleton implementation leverages static storage duration to ensure that only one instance of the Singleton exists throughout the program, making it a valid Singleton pattern. While other implementations may offer advantages in terms of performance or memory management, Meyers' version remains a reliable and widely used Singleton design.

The above is the detailed content of Is Meyers' Lazy Initialized Singleton Implementation Truly a Singleton?. For more information, please follow other related articles on the PHP Chinese website!

source:php.cn
Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Latest Articles by Author
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template