Flow-control structures: Difference between revisions

Line 1,110:

=={{header|REXX}}==

===exit===

The EXIT statement terminates the running (REXX) program and passes control to

the invoking program (it could be the shell/host/supervisor program).

If the invoking program is a REXX program, it also is terminated.

Line 1,125:

</lang>

===return===

the RETURN statement terminates the running (REXX) program and passes control to

the invoking program (it could be the shell/host/supervisor program).

If the invoking program isn't a REXX program, the RETURN statement acts like an EXIT.

Line 1,139:

</lang>

===SIGNAL===

The SIGNAL statement can be thought of as a GO TO statement, however, on issuance of

a SIGNAL statement, all executing DO loops and SELECTs are terminated.

Essentially, that means that there is no real way to re-enter a DO loop once a SIGNAL

Line 1,203:

</lang>

===leave===

The LEAVE statement transfer control to the next REXX statement following the END

statment of the current DO loop.

The LEAVE statement can also specify which DO loop is to be left if the DO loop has

Line 1,232:

</lang>

===iterate===

The ITERATE statement immediately transfer control to the DO statement, that is, it iterates

(increments or decements) the named REXX variable that is specified on the DO statement.

The ITERATE statement can also specify which DO loop is to be iterated.

Line 1,262:

</lang>

===call===

The CALL statement immediately transfer control to a named subroutine, and the CALL

statement may have any number (or none) parameters.

The named subroutine may or may not return a RESULT (which is similar to a return code).

Line 1,286:

</lang>

===select===

The SELECT statement is used to conditionaly test for cases to selectively execute REXX

statement(s).