This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

Intrinsic C# Operator

CIL Representation

--

op_Decrement()

++

op_Increment()

+

op_Addition()

Continued

C H A P T E R   1 2  

■

I N D E X E R S, O P E R ATO R S, A N D   P O I N T E R S

395

8849CH12.qxd  9/26/07  11:31 AM  Page 395

---

Table 12-2.

Continued

Intrinsic C# Operator

CIL Representation

-

op_Subtraction()

*

op_Multiply()

/

op_Division()

==

op_Equality()

>

op_GreaterThan()

<

op_LessThan()

!=

op_Inequality()

>=

op_GreaterThanOrEqual()

<=

op_LessThanOrEqual()

-=

op_SubtractionAssignment()

+=

op_AdditionAssignment()

■

Note

There is a practical reason to know the “special names” of an overloaded operator. Because many lan-

guages cannot use types with overloaded operators, programmers of said languages are able to call these internal

names statically from the defining type (e.g.,

Point.op_Addition(myPoint, yourPoint)

).

Final Thoughts Regarding Operator Overloading

As you have seen, C# provides the capability to build types that can respond uniquely to various

intrinsic, well-known operators. Now, before you go and retrofit all your classes to support such

behavior, you must be sure that the operator(s) you are about to overload make some sort of logical

sense in the world at large.

For example, let’s say you overloaded the multiplication operator for the MiniVan class. What

exactly would it mean to multiply two MiniVan objects? Not much. In fact, it would be very confus-

ing for teammates to see the following use of MiniVan objects.