preprocessFile: Difference between revisions
Jump to navigation
Jump to search
m (formatting) |
Lou Montana (talk | contribs) m (Text replacement - " <dd class="notedate">" to " <dt><dt> <dd class="notedate">") |
||
Line 47: | Line 47: | ||
<dl class="command_description"> | <dl class="command_description"> | ||
<!-- Note Section BEGIN --> | <!-- Note Section BEGIN --> | ||
<dt><dt> | |||
<dd class="notedate">Posted on March 4, 2008</dd> | <dd class="notedate">Posted on March 4, 2008</dd> | ||
<dt class="note">[[User:Alef|Alef]]</dt> | <dt class="note">[[User:Alef|Alef]]</dt> | ||
<dd class="note">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". | <dd class="note">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". | ||
<dt><dt> | |||
<dd class="notedate">Posted on July 8, 2011</dd> | <dd class="notedate">Posted on July 8, 2011</dd> | ||
<dt class="note">[[User:kju|kju]]</dt> | <dt class="note">[[User:kju|kju]]</dt> | ||
<dd class="note">Use [[preprocessFileLineNumbers]] instead as it provides more context information on error. | <dd class="note">Use [[preprocessFileLineNumbers]] instead as it provides more context information on error. | ||
<dt><dt> | |||
<dd class="notedate">Posted on December 17, 2013</dd> | <dd class="notedate">Posted on December 17, 2013</dd> | ||
<dt class="note">[[User:Killzone_Kid|Killzone_Kid]]</dt> | <dt class="note">[[User:Killzone_Kid|Killzone_Kid]]</dt> | ||
Line 61: | Line 61: | ||
[[Image:PreprocessFile.jpg]] | [[Image:PreprocessFile.jpg]] | ||
<dt><dt> | |||
<dd class="notedate">Posted on July 25, 2014</dd> | <dd class="notedate">Posted on July 25, 2014</dd> | ||
<dt class="note">[[User:BrotherhoodOfHam|BrotherhoodOfHam]]</dt> | <dt class="note">[[User:BrotherhoodOfHam|BrotherhoodOfHam]]</dt> |
Revision as of 00:11, 6 April 2021
Description
- Description:
- Reads and processes the content of the specified file. Preprocessor is C-like, supports comments using // or /* and */ and PreProcessor Commands. 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:
- System
Syntax
- Syntax:
- preprocessFile fileName
- Parameters:
- fileName: String - Path to the file and name of the file
- Return Value:
- String
Examples
- Example 1:
_content = preprocessFile "myFunction.sqf";
Additional Information
- See also:
- fileExists 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
- 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.
- Posted on December 17, 2013
- Killzone_Kid
- 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
- BrotherhoodOfHam
Essentially what the preprocessFile command does is it refers to the contents of a file as a string:
Example 1:
boop.html:<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.
Example 2:
init.sqf:
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.
Categories:
- Scripting Commands
- Introduced with Operation Flashpoint version 1.85
- Operation Flashpoint: New Scripting Commands
- Operation Flashpoint: Scripting Commands
- Operation Flashpoint: Elite: Scripting Commands
- ArmA: Armed Assault: Scripting Commands
- Arma 2: Scripting Commands
- Arma 2: Operation Arrowhead: Scripting Commands
- Take On Helicopters: Scripting Commands
- Arma 3: Scripting Commands
- Command Group: System