Different Application Methods of C ++ static

There are many differences between the application of C ++ and other languages, especially C. Today, we can analyze the differences in the C ++ static application method. At the same time, we can further master the programming methods of the C ++ language.

Sample Code for C ++ static:

 
 

  
  
public class C {   
  
  
public static void M() {   
  
  
Console.WriteLine("call in class C");   
  
  
}   
  
  
}  
  
  
public class D : C {   
  
  
public new static void M() {   
  
  
Console.WriteLine("call in class D");   
  
  
}   
  
  
}  
  
  
public class E<T> where T : C {   
  
  
public static void N() {   
  
  
T.M();   
  
  
}   
  
  
} 
 
 

The code is incorrect. An instance is not allowed to call a static method. If you compile the SDK, the following message is displayed:

 
 

  
  
Error 2 'T' is a 'type parameter', 
which is not valid in the given context 
 
 

Why? From the perspective of language design, for the above Code, only one of the following three cases can be true.

• How to disable the C ++ heap object
• How to disable C ++ stack objects
• Basic concepts of C ++ Functions
• Discussion on the basic content of the variable parameter table in C ++
• Function Comparison of various C ++ memory regions

1. The statement is incorrect.

2. E. N () CILS C.M () no matter what T is.

3. E. N () callc.m () but E. N () calld.m ().

If the design follows 2, the user expects to execute the method M of class D instead of C when T is class D. Static is static because it can be exactly determined at the time of compilation, or this method can be determined at the Static code analysis stage. Therefore, if we design it in the 3 way, we violate this principle. In this way, there is only 1.

Another explanation:

1. virtual static. Why is there no such thing?

2. No such pointer.