The SETOPTION are normally set at the beginning of a script if a user chooses so. They are used in this expale to illustrate the most restrictive settings possible when codign a UDF. If a user e.g. ahs NoVarsInString=ON a UDF might not work correctly of the UDF writer is using NoVarsInString=OFF (KiXtart default).

I for example like to use SETOPTION() in the Golf tournaments to the "delight" of a couple of participants [Big Grin]

Yes, UDFs can interact with the user. There are already a couple of UDFs that expand the GET/GETS with custom timeouts, or password-entry capabilities.

A UDF does not need to check for the existance of its dependencies. Dependencies are noted in the UDF header. Also, it does not need to check for the correct KiXtart version. Missing dependencies and incorrect KiXtart versions will already lead to error messages on the command prompt when running the script.

If a UDF is dependent on the presence of other components that might not be present o a computer, then thsi should be noted in either the DEPENDENCIES or REMARKS section, but preferably the first one. Third-party utilities should be referenced including a source where it is available.

I've updated the original post as necessary.
_________________________
There are two types of vessels, submarines and targets.