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

// Converting a System.Int32 to a Square.

Square sq2 = (Square)90;

Console.WriteLine("sq2 = {0}", sq2);

// Converting a Square to a System.Int32.

int side = (int)sq2;

Console.WriteLine("Side length of sq2 = {0}", side);

Console.ReadLine();

}

and here is the update to the Square type:

public struct Square

{

...

public static explicit operator Square(int sideLength)

{

Square newSq;

newSq.Length = sideLength;

return newSq;

}

public static explicit operator int (Square s)

{return s.Length;}

}

To be honest, converting from a Square into a System.Int32 may not be the most intuitive (or

useful) operation. However, this does point out a very important fact regarding custom conversion

routines: the compiler does not care what you convert to or from, as long as you have written syn-

tactically correct code. Thus, as with overloading operators, just because you can create an explicit

cast operation for a given type does not mean you should. Typically, this technique will be most

helpful when you’re creating .NET structure types, given that they are unable to participate in

classical inheritance (where casting comes for free).