ContinueIf command: Difference between revisions

From m204wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 2: Line 2:


{|
{|
|width="50%"| '''Action:'''
|width="125px"| '''Action:'''
|width="50%"|
|width="775px"|
<span class="f_Para">Determines whether the processing of a Debugger [[Using Debugger Macros|macro]] may continue. If the state (&quot;True&quot; or &quot;False&quot;) of a specified command argument ([[Working with macro variables|macro variable]], [[Working with Client functions (Debugger)|client function]], or constant) is </span><span class="f_Monospace">True,</span><span class="f_Para"> the macro continues. </span>
<span class="f_Para">Determines whether the processing of a Debugger [[Using Debugger Macros|macro]] may continue. If the state (&quot;True&quot; or &quot;False&quot;) of a specified command argument ([[Working with macro variables|macro variable]], [[Working with Client functions (Debugger)|client function]], or constant) is </span><span class="f_Monospace">True,</span><span class="f_Para"> the macro continues. </span>



Latest revision as of 00:57, 26 January 2023

Action:

Determines whether the processing of a Debugger macro may continue. If the state ("True" or "False") of a specified command argument (macro variable, client function, or constant) is True, the macro continues.

If the state of the continueIf argument or comparison expression is False, the macro containing this command and any macro(s) within which this macro is contained terminate (without error). This behavior contrasts with that of the continueMacroIf command, which exits only the macro containing the continueMacroIf command.

Syntax:

continueIf test

Where test is:

&var | &&function | const  [ = | <> &var | &&function | const 

Where:

  • &var is a macro variable that may or may not already exist.
  • &&function is a Client function.
  • const is a constant.

Notes:

If continueIf is used with a single argument and that argument is 0 or a zero length (null) string, or if it is undefined, its state is considered to be False. For all other values, its state is considered to be True. In an equality comparison any undefined item makes an equality comparison False.

Example:

# Execute Step and optionally update history
noSpan
step
continueIf &historyWanted
getHistory 
...
continueIf &testMe <> &testMe2 

Scope: Allowed only in Debugger macros
Client menu: --
Introduced: Build 37