Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Urgent: Event Handler Recursion

Posted on 2004-09-16
7
Medium Priority
?
684 Views
Last Modified: 2012-06-27
Does anyone know what the exact behavior of the following scenario would be:

1. Class c1 has an event e1.
2. Class c2 has an event handler eh1
3. Instance c2a's eh1 method is attached as a handler for the event c1a.e1.
4. Event c1a.e1 is raised once.
5. Inside the c2a.eh1 handler, 2 new instances of c2 (c2b and c2c) are instantiated, and their eh1 methods are attached as handlers for the same event c1a.e1.

So the question is, will the method eh1 get called 1 time, or 3 times, or is it ambiguous?

Or in other words, at what point during the raising of an event does adding/removing handlers stop applying to the event already being raised?

Thanks!
0
Comment
Question by:Justin_W
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 37

Expert Comment

by:gregoryyoung
ID: 12079892
using System;

namespace ConsoleApplication11
{

      public delegate void FooDelegate();
      public class foo
      {
            public event FooDelegate Fooed;
            private int i=0;
            public string name;

            public void OnFoo()
            {
                  i++;
                  if (Fooed != null)
                        Fooed();
            }

            public void eh1()
            {
                  Console.WriteLine(name + ":eh1 called");
                  foo f1 = new foo();
                  foo f2 = new foo();
                  f1.name = "f1:" + i.ToString();
                  f2.name = "f2:" + i.ToString();
                  this.Fooed += new FooDelegate(f1.eh1);
                  this.Fooed += new FooDelegate(f2.eh1);
            }

            [STAThread]
            static void Main(string[] args)
            {
                  foo f = new foo();
                  f.name = "f";
                  f.Fooed += new FooDelegate(f.eh1);
                  for(int i=0;i<10;i++)
                  {
                        Console.WriteLine("Loop " + (i+1).ToString());
                        f.OnFoo();
                  }
            }
      }
}


add does not appear to apply (atleast in this case) until the next time the event is called. Subtract on the other hand appears to work so long as the event has not yet been called previously.

0
 
LVL 24

Author Comment

by:Justin_W
ID: 12080161
>> add does not appear to apply (atleast in this case) until the next time the event is called.
>> Subtract on the other hand appears to work so long as the event has not yet been called previously.

Thanks Greg!

Do you have any clue as to whether that behavior is guaranteed or merely an implementation detail?  Specifically, do you know whether the behavior may be different when there are multiple Events being handled and if some of the instances are defined in VB.NET assemblies and some in C# assemblies?  I don't want to rely on ambiguous behavior, but it would be really helpful if you happen to know for sure.
0
 
LVL 37

Accepted Solution

by:
gregoryyoung earned 2000 total points
ID: 12080270
as for implementational detail or guarenteed .... this is the best I could find in the C# language specification

Invocation of a delegate instance whose invocation list contains multiple entries proceeds by invoking each of the methods in the invocation list, synchronously, in order. Each method so called is passed the same set of arguments as was given to the delegate instance. If such a delegate invocation includes reference parameters (Section 10.5.1.2), each method invocation will occur with a reference to the same variable; changes to that variable by one method in the invocation list will be visible to methods further down the invocation list. If the delegate invocation includes output parameters or a return value, their final value will come from the invocation of the last delegate in the list.

I could not however find anything where they deal with adding a delegate during the invocation of a delegate.

I would assume your second case to be no ...

0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
LVL 24

Author Comment

by:Justin_W
ID: 12080653
Thanks!  That helps a lot.
0
 
LVL 37

Expert Comment

by:gregoryyoung
ID: 12080825
sorry I couldnt help more mate, perhaps the CLR specification would hold something ? It appears atleast at face value to be an implementational detail.
0
 
LVL 24

Author Comment

by:Justin_W
ID: 12080891
You helped a lot.  I agree about the "implementation detail" part.  Based on your test, and the C# spec., and on the way order of execution is determined for event handlers defined in different classes, it seems like semi-predictable ambiguity is the best I can hope for.  As long as it doesn't cause any runtime errors (which both our tests seem to indicate is the case), I think I can safely raise the event inside a loop (with a special exit condition) so that it keeps getting raised until the system arrives at a rest state.  Thanks again.
0
 
LVL 24

Author Comment

by:Justin_W
ID: 12424101
FYI:
I've posted a semi-related followup question here:
http://www.experts-exchange.com/Programming/Programming_Languages/Dot_Net/Q_21184822.html

If anyone can provide any insight on it, I'd really appreciate it.  Thanks!
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Ready to improve network connectivity? Watch this webinar to learn how SD-WANs and a one-click instant connect tool can boost provisions, deployment, and management of your cloud connection.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is for Object-Oriented Programming (OOP) beginners. An Interface contains declarations of events, indexers, methods and/or properties. Any class which implements the Interface should provide the concrete implementation for each Inter…
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
Do you want to know how to make a graph with Microsoft Access? First, create a query with the data for the chart. Then make a blank form and add a chart control. This video also shows how to change what data is displayed on the graph as well as form…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question