| Reader's Clinic - Functions and Subroutines |
| Argument passing - Subroutines and Functions - Mike Pope |
| Reader's Clinic - Functions and Subroutines |
| Reader's Letters - Jim Owen |
| Playing with Scan Codes |
| Argument passing - Subroutines and Functions - Mike Pope |
| File Variables |
| Argument passing - Subroutines and Functions - Mike Pope |
| RevTech Replies - Mike Pope (RevTech UK Ltd) |
| Symbol Table Structure |
| Vroom |
| QTIPS - Replacing GAS.BAR routine during PERFORM "SELECT" |
| QTIPS - Extended Select BY |
| QTIPS - PERFORM Arguments and FMT Specifications |
| What's New (and un(der)documented!) In 2.12 |
RevMedia FKB
| Document | V2I1A2 |
| Title | Reader's Clinic - Functions and Subroutines |
| Keywords | FUNCTION SUBROUTINE LOCKER |
| Text | Stefan Gilboy of Logix Consultants makes the interesting point that functions can be declared as both subroutine and function at the beginning of the program This is especially useful in a function such as LOCKER (from utility diskette # 1) Here a dummy variable must be assigned a variable so that the routine can be called to perform an action that does not return anything Thus the following code DECLARE FUNCTION LOCKER OPEN "TEST" TO TF THEN IF LOCKER(TF 1 "L") THEN DELETE TF 1 DUM = LOCKER(TF 1 "U") END END could be replaced with DECLARE FUNCTION LOCKER DECLARE SUBROUTINE LOCKER OPEN "TEST" TO TF THEN IF LOCKER(TF 1 "L") THEN DELETE TF 1 LOCKER(TF 1 "U") END END (Volume 2 Issue 1 Page 3) |
Page last modified: 08/02/03