395
edits
Conditions: Difference between revisions
Jump to navigation
Jump to search
m
yes you can use strings too. Note that it does not guarantee type conversion: if the left one is a string, there will be no numeric comparison
Philosopher (talk | contribs) m (→Supported elements: rephrase/grammar/code-language mix) |
Philosopher (talk | contribs) m (yes you can use strings too. Note that it does not guarantee type conversion: if the left one is a string, there will be no numeric comparison) |
||
| Line 1: | Line 1: | ||
{{Stub}} | {{Stub}} | ||
'''Conditions''' (or '''SGConditions''') in the SimGear library are a property-based representation of custom conditions based on comparing property values. They can be evaluated from both C++ and Nasal (see simgear/props/condition.hxx and [[$FG_ROOT]]/Nasal/props.nas). | '''Conditions''' (or '''SGConditions''') in the SimGear library are a property-based representation of custom conditions based on comparing property values. They can be evaluated from both C++ and Nasal (see simgear/props/condition.hxx and [[$FG_ROOT]]/Nasal/props.nas). Comparison of string-typed properties involves lexicographic ordering, as specified by the C++ operators <tt><</tt> and <tt>></tt>. | ||
== Usage == | == Usage == | ||