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

// We have direct access to the delegate!

myCar.explodedList = new Car.Exploded(CallWhenExploded);

myCar.Accelerate(10);

// We can now assign to a whole new object...

// confusing at best.

myCar.explodedList = new Car.Exploded(CallHereToo);

myCar.Accelerate(10);

// The caller can also directly invoke the delegate!

myCar.explodedList.Invoke("hee, hee, hee...");

}

static void CallWhenExploded(string msg)

{ Console.WriteLine(msg); }

static void CallHereToo(string msg)

{ Console.WriteLine(msg); }

}

Exposing public delegate members breaks encapsulation, which not only can lead to code that

is hard to maintain (and debug), but could also open your application to possible security risks!

Obviously, you would not want to give other applications the power to change what a delegate is

pointing to or the power to invoke the members without your permission.