Difference between revisions of "diag scope"

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "\| *(arg|eff|mp|serverExec|gr[0-9]) *= *(.*) * *\|([^=0-9]{12})" to "|$1=$2 |descr=$3")
m (Text replacement - "\| *arma3 * * *\| *([0-2]\.[0-9]{2}) * " to "|game1= arma3 |version1= $1 ")
Line 1: Line 1:
 
{{RV|type=command
 
{{RV|type=command
  
| arma3
+
|game1= arma3
 
+
|version1= 2.02
|2.02
 
  
 
|gr1= Diagnostic
 
|gr1= Diagnostic

Revision as of 23:18, 13 June 2021

Hover & click on the images for description

Description

Description:
Returns script scope depth. When script is directly executed by the engine or a new script is added to the scheduler, the scope depth is 0. The examples of such execution are event handlers, spawn, etc. isNil Code will also create a parent scope. Any use of call and such will stack execution creating child scopes and increasing scope depth.
Groups:
DiagnosticPerformance Profiling

Syntax

Syntax:
diag_scope
Return Value:
Number

Examples

Example 1:
[] spawn { systemChat str diag_scope; // 0 call { call { systemChat str diag_scope; // 2 isNil { systemChat str diag_scope; // 0 call { systemChat str diag_scope; // 1 }; }; }; }; };

Additional Information

See also:
exitWithdiag_fpsdiag_fpsMindiag_frameNodiag_logdiag_tickTimediag_deltaTime

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