[Mono-list] [review] delegates are cascading.

[Dietmar Maurer]

Just some questions:

- why do we need that method_static field (if we need that info we can
check (m_target == null))

- how can I call those delegate constructors? All examples I have call
the runtime provided constructor instead.

- Dietmar


On Sat, 2002-03-09 at 10:55, Daniel Stodden wrote:
> 
> yay.
> 
> attached two lengthy patches over mono/ and mcs/
> to make MuticastDelegate::Invoke() run smoothly over combined
> delegates. Remove() is missing but I'll finish that over the next days.
> 
> i'm pretty certain it is solid, but since it changes quite 
> bit in emit-x86..
> please, if someone review this and tell me whether its okay to check in.
> 
> regards,
> dns
> 
> abstract: this removes the array-based approach in favour of a reverse,
> self-contained linked list. [emit-x86].Invoke() then recurses over the
> contained links.
> Why reverse? The docs require Remove() to kill any _last_ occurences of
> a combination in the current delegate. any other method needs to
> traverse the whole list anyways, so reversing should keep remove more
> efficient.