VBA allows "overloads" of aliased functions. RD is confused...

[comintern]

Apparently, the hack that VBA uses to support forwarding the type hinted functions (i.e. Left and Left$) lets you "override" them as variables by specifying a different type hint:

Sub IFoundYourDirtyBuggySecret()
    Format# = 42
    Debug.Print Format#
End Sub

For any function that isn't aliased to a pair of _B_var_Foo and _B_str_Foo, this would result in a compiler error:

Sub NotSoMuch()
    IIf# = 42    'Compile error:  Type-declaration character does not match declared data type
    Debug.Print IIf#
End Sub

This creates problems for RD, which is currently resolving them to the function:

[ThunderFrame]

Format$ is somewhat special.

I can define a constant: Const Format$ = "abc", but I can't use it without getting a compile error "Argument not optional". I can use it if I use it with square brackets: Debug.Print [Format$]

If I instead define a function...

Function Format$()
  Format$ = "abc"
End Function

...it then shadows VBA.Format$, and the function can be used without square brackets.

CurDir is also special.

I can define a constant Const CurDir$ = "abc", but if I use it, I get the result of the VBA built-in function. If I use square brackets, I get the value of the constant.

If I instead define a function...

Function CurDir$()
  CurDir = "abc"
End Function

...it then shadows VBA.Format$, and the function can be used without square brackets.

Input$ and InputB$ are different...
I can't define constants or functions named Input$ or InputB$.

And for similar but different reasons, Date$ and String$ are different.
Date and String are reserved words, and can't be used (with or without a typehint) as identifiers.

[retailcoder]

Confirmed repro as of 2.5.92: