a class guaranteed to have only a single instance, with a single global access point to that instance
a classic design pattern that allows you to make sure you have one and only one instance of a given class
a class that assures existence of a maximum of one object of its type at a given time, and provides a global access point to this object
a class that can only be instantiated one time
a class that has exactly one instance
a class that makes sure only one instance of it is ever created
a class that only ever has one instance and provides a global way of accessing it
a class that supports the creation of just one object
a class which guarantees that there is no more than one instance of it (while there might be no instance also)
a class which owns an instance of the same class as itself
a class with just one instance
a design pattern -- frequently occurring code specification -- in which only a single object can ever be created from a class
a design pattern that makes one single instance of a class
a design pattern that specifies a particular object will only have a single instantiation
an class that can be instantiated once, and only once
an object class that can have only one instance in any system
an object, only one instance of which will ever exist
an object that cannot be instantiated
an object that has and can have no more than one instance
an object that has at most one instance of itself in memory at any given time
an object that only has one instance in a system at any time
an option, but I like the above syntax better and we don't need lazy instantiation
a type, but it is not a class
a very simple design pattern which allows you to restrict a class to a
A type used to indicate an individual object. A singleton has only one instance.