Okay, i understand. Not a big issue. I knew it was far stretch anyways.
I think i will name them using their signatures.
an example:
AddEvent(FrameEnded, FrameEndedDelegate(func));
but this also has a variant that gives takes a float.
so i need to find another meaningful name. Like
AddEvent(FrameEnded, FrameEndedDelegateWithTimePassed(func));
This gets too complex for my taste. if i were to name it based on signature then i don't need to remember just formulate its name from the signature of the bound function. That function the one she wrote, she can figure delegate name easily.
Another thing when the delegate name is typed wrong since there are too many overloads of the AddEvent resulting error message is not helpful.
One more is that i can generate funcdef declarations using a simple for loop, fn_void_void, fn_void_int, fn_void_float etc... Saves me typing and figuring out clever names for each delegate. Like a poor man's template :P
Since, i have no real experience with named delegates. Maybe i will be doing wrong. Time will tell :)