Utility pattern
From Wikipedia, the free encyclopedia
| This article does not cite any references or sources. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (November 2008) |
|
|
This article may be confusing or unclear to readers. Please help clarify the article; suggestions may be found on the talk page. (February 2009) |
The Utility pattern is a software pattern that is used for utility classes that do not require instantiation and only have static methods. The stateless class is designated as static so that no instance can be created. Good candidates for utility classes are convenience methods that can be grouped together functionally.
Furthermore, methods in Utility classes are usually deterministic. As the Utility class is stateless, all parameters in each method must pass all necessary information to the method.
Example in C#
public static class LogUtil
{
public static void LogError(String message)
{
MyLogger logger = new MyLogger();
logger.LogError(message);
}
public static void LogWarning(String message)
{
MyLogger logger = new MyLogger();
logger.LogWarning(message);
}
public static void LogInfo(String message)
{
MyLogger logger = new MyLogger();
logger.LogInfo(message);
}
}
// A simple example showing how the utility methods are used
class MyProgram
{
static void Main(String[] args)
{
if (args.Length > 0)
{
// Call our utility helper methods. Note that these are static methods
// that are called directly off the class.
LogUtil.LogError("User ran app with arguments!");
}
else
{
LogUtil.LogInfo("Running program.");
Run();
}
}
}
[edit] See also
| This computer programming-related article is a stub. You can help Wikipedia by expanding it. |