Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Possible Duplicate:
Why must C# operator overloads be static?
Why Static keyword before the function signature of all the overloaded operators in C# like:
public static void operator = (Object a, Object b)
When we are doing a = b; then a value will be implicitly passed right. So there is no need of static keyword. It must be like:
public void operator = (Object b)
Is it?
The fact that operators are static allows them to be used in situations where there are null values. It also emphasizes the fact that operators are not applied polymorphically. (They potentially could be applied polymorphically if they weren’t static, admittedly… but overriding would generally be a bad idea anyway IMO.)
(Note that you can’t overload the assignment operator in C# anyway.)