TokenNameValueTypes: Difference between revisions
Jump to navigation
Jump to search
m (Float moved to FloatTokenNames: to keep confusion away from comref) |
mNo edit summary |
||
Line 1: | Line 1: | ||
<big> | <big>Token Name values</big> | ||
The ofp engine, and specifically, a binarised file (signature raP) identifies only a few different 'types' of Token Name | |||
aString = "A string"; | |||
anInteger = 1234567; | |||
aFloat = 0.0123; | |||
anArray[] = {.....}; | |||
Everything that can be stated in a config.cpp, a description.ext, a mission.sqm for TokenName value pairs devolves to one of the above 'types'. | |||
Separately, a '''fifth''' type exists called boolean. | |||
aBoolean = 0; | |||
''In fact'' the engine only stores and 'sees' this value as an integer. But by convention in humanly readable text files (config.cpp vs config.bin), integers that can only have zero or non zero values are declared in statements as | |||
#define false 0 | |||
#define true 1 | |||
LightOn = true; |
Revision as of 06:15, 1 July 2006
Token Name values
The ofp engine, and specifically, a binarised file (signature raP) identifies only a few different 'types' of Token Name
aString = "A string"; anInteger = 1234567; aFloat = 0.0123; anArray[] = {.....};
Everything that can be stated in a config.cpp, a description.ext, a mission.sqm for TokenName value pairs devolves to one of the above 'types'.
Separately, a fifth type exists called boolean.
aBoolean = 0;
In fact the engine only stores and 'sees' this value as an integer. But by convention in humanly readable text files (config.cpp vs config.bin), integers that can only have zero or non zero values are declared in statements as
#define false 0 #define true 1
LightOn = true;