The behavior, described below, of VisualAPL with respect to these named varibles is designed to be consistant and compatible with any other .Net programming language. Therefore this behavior differs from the traditional APL behavior with respect to named variables in the called function header.
In VisualAPL:
- If the calling and called functions are members of the same class, these named variables in the function header of the called function are persistant in the calling class after the function call is completed.
If the calling and called function are members of different classes, then named variables in the function header of the called function do not exist and hence cannot persist in the calling class unless they are also defined as public properties in the called class.
If a variable is neither named in the header of the called function or defined as a public property in the called class, then it does not exist in the calling class.
The attached documents provide additional information and a VisualAPL console project example illustrating this feature of VisualAPL.