That clarifies it
1. "Procedure and function call." No, you can't write FuncName(Param1, Param2) on its own like that. You'll get "Compile error: Expected = ".He's right, that's perfectly clear.
However, if you write FuncName Param1, Param2 you DO get to discard the return value, AND Param1 and Param2 operate as reference parameters. I confirmed that using the following function:
Function FuncName(Param1, Param2)
Param1 = "Fred"
Param2 = "Wilma"
End Function
When I call the above with
Dim Param1, Param2
FuncName Param1, Param2
then Debug.Print Param1 gives me "Fred" and Debug.Print Param2 gives me "Wilma".
However, if I call it with
FuncName (Param1), (Param2)
As I'm expected to do if I want to stipulate transient value parameters, then Debug.Print returns "Empty" for both parameters, indicating the expected behaviour of VB, which Verity seems unaware of.
Even if I do supply the Call keyword, which requires the function parentheses, I can still optionally place a parameter in its own parentheses and thereby force it to act temporarily as a value parameter, e.g.
Call FuncName (Param1, (Param2))
All this illustrates the amazing flexibility of Visual Basic. Maybe coming from the C oriented background of EXE, Verity expects obfuscation where there is none.
