views:

54

answers:

2

Why cant i use the event declared in Base from Sub?

class Program
{
    static void Main(string[] args)
    {
        Sub sub = new Sub();
        sub.log += new Base.logEvent(sub_log);
        sub.go();
    }

    static void sub_log(string message, int level)
    {
        Console.Out.WriteLine(message + " " + level);
    }
}

public abstract class Base
{
    public delegate void logEvent(String message, int level);

    public event logEvent log;
}

public class Sub : Base
{

    public void go()
    {
        log("Test", 1); // <-- this wont compile
    }
}
+1  A: 

Because events can only be called from the declaring class. Just create a method in the base class to call it:

protected virtual RaiseLogEvent(string s, int i)
{
  log(s, i);
}

So you can use it in deriving classes, and even override it.

On another note, I would strongly advise you to follow the design guidelines for events, and create an own EventArgs class, and use the EventHandler<T> delegate.

Femaref
+1  A: 

Events may only be invoked from the class that declares them.

From outside of the definition of a class (even in a derived class) you can only register and unregister from an event. Inside of the class, the compiler only allows you to raise the event. This is a by-design behavior of C# (which actually changes slightly in C#4 - Chris Burrows describes the changes on his blog).

What you want to do here is provide a RaiseLogEvent() method in the base class, which would allow the derived class to invoke this event.

public abstract class Base
{ 
  public delegate void logEvent(String message, int level); 

  public event logEvent log; 

  protected void RaiseLogEvent( string msg, int level )
  {
      // note the idomatic use of the copy/test/invoke pattern...
      logEvent evt = log;
      if( evt != null )
      {
          evt( msg, level );
      }
  }
} 

As an aside, you should consider using the EventHandler<> delegate type, rather than creating your own event types when possible.

LBushkin
So instead of declareing a delegate i make a subclass of EventArgs that holds my message and loglevel? Why is that better?
klundby
@klundy: The standard pattern for event handler in .NET is to supply a sender and a object representing the arguments. This allows subscribers of envents to retain consistency in their signatures, and reduces confusion about what parameters are expected. With C# 4's delegate co/contra-variance it becomes easier to write generic event handlers when the handler does not care about the arguments or sender. What I've done in many cases is to create a `EventArgs<TA,TB,...>` generic class that inherits from `EventArgs` and allows me to pass data to handlers ... but that's just a style choice.
LBushkin