preprocessFile: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
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 Arma 3|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]]

Revision as of 13:01, 25 March 2013

Hover & click on the images for description

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

Syntax:
String = preprocessFile fileName
Parameters:
fileName: String
Return Value:
String

Examples

Example 1:
_content=preprocessFile "myFunction.sqf"

Additional Information

See also:
preprocessFileLineNumbersloadFileFunctionSQF syntaxcallspawnexecVMPreProcessor Commands

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