Talk:Flow-control structures: Difference between revisions
→REXX Return: extracted from (oo)rexref and simplified
(→REXX Return: clarification or expansion of statement definition for RETURN. -- ~~~~) |
Walterpachl (talk | contribs) (→REXX Return: extracted from (oo)rexref and simplified) |
||
Line 39:
::::: The RETURN text mentions "which could be a subroutine or function)" ... and passed control to the invoking program (the program that called or invoked the subroutine/function). If you think the phrase could use clarification, then feel free to add more verbage. It's sometimes not clear to readers what is being referred to which REXX code is being executed (or being called/invoked) when the REXX code calls/invokes an internal REXX program versus an external REXX program. This can be an area of misunderstanding, and certainly, an area of confusion. I'm not sure how to succinctly put that into words that is concise and easy to understand without getting to wording that is too obtuse. I don't want to re-write a REXX tutorial on the RETURN statement. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 19:07, 17 December 2013 (UTC)
--------------------------
How about this:
<pre>RETURN returns control, and possibly a result, from a Rexx program or routine to the point of
its invocation.
If no internal routine (subroutine or function) is active,
RETURN and EXIT are identical in their effect on the program that is run. (See EXIT.)
If called as a function, an expression must be present, its value is returned to the point of
invocation.
If called as a routine, control is passed back to the caller.
If an expression is present, it is evaluated and the Rexx special variable RESULT is set
to the value of expression. Otherwise the special variable RESULT is dropped.</pre>
--[[User:Walterpachl|Walterpachl]] ([[User talk:Walterpachl|talk]]) 21:01, 17 December 2013 (UTC)
== REXX Exit ==
| |||