why we use static class, reasons with example

Question

why we use static class, reasons with example.

Tuhin Paul · Answer

Static classes are used in programming to create utility classes that contain static members (fields, methods, properties, or events) that can be accessed without the need to create an instance of the class. Here are some reasons why we use static classes: A static class is an excellent way to group related functions together. For example, you might have a static class that contains math-related functions such as calculating the area of a circle or finding the square root of a number. By grouping these functions together in a static class, you can make your code more organized and easier to maintain. Since static members are shared across all instances of a class, they can be accessed more quickly than instance members. This can lead to a performance boost, especially when working with large amounts of data. A singleton is a design pattern that ensures that a class has only one instance and provides a global point of access to that instance. Static classes can be used to implement the Singleton pattern, where a static instance of the class is created once and then accessed through a static method. Example: Let's say you are building a game and you want to keep track of the score. You could create a static class called ScoreManager that contains a static field for the score and static methods to update and retrieve the score. Here's an example implementation: public static class ScoreManager { private static int score = 0; public static void AddPoints(int points) { score += points; } public static void ResetScore() { score = 0; } public static int GetScore() { return score; } } You can then access the ScoreManager from anywhere in your code, without the need to create an instance of the class: ScoreManager.AddPoints(10); int currentScore = ScoreManager.GetScore(); ScoreManager.ResetScore();

Vulpes · Answer

You would use a static class if: 1. You just want a class to contain a bunch of static or constant members. 2. You don't want it to be possible to instantiate the class. 3. You don't want it to be possible to inherit from the class. In effect, static classes are the nearest thing we have to procedural programming in an otherwise object oriented language. For example: using System; static class Program { const string Hello = "Hello"; // it's OK for a static class to include a constant static void Main() // all members of a static class must be static, const or nested types { Console.WriteLine("The Main method is in a static class"); Program P = new Program(); // compiler error - can't instantiate a static class } class Yourclass // it's OK for a static class to include a nested type { } } class MyClass : Program // compiler error - can't derive from static class { }