exit | |||||||
Type | control structure | ||||||
Dictionary | LCS | ||||||
Library | LiveCode Script | ||||||
Syntax |
| ||||||
Summary | |||||||
Introduced | 1.0 | ||||||
OS | mac, windows, linux, ios, android | ||||||
Platforms | desktop, server, mobile | ||||||
Parameters |
| ||||||
Example |
| ||||||
Related | Constant: return Command: call Function: commandNames Control Structure: getProp, return, setProp, if, pass, break, on, exit to top, exit repeat, function Glossary: object, function handler, return, message handler, setProp handler, pass, execute, function call, command, control structure, getProp handler, trigger, getProp call, caller, message path, message, statement, handler | ||||||
Description | Use the exit control structure to skip the rest of a handler's statements without returning a result. Form: The exit statement appears on a line by itself, anywhere inside a handler. You can use an exit control structure in a message handler, function handler, getProp handler, or setProp handler. Usually, exit is used within an if control structure, so that the handler stops if a condition is true and continues if the condition is false. If the current handler was called from another handler, the calling handler continues executing. The exit statement only stops the current handler, not the calling handler. (To stop all pending handlers, use the exit to top control structure.) When a handler executes an exit statement, the message, trigger, function call, or getProp call stops and is not passed to the next object in the message path. To halt the current handler and pass the message, trigger, or call on through the message path, use the pass control structure instead. To halt the current handler and return a result, use the return controlstructure instead.
|