Public Event Handlers

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Leslie Sanford - 07 Jan 2006 00:49 GMT

Is it considered bad style to make event handlers public? Something like
this:

public void Send(object sender, SomeEventArgs e)
{
// Do stuff...
}

The idea is that by making the handlers public, a third party can
configure the flow of events through an application by attaching and
detaching objects with events to objects with event handlers. The
objects involved don't have to know about each other.

I can't find anything in the guidelines that say one way or the other.

Reply to this Message

Lloyd Dupont - 07 Jan 2006 03:24 GMT

I think that, wether or not the method is an event handler, the question is:
is it appropriate to make this method public?

difficult question...

my politic is the following:
I made as much as possible method public and virtual.
If calling a method require additional work to maintain the object in an
appropriate state (i.e. other method call are required not to break the
object) I make it protected or internal.
If the method just make no sense to the outside world (such as a utility
method) I make it private.

> Is it considered bad style to make event handlers public? Something like
> this:
[quoted text clipped - 10 lines]
>
> I can't find anything in the guidelines that say one way or the other.

Reply to this Message

Public Event Handlers

Free Magazines