Err.Description doesn't make it through to a compiled DLL

[Greedquest]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce

Public Class Foo
    Public Sub t()
        Err.Raise vbObjectError + 5, Description:="No project found with that name"
    End Sub
End Class

Expected behavior
Called from tB we get

as expected.

In VBA we get:

... which is the default message for that error number Error$(vbObjectError + 5)

Desktop (please complete the following information):

• Version: 0.10.5788
• Win 10

[WaynePhillipsEA]

Thanks for reporting. There's a little bit of work to be done on error handling in #56 soon, and so this will be remedied at that point.

[GCuser99]

I'll just add that when I compile the below into an ActiveX DLL (v334), calling the TestErrChild() does raise the error properly, but calling it indirectly through TestErrParent() returns incorrect function for the error description.

'both of these procedures are in the same class module
Public Sub TestErrParent() 
    Call TestErrChild 'error description displays "incorrect function"
End Sub

Public Sub TestErrChild()
    Err.Raise 1, "somewhere", "error raised in child sub" 
End Sub

Also, if TestErrChild() is rejiggered into a function instead of a sub, running TestErrParent() does not raise ANY error, and returns False in the MsgBox:

'both of these procedures are in the same class module
Public Sub TestErrParent()
    MsgBox TestErrChild() 'no error is raised and this displays "False"
End Sub

Public Function TestErrChild() As Boolean
    Err.Raise 1, "somewhere", "error raised in child function" 
    TestErrChild = True
End Function

Thanks!

EDIT: Further to above... I edited my original post to indicate that the parent and child procedures above all lived in a class module. But if I move the child procedures to a standard module, while leaving the parent (caller) procedures in the class module, all works as expected!

[WaynePhillipsEA]

Fixed in BETA 411. Thanks