Code vs. Strings: Difference between revisions
Jump to navigation
Jump to search
Besselinksjm (talk | contribs) (Rewritten introduction to reflect exceptions) |
Besselinksjm (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
Since [[Armed Assault]] the convention to use quotation marks for [[String]]s and curly braces for [[Code]] has been formalised. Exceptions, however, do exist: for example [[bindKey (VBS2)]], [[onMapSingleClick]] and [[onDoubleClick]]. When scripting ''<nowiki>'...'</nowiki>'', ''"..."'' or ''""...""'' generally indicates data type String, and {...} indicates data type Code. | Since [[Armed Assault]] the convention to use quotation marks for [[String]]s and curly braces for [[Code]] has been formalised. Exceptions, however, do exist: for example [[bindKey (VBS2)]], [[onMapSingleClick]] and [[onDoubleClick]]. When scripting ''<nowiki>'...'</nowiki>'', ''"..."'' or ''""...""'' generally indicates data type String, and {...} indicates data type Code. | ||
In [[Operation Flashpoint | OFP]] many language constructs (including [[forEach]], [[if]], [[while]]) use the concept of "code strings". | In [[Operation Flashpoint | OFP]] many language constructs (including [[forEach]], [[if]], [[while]]) use the concept of "code strings". Code is passed as a string to them and they interpret it as code if they wish. Since version 1.85, string constants can be written in two ways: Using double quotes (like "Hello") or curled braces (like {a=a+1}). | ||
Code is passed as a string to them and they interpret it as code if they wish. | |||
Since version 1.85, string constants can be written in two ways: | |||
Using double quotes (like "Hello") or curled braces (like {a=a+1}). | |||
A partial list of commands which expect code as parameter is provided at [[Code Commands]]. | |||
[[Category: Scripting_Topics ]] | [[Category: Scripting_Topics ]] |
Revision as of 12:06, 18 January 2010
Since Armed Assault the convention to use quotation marks for Strings and curly braces for Code has been formalised. Exceptions, however, do exist: for example bindKey (VBS2), onMapSingleClick and onDoubleClick. When scripting '...', "..." or ""..."" generally indicates data type String, and {...} indicates data type Code.
In OFP many language constructs (including forEach, if, while) use the concept of "code strings". Code is passed as a string to them and they interpret it as code if they wish. Since version 1.85, string constants can be written in two ways: Using double quotes (like "Hello") or curled braces (like {a=a+1}).
A partial list of commands which expect code as parameter is provided at Code Commands.