Difference between revisions of "preprocessFile"
Jump to navigation Jump to search
|Line 7:||Line 7:|
| Reads and processes the content of the specified file. Preprocessor is C-like, supports comments using // or /* and */ and
| Reads and processes the content of the specified file. Preprocessor is C-like, supports comments using // or /* and */ and .<br>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. |= Description
Revision as of 13:05, 4 November 2017
- Posted on March 4, 2008
- 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
- Use preprocessFileLineNumbers instead as it provides more context information on error.
- Posted on December 17, 2013
- The main difference between preprocessFile and preprocessFileLineNumbers is that the latter adds #line directive to the target file, which allows to log the __LINE__ error happened at and the __FILE__ error happened in.
- Posted on July 25, 2014
Essentially what the preprocessFile command does is it refers to the contents of a file as a string:
<t align = 'center' valign = 'middle' shadow = '0' size = '2'>structured text</t>init.sqf:
_text = parseText preprocessFile "boop.html"; hint _text;
This is especially useful for long strings, and it works on files with any file extension as long as they can be edited with a text editor.
hint preprocessFile "description.ext"; copyToClipboard preprocessFile "mission.sqm";The above is all valid. However, using *.jpg or any other files saved in an image format is not possible.