Lazy Initialization

This example has been lifted from the Q & A section here:http://stackoverflow.com/a/1008289/3807729

See this article for a simple design for a lazy evaluated with guaranteed destruction singleton:

http://stackoverflow.com/questions/270947/can-any-one-provide-me-a-sample-of-singleton-in-c/271104#271104

The classic lazy evaluated and correctly destroyed singleton.

class S
{
    public:
        static S& getInstance()
        {
            static S    instance; // Guaranteed to be destroyed.
                                  // Instantiated on first use.
            return instance;
        }
    private:
        S() {};                   // Constructor? (the {} brackets) are needed here.

        // C++ 03
        // ========
        // Dont forget to declare these two. You want to make sure they
        // are unacceptable otherwise you may accidentally get copies of
        // your singleton appearing.
        S(S const&);              // Don't Implement
        void operator=(S const&); // Don't implement

        // C++ 11
        // =======
        // We can use the better technique of deleting the methods
        // we don't want.
    public:
        S(S const&)               = delete;
        void operator=(S const&)  = delete;

        // Note: Scott Meyers mentions in his Effective Modern
        //       C++ book, that deleted functions should generally
        //       be public as it results in better error messages
        //       due to the compilers behavior to check accessibility
        //       before deleted status
};

See this article about when to use a singleton: (not often)

http://stackoverflow.com/questions/86582/singleton-how-should-it-be-used

See this two article about initialization order and how to cope:

http://stackoverflow.com/questions/211237/c-static-variables-initialisation-order/211307#211307

http://stackoverflow.com/questions/335369/finding-c-static-initialization-order-problems/335746#335746

See this article describing lifetimes:

http://stackoverflow.com/questions/246564/what-is-the-lifetime-of-a-static-variable-in-a-c-function

See this article that discusses some threading implications to singletons:

http://stackoverflow.com/questions/449436/singleton-instance-declared-as-static-variable-of-getinstance-method/449823#449823

See this article that explains why double checked locking will not work on C++:

http://stackoverflow.com/questions/367633/what-are-all-the-common-undefined-behaviour-that-c-programmer-should-know-about/367690#367690

Found a mistake? Have a question or improvement idea? Let me know.

Singleton:

* Singleton Design Pattern

* Lazy Initialization

* Static deinitialization-safe singleton.

* Subclasses

* Thread-safe Singeton

Table Of Contents

0 Getting started

1 Literals

2 Basic type keywords

3 Operator precedence

4 Floating point arithmetic

5 Bit operators

6 Bit manipulation

7 Bit fields

8 Arrays

9 Flow control

10 const keyword

11 Loops

12 mutable keyword

13 friend keyword

14 keywords

15 Variable declaration keywords

16 auto keyword

17 Pointers

18 Type keywords (class, enum, struct, union)

19 Classes / structs

20 std::string

21 Enumeration

22 std::atomic

23 std::vector

24 std::array

25 std::pair

26 std::map

27 std::unordered_map

28 std::set and std::multiset

29 std::any

30 std::variant

31 std::optional

32 std::integer_sequence

33 std::function

34 std::forward_list

35 std::iomanip

36 Iterators

37 Basic I/O

38 File I/O

39 Streams

40 Stream manipulators

41 Metaprogramming

42 Returning multiple values from a function

43 References

44 Polymorphism

45 Value and reference semantics

46 Function call by value vs. by reference

47 Copying vs assignment

48 Pointers to class / struct members

49 The this pointer

50 Smart pointers

51 Unions

52 Templates

53 Namespaces

54 Function overloading

55 Operator overloading

56 Lambdas

57 Threading

58 Value categories

59 Preprocessor

60 SFINAE

61 Rule of three, five and zero

62 RAII

63 Exceptions

64 Implementation-defined behavior

65 Special member functions

66 Random numbers

67 Sorting

68 Regular expressions

69 Perfect forwarding

70 Virtual member functions

71 Undefined behavior

72 Overload resolution

73 Move semantics

74 Pimpl idiom

75 Copy elision

76 Fold expressions

77 Unnamed types

78 Singleton

79 ISO C++ Standard

80 User-defined literals

81 Type erasure

82 Memory management

83 Explicit type conversions

84 RTTI

85 Standard library algorithms

86 Expression templates

87 Scopes

88 Atomic types

89 static assert

90 constexpr

91 Date and time with std::chrono

92 Trailing return type

93 Function template overloading

94 Common compile linker errors

95 Design patterns

96 Optimizations

97 Compiling and building

98 Type traits

99 One definition rule

100 Unspecified behavio

101 Argument dependent name lookup

102 Attributes

103 Internationalization

104 Profiling

105 Return type covariance

106 Non-static member functions

107 Recursion

108 Callable objects

109 Constant class member functions

110 C++ vs. C++ 11 vs C++ 17

111 Inline functions

112 Client server examples

113 Header files

114 Const correctness

115 Refactoring techniques

116 Parameter packs

117 Iteration

118 type deduction

119 C++ 11 memory model

120 Build systems

121 Concurrency with OpenMP

122 Type inference

123 Resource management

124 Storage class specifiers

125 Alignment

126 Inline variables

127 Linkage specifications

128 Curiusly recurring template pattern

129 Using declaration

130 Typedef and type aliases

131 Layout of object types

132 C incompatibilities

133 Optimization

134 Semaphore

135 Thread synchronization

136 Debugging

137 Futures and promises

138 More undefined behaviors

139 Mutexes

140 Recursive mutex

141 Unit testing

142 decltype

143 Digit separators

144 C++ Containers

145 Arithmetic meta-programming

146 Contributors