compileFinal: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - " <!-- (DIS)?CONTINUE Notes -->" to "") |
Lou Montana (talk | contribs) m (Text replacement - "\|game([0-9]) ?= (.+) \|version([0-9]) ?= (.+) " to "|game$1= $2 |version$3= $4 ") |
||
| Line 2: | Line 2: | ||
|game1= arma3 | |game1= arma3 | ||
|version1= 0.56 | |version1= 0.56 | ||
Revision as of 14:54, 3 May 2021
Description
- Description:
- Compile expression and makes it final, preventing it from:
- repeated compile or compileFinal
- removal by nil
- remote rewrite using publicVariable, publicVariableClient and publicVariableServer
- Groups:
- Strings
Syntax
Examples
- Example 1:
myCode = compileFinal "a = a + 1"; call myCode;
// Repeated compile won't have any effect myCode = compileFinal "a = a + 2";
// Duplicate code will be final as well myDuplicateCode = myCode;
Additional Information
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 August 14, 2013
- AgentRev
- When broadcasting a compileFinal'ed variable using publicVariable or its variants, the variable also becomes final on the other client(s) and/or the server. Also, compileFinal does not prevent event handlers from being removed or overwritten.
- Posted on May 27, 2017 - 11:58 (UTC)
- IT07
- in Arma 3 1.70.141838, compileFinal also works for profileNamespace and uiNamespace. But be careful with that.
- Posted on October 23, 2020 - 10:39 (UTC)
- Dscha
- Change with Arma 3 Patch 2.00, compileFinal is now unable to store code type variables in profileNamespace!