This article summarizes the precautions for methods in .NET in more detail. Share it for your reference. The specific analysis is as follows:
1. Return in the method will terminate the entire method segment.
And break can only terminate the current loop.
2. The method is to reuse a pair of available codes.
a. For reusable code, select in vs, right-click to refactor and extract the method. It can be automatically encapsulated into a method.
b. When we call an undefined method in programming. Ctrl + . Then Enter. The corresponding method will be automatically generated.
3. For the method return value, if the return value is defined, the method must have a corresponding return.
There is no return value method to use void
4. Constructor does not need to be modified with keywords such as void or int.
5. Parameter modifier params represent variable length parameters
Note: Variable parameters must be the last parameter!
Principle: When the compiler compiles, we make the actual parameters we get into an array. Then pass it in。 Personally think Syntactic sugar is also。 Ha ha
6. Parameter modifier ref
Indicates reference passing. For the value type referenced by the assignment, if you want to use the reference pass method to call the method. The formal parameters of the method need to be modified with ref.
Notice:
1) Values must be assigned before parameter reference.
2) In the method, no value can be assigned to the ref parameter. (Note that you can do it without doing it, which means that assignment is OK, and not assignment is OK.)
For example, the method requires the exchange of the values of two variables.
It needs to be defined like this
{
//Implementation omitted. . . . . . .
}
When calling
int b = 2; //Note that the value must be assigned in advance here.
Swap(ref a, ref b);
7. Parameter modifier out
Let the function output multiple values
Notice:
1) The out parameter must be assigned in the method.
2) The variables of the out parameter do not need to be assigned before being passed. (It's meaningless)
8. Method overload (overload) compile-time polymorphism
Methods with the same method name but different parameters are called method overloading.
Notice:
Conditions for method overloading
1) The method name is the same
2) Different parameters
or
3) The number of parameters is the same but the parameter types are different.
Compilation-time polymorphism is static. Although it is also called XX polymorphism, it has nothing to do with object-oriented characteristics.
Overloading is just a language feature, a syntax rule, has nothing to do with polymorphism, and has nothing to do with object orientation.
I hope this article will be helpful to everyone's .NET programming.