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

// Make a car as usual.

Car c1 = new Car("SlugBug", 100, 10);

// Register event handlers with Car type.

c1.OnAboutToBlow(new Car.AboutToBlow(CarAboutToBlow));

c1.OnExploded(new Car.Exploded(CarExploded));

// Speed up (this will trigger the events).

Console.WriteLine("***** Speeding up *****");

for (int i = 0; i < 6; i++)

c1.Accelerate(20);

Console.ReadLine();

}

// The Car will call these methods.

public static void CarAboutToBlow(string msg)

{ Console.WriteLine(msg); }

public static void CarExploded(string msg)

{ Console.WriteLine(msg); }

}

The only major point to be made here is the fact that the caller is the entity that assigns the del-

egate member variables via the helper registration methods. Also, because the AboutToBlow and

Exploded delegates are nested within the Car class, we must allocate them using their full name

C H A P T E R   1 1  

■

D E L E G AT E S, E V E N T S, A N D   L A M B D A S

350

8849CH11.qxd  10/1/07  10:43 AM  Page 350

---

(e.g., Car.AboutToBlow). Like any delegate constructor, we pass in the name of the method to add to

the invocation list, which in this case are two static members on the Program class (if you wanted

to wrap these methods in a new class, it would look very similar to the CarEventSink type of the

CallbackInterface example).