execVM: Difference between revisions
Jump to navigation
Jump to search
m (=) |
mNo edit summary |
||
| Line 14: | Line 14: | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| [[Script]] <nowiki>=</nowiki> '''''argument'' execVM | | [[Script]] <nowiki>=</nowiki> '''''argument'' execVM "filename"''' |= Syntax | ||
|p1= argument [[Any Value]](s) including | |p1= argument [[Any Value]](s) including Nothing at all.|= Parameter 1 | ||
|p2= filename [[String]] |= Parameter 2 | |p2= filename [[String]] |= Parameter 2 | ||
| Line 23: | Line 23: | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
|x1= <code> | |x1= <code>_var <nowiki>=</nowiki> [[player]] execVM "test.sqf"</code> |= Example 1 | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
Revision as of 01:31, 30 August 2007
Description
- Description:
- Compile and execute SQF Script. The optional argument is passed to the script as local variable _this. The Script is first searched for in the mission folder, then in the campaign scripts folder and finally in the global scripts folder.
- Groups:
- Uncategorised
Syntax
- Syntax:
- Script = argument execVM "filename"
- Parameters:
- argument Any Value(s) including Nothing at all.
- filename String
- Return Value:
- Script
Examples
- Example 1:
_var = player execVM "test.sqf"
Additional Information
- See also:
- SQF syntax Control Structures
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
Notes
- Posted on January 5, 2007 - 12:30
- Giova
- More about the Returned value: the type 'Script' returned by this command, is in fact a kind of 'Thread Handle'. GOOD POINT: sqf functions launched with execVM will run asynchronously from its caller script/function. It is possible to manage multi-threading development, by using: -handle script returned by execVM -force the thread to terminate by using 'terminate' command -synchronise a script by using 'ScriptDone' command BAD POINT: -sqf funcion cannot return value (because execVM is already returning the thread Handle) -the variable _time does not work in sqf called with execVM command