Talk:execVM filename

Merge suggesttion

I suggest to merge this article with execVM to execVM page. --Djura 18:48, 23 July 2006 (CEST)

---

These articles are scripting commands and are grouped with the rest of the scripting commands.

They are both listed in my comref as separate commands.

execVM filename expects just the one parameter filename

execVM expects two parameters argument and filename

The new commands are still WIP and if these two commands need to be rationalised then it will eventually happen once BI have finalised, as much as possible, the comref.

Until then I would suggest they remain as they are for now.

Planck 13:51, 23 July 2006 (CEST)

Compiling

Question: When does the compiling process happen? While the mission is loaded or everytime the function is executed or only one time when the function is executed the first time? I would like to know this, so that I know what saves more performance either to use execVM or compile every function at the beginning of the mission to process the compiled code with call . --T_D 18:25, 5 August 2006 (CEST)

It is compiled each time execVM is called. Using compile / call (or spawn) gives you more control over this and can be used to precompile code to be executed more often. --Suma 23:07, 16 October 2006 (CEST)

Function or Script?

Something about the this article is either very confusing or wrong. It says that this is compiling and executing a function but this doesn't make much sense to me as it returns a script. And obviously execVM can execute the sleep command without freezing the game. So what is it? All signs point that this does interpret the input as a script and not as a function and it executes it like a script. So I think the entry should not state that is executes function. Donnervogel 15:25, 8 December 2006 (CET)

execVM "x.sqf" is the same as spawn compile preprocessFile "x.sqf". It executes a function, but returns a script handle. That's it. ;) --raedor 15:59, 8 December 2006 (CET)

I think you are correct. Changed to Script.--Suma 16:41, 8 December 2006 (CET)

Merged

this document has been merged to execVM

the original intent of this alternative syntax entry was to state no argument was necessary to the command, unfortunately it suggests the filename is different (or not required)

In any event the example used for this entry used an argument !

ook?