preprocessFile: 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 44: | Line 44: | ||
[[Category:Scripting Commands ArmA|PREPROCESSFILE]] | [[Category:Scripting Commands ArmA|PREPROCESSFILE]] | ||
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]] |
Revision as of 11:23, 2 November 2011
Description
- Description:
- Reads and processes the content of the specified file. Preprocessor is C-like, supports comments using // or /* and */ and macros defined with #define.
Due to the hard-drive access this command executes (and the lack of caching) this command should not be used in time-critical script loops. - Groups:
- Uncategorised
Syntax
Examples
- Example 1:
_content=preprocessFile "myFunction.sqf"
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
Notes
- Posted on March 4, 2008
- Alef
- File path is always relative to mission directory. If script dir\a.sqf includes dir\b.sqf, use "dir\b.sqf" and not "b.sqf".
- Posted on July 8, 2011
- kju
- Use preprocessFileLineNumbers instead as it provides more context information on error.
Bottom Section
Categories:
- Scripting Commands
- Introduced with Operation Flashpoint: Resistance version 1.85
- Operation Flashpoint: Resistance: New Scripting Commands
- Operation Flashpoint: Resistance: Scripting Commands
- Command Group: Uncategorised
- Scripting Commands OFP 1.96
- Scripting Commands ArmA
- Scripting Commands ArmA2
- Scripting Commands Take On Helicopters