try: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "<dl class="command_description"> <dd class="notedate">" to "<dl class="command_description"> <dt></dt> <dd class="notedate">") |
Lou Montana (talk | contribs) m (Text replacement - "<sqf>([^↵][^<]*↵[^<]*)<\/sqf>" to "<sqf> $1 </sqf>") |
||
(51 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
|game1= arma1 | |game1= arma1 | ||
|version1= 1.00 | |||
| | |game2= arma2 | ||
|version2= 1.00 | |||
|game3= arma2oa | |||
|version3= 1.50 | |||
|game4= tkoh | |||
|version4= 1.00 | |||
|game5= arma3 | |||
|version5= 0.50 | |||
|gr1= Program Flow | |gr1= Program Flow | ||
|descr= Defines a try-catch structure. This sets up an [[Exception handling|exception handling]] block. Any thrown exception in a try block is caught in a [[catch]] block. The structured exception block has the following form: | |descr= Defines a try-catch structure. This sets up an [[Exception handling|exception handling]] block. Any thrown exception in a try block is caught in a [[catch]] block. The structured exception block has the following form: | ||
< | <sqf> | ||
{ | try | ||
{ /* block that can throw exception */ } | |||
{ | catch | ||
{ /* block that processes the exception. Exception is described in the _exception variable */ }; | |||
</sqf> | |||
|s1= [[try]] code | |s1= [[try]] code | ||
Line 19: | Line 32: | ||
|r1= [[Exception handling|Exception Type]] | |r1= [[Exception handling|Exception Type]] | ||
| s2= args [[try]] code | |s2= args [[try]] code | ||
|s2since= arma3 1.54 | |||
|p21= args: [[Anything]] - passed arguments, will be put in ''_this'' variable inside the "code" | |p21= args: [[Anything]] - passed arguments, will be put in ''_this'' variable inside the "code" | ||
Line 25: | Line 40: | ||
|p22= code: [[Code]] | |p22= code: [[Code]] | ||
| r2= [[Exception handling|Exception Type]] | |r2= [[Exception handling|Exception Type]] | ||
|x1= < | |x1= <sqf>try { throw "invalid argument" } catch { hint str _exception };</sqf> | ||
|x2= | |x2= <sqf>123 try { if (_this != 123) throw "invalid argument" } catch { hint str _exception };</sqf> | ||
|x3= | |x3= <sqf> | ||
try { | |||
if (a > b) throw "Error: some error"; // OK | |||
} | // the command argument is static | ||
} catch { | |||
hint str _exception; | |||
}; | }; | ||
try { | |||
_someFunc = { | _someFunc = { | ||
// ... | |||
}; | }; | ||
if (a > b) throw (call _someFunc); // NOT OK | |||
// the command argument is dynamic | |||
// _someFunc is called first to get the value regardless of (a > b) outcome | |||
} | } catch { | ||
hint str _exception; | |||
}; | }; | ||
try { | |||
_someFunc = { | _someFunc = { | ||
// ... | |||
}; | }; | ||
if (a > b) then {throw (call _someFunc)}; // OK | |||
// the command argument is dynamic | |||
// _someFunc is only called when (a > b) is true | |||
} | } catch { | ||
hint str _exception; | |||
};</ | }; | ||
</sqf> | |||
|seealso= [[Exception handling]] | |seealso= [[Exception handling]] [[throw]] [[catch]] | ||
}} | }} | ||
{{Note | |||
|user= Killzone_Kid | |||
|timestamp= 20150609205200 | |||
|text= Do not expect this behave like Javascript try catch and ignore all errors. But it does have one useful behaviour. Normally when a runtime error occurs in SQF (unlike when there is compile error) it continues to execute till the end. But if the script is placed in [[try]] {} scope and [[throw]] is used upon error, the script immediately terminates, exits the [[try]] {} scope and enters [[catch]] {} scope. This way it is possible to process possible exceptions in civilised manner. | |||
}} | |||
Do not expect this behave like Javascript try catch and ignore all errors. But it does have one useful behaviour. Normally when a runtime error occurs in SQF (unlike when there is compile error) it continues to execute till the end. But if the script is placed in [[try]] {} scope and [[throw]] is used upon error, the script immediately terminates, exits the [[try]] {} scope and enters [[catch]] {} scope. This way it is possible to process possible exceptions in civilised manner. | |||
Latest revision as of 19:43, 3 September 2024
Description
- Description:
- Defines a try-catch structure. This sets up an exception handling block. Any thrown exception in a try block is caught in a catch block. The structured exception block has the following form:
try { /* block that can throw exception */ } catch { /* block that processes the exception. Exception is described in the _exception variable */ };
- Groups:
- Program Flow
Syntax
- Syntax:
- try code
- Parameters:
- code: Code
- Return Value:
- Exception Type
Alternative Syntax
- Syntax:
- args try code
- Parameters:
- args: Anything - passed arguments, will be put in _this variable inside the "code"
- code: Code
- Return Value:
- Exception Type
Examples
- Example 1:
- Example 2:
- Example 3:
- try { if (a > b) throw "Error: some error"; // OK // the command argument is static } catch { hint str _exception; }; try { _someFunc = { // ... }; if (a > b) throw (call _someFunc); // NOT OK // the command argument is dynamic // _someFunc is called first to get the value regardless of (a > b) outcome } catch { hint str _exception; }; try { _someFunc = { // ... }; if (a > b) then {throw (call _someFunc)}; // OK // the command argument is dynamic // _someFunc is only called when (a > b) is true } catch { hint str _exception; };
Additional Information
- See also:
- Exception handling throw catch
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
- Posted on Jun 09, 2015 - 20:52 (UTC)
- Do not expect this behave like Javascript try catch and ignore all errors. But it does have one useful behaviour. Normally when a runtime error occurs in SQF (unlike when there is compile error) it continues to execute till the end. But if the script is placed in try {} scope and throw is used upon error, the script immediately terminates, exits the try {} scope and enters catch {} scope. This way it is possible to process possible exceptions in civilised manner.
Categories:
- Scripting Commands
- Introduced with Armed Assault version 1.00
- ArmA: Armed Assault: New Scripting Commands
- ArmA: Armed Assault: Scripting Commands
- Arma 2: Scripting Commands
- Arma 2: Operation Arrowhead: Scripting Commands
- Take On Helicopters: Scripting Commands
- Arma 3: Scripting Commands
- Command Group: Program Flow