dot-net

A "normal" event on an instance ignores null subscriptions. If I do so on a substituted interface, a null subscription leads to an exception. I have a not so nice legacy code with different listeners to an event an one class that does null-attach internally under some conditions, would be nice if this behaviour would be able to be tested as well. Example code for the problem:

        publ

Justification
It's much more common to see the code below:

Public Sub Foo()
    Dim i, j, k As Long
    'code
End Sub

than it is to see:

Public Sub Foo()
    Dim i As Long, j As Long, k As Long
    'code
End Sub

This is a very common pitfall. Example code in a MultipleDeclarations inspect