loadFile: Difference between revisions
Jump to navigation
Jump to search
m (Text replace - "</dd>" to "") |
m (Text replace - "{{uc:{{PAGENAME}}}}" to "{{uc:{{PAGENAME}}}} {{uc:{{PAGENAME}}}}") |
||
Line 47: | Line 47: | ||
[[Category:Command_Group:_System_Commands|{{uc:{{PAGENAME}}}}]] | [[Category:Command_Group:_System_Commands|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]] |
Revision as of 11:17, 2 November 2011
Description
- Description:
- Return content of given filename.
- Groups:
- Uncategorised
Syntax
Examples
- Example 1:
_contents = loadFile "myFunction.sqf"
Additional Information
- See also:
- preprocessFileLineNumberspreprocessFile
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
- Unknown
- Unknown
- In Armed Assault, the 'loadfile' command must be preceded by the 'compile' command to work.
Ex OFP 1.96: _falarmEvent = loadfile ("syswarn\falarmEvent.sqf")
Ex ArmA 1.0: _falarmEvent = compile loadfile ("syswarn\falarmEvent.sqf") - Tactii 01:10, 11 July 2007 (CEST)
- Tactii
- This is not entirely accurate. loadFile only needs to be preceded with compile when loading code (for example, a function contained in an .sqf file). Using loadFile without compile will return a string, which, in some cases, is exactly what you want.
Bottom Section
Categories:
- Scripting Commands
- Introduced with Operation Flashpoint: Resistance version 1.90
- Operation Flashpoint: Resistance: New Scripting Commands
- Operation Flashpoint: Resistance: Scripting Commands
- Command Group: Uncategorised
- Scripting Commands: Local Effect
- Scripting Commands OFP 1.96
- Scripting Commands ArmA
- Command Group: System Commands
- Scripting Commands ArmA2
- Scripting Commands Take On Helicopters