Difference between revisions of "Control Structures"
m |
m (→Subs) |
||
| Line 1: | Line 1: | ||
==Subs== | ==Subs== | ||
| − | The term sub is short for subroutine. Subs are an important feature of the EasyUO script | + | The term <i>sub</i> is short for subroutine. Subs are an important feature of the EasyUO script that will make your scripts more logically structured, easier to read, and will make you have to write less code. |
A basic sub definition starts with a sub statement followed by the subs name (sub names are case insensitive), a number of script lines and ends with a return statement. | A basic sub definition starts with a sub statement followed by the subs name (sub names are case insensitive), a number of script lines and ends with a return statement. | ||
Revision as of 12:40, 17 September 2005
Subs
The term sub is short for subroutine. Subs are an important feature of the EasyUO script that will make your scripts more logically structured, easier to read, and will make you have to write less code.
A basic sub definition starts with a sub statement followed by the subs name (sub names are case insensitive), a number of script lines and ends with a return statement.
sub testSub ... return
If parameters were added to the calling gosub command they will be present in the variables %1, %2, and so on. The variable %0 holds the number of parameters passed. As all variables are in the global scope, the %0, %1, %2.. will be overwritten if you call another sub from inside a sub.
| Note: |
|
gosub
The gosub command transfers the execution to a sub with the name given by the parameter.
gosub sub_name
Parameters can be added after the sub name. They will be transfered in the variables %1, %2, and so on. The variable %0 holds the number of parameters passed.
return
The return command transfers the execution back to where the sub was called using gosub.
return
