C#

mabrahao wrote:

static constructor can be useful

public class Test
{
   // Constructor
   public Test(){}

   public static Color GetColor()
   {
      return Color.White;
   }
}

// somewher in your app

Color c = Test.GetColor(); // Test t = New Test() was never called.

Saksida Bojan wrote:

mabrahao wrote:
static constructor can be useful

No such thing. static is usefull if you call function without intilizing class. If you intilize, constructor is called

Saksida Bojan wrote:

No such thing.

From    To    Increment
1.01    2.00  0.01
2.02    4.00  0.02
4.04   10.00  0.05
....
500    1000   10

public class OddsPrice
{
   // --- Class members --- //

   // Legal prices in ascending order.
   static int[] priceArray;

   // Type initializer: Initializes price array.
   static OddsPrice()
   {
       priceArray = new int[256];
       int price = 100; // cents
       int i = 0;
       while ((price += 1) <= 200) priceArray[i++] = price;
       while ((price += 2) <= 400) priceArray[i++] = price;
       ...
   }

   // --- Instance members --- //

   // Byte representation of value: Index in ordered set of legal values.
   byte value;

   // Value in cents
   public int Value
   {
      get { return priceArray[value]; }
   }
}

Kim0618 wrote:

After the program is running for a long time by user interactions, its memory usage will increase to the limit

Kim0618 wrote:

I have tried memory garbage collection but the program is too complex that garbage collection cannot clean up the memory usage effectively.