Singleton模式要求一个类有且仅有一个实例,并且提供了一个全局的访问点。这就提出了一个问题:如何绕过常规的构造器,提供一种机制来保证一个类只有一个实例?客户程序在调用某一个类时,它是不会考虑这个类是否只能有一个实例等问题的,所以,这应该是类设计者的责任,而不是类使用者的责任。
C#实现:

/// <summary>
/// 简单实现
/// </summary>
public sealed class Singleton1
{
private static Singleton1 instance = null;
Singleton1() { }
public static Singleton1 Instance
{
get
{
if (instance == null)
{
instance = new Singleton1();
}
return instance;
}
}
}
/// <summary>
/// 线程安全,双重锁定
/// </summary>
public sealed class Singleton2
{
private static Singleton2 instance = null;
static readonly object padlock = new object();
Singleton2() { }
public static Singleton2 Instance
{
/// 简单实现
/// </summary>
public sealed class Singleton1
{
private static Singleton1 instance = null;
Singleton1() { }
public static Singleton1 Instance
{
get
{
if (instance == null)
{
instance = new Singleton1();
}
return instance;
}
}
}
/// <summary>
/// 线程安全,双重锁定
/// </summary>
public sealed class Singleton2
{
private static Singleton2 instance = null;
static readonly object padlock = new object();
Singleton2() { }
public static Singleton2 Instance
{
get
{
if (instance == null)
{
lock (padlock)
{
if (instance == null)
{
instance = new Singleton();
}
return instance;
}
}
}
}
}
{
if (instance == null)
{
lock (padlock)
{
if (instance == null)
{
instance = new Singleton();
}
return instance;
}
}
}
}
}