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

// Circle DOES NOT override Draw().

class Circle : Shape

{

public Circle() {}

public Circle(string name) : base(name){}

}

// Hexagon DOES override Draw().

class Hexagon : Shape

{

public Hexagon() {}

public Hexagon(string name) : base(name){}

public override void Draw()

{

Console.WriteLine("Drawing {0} the Hexagon", shapeName);

}

}

The usefulness of abstract methods becomes crystal clear when you once again remember that

subclasses are never required to override virtual methods (as in the case of Circle). Therefore, if you

create an instance of the Hexagon and Circle types, you’d find that the Hexagon understands how to

“draw” itself correctly (or at least print out an appropriate message to the console). The Circle,

however, is more than a bit confused (see Figure 6-10 for output):

static void Main(string[] args)

{

Console.WriteLine("***** Fun with Polymorphism *****\n");

Hexagon hex = new Hexagon("Beth");

hex.Draw();

Circle cir = new Circle("Cindy");