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

// Define the delegate types.

public delegate void AboutToBlow(string msg);

public delegate void Exploded (string msg);

// Define member variables of each delegate type.

private AboutToBlow almostDeadList;

private Exploded explodedList;

// Add members to the invocation lists using helper methods.

public void OnAboutToBlow(AboutToBlow clientMethod)

{ almostDeadList = clientMethod; }

public void OnExploded(Exploded clientMethod)

{ explodedList = clientMethod; }

...

}

Notice in this example that we define the delegate types directly within the scope of the Car

type. As you explore the base class libraries, you will find it is quite common to define a delegate

within the scope of the type it naturally works with. On a related note, given that the compiler trans-

forms a delegate into a full class definition, what we have actually done is create two nested classes

(AboutToBlow and Exploded) within the Car class.

Next, note that we declare two private member variables (one for each delegate type) and two

helper functions (OnAboutToBlow() and OnExploded()) that allow the client to add a method to the

delegate’s invocation list. In concept, these methods are similar to the Advise() and Unadvise()

methods we created during the CallbackInterface example. Of course, in this case, the incoming

parameter is a client-allocated delegate object rather than a class implementing a custom interface.