Modeling C# delegates

[DionBarrier]

I'm trying to figure out a reasonable/best way to model C# delegates. EA's reverse engineering drops the ball and simply won't touch it.  Technically I know they are a syntactic sugar representation of a class but  it just seems clunky to model them that way and out-of-band with EA's Code Engineering.  Does anyone have any suggestions on how I might model the below example?  Thanks.

namespace MyNamespace
{
    public delegate void MyDelegate(MyClassA param1, MyClassB param2);
}

[Makulik]

Hi,

Somehow delegates and event are a form of "degenerate" interface specification with exactly one method per interface and strong coupling of source/sink interface. But I'm afraid this kind of view won't help much for the code generation cycle. You might try to find a way to express delegates as specially stereotyped interfaces and have adapted code generation templates for this stereotype though.

HTH
Günther