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

// Can call as:

// Square sq2 = (Square)90;

// or as:

// Square sq2 = 90;

public static implicit operator Square(int sideLength)

{

Square newSq;

newSq.Length = sideLength;

return newSq;

}

// Must call as:

// int side = (int)mySquare;

public static explicit operator int (Square s)

{ return s.Length; }

}

The Internal Representation of Custom Conversion Routines

Like overloaded operators, methods that are qualified with the implicit or explicit keywords have

“special” names in terms of CIL: op_Implicit and op_Explicit, respectively (see Figure 12-6).

Figure 12-6.

CIL representation of user-defined conversion routines

■

Note

The Visual Studio 2008 Object Browser shows custom conversion operators using the “explicit operator”

and “implicit operator” icons.

That wraps up our examination of defining custom conversion routines. As with overloaded

operators, remember that this bit of syntax is simply a shorthand notation for “normal” member

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

403

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

---

functions, and in this light it is always optional. When used correctly, however, your custom struc-

tures can be used more naturally, as they can be treated as true class types related by inheritance.