Naming Task and Function Parameters

You can use any valid variable name for a Task name or parameter variable. Names like $STRING and #NUMBER will work but, unlike function data naming conventions, $ and # (and other variants) have no special meaning for a Task parameter.

A number of naming practices may give rise to confusion during application maintenance a few months hence.

You can name function parameters with a name that looks like a file variable, but that will probably lead to confusion when maintaining the function in the future. Things to avoid include:

Using names with a file variable format: legal but probably better done by prefixing the parameter with a string (such as "P_").
Using Task parameter names for function parameter names: legal, but can lead to maintenance nightmares unless the names are identical and the Task parameter is always mapped to the function parameter of the same name (and vice versa).
Using similar Task and function parameter names, such as CustNo and CustNum: you will not remember which is which.

Comment on this topic

Topic ID: 540091