Actions
Feature #221
openFeature #78: Output system improvements
Support conditionals in output definition files
Start date:
Due date:
% Done:
0%
Estimated time:
16.00 h
Responsible:
Description
Maintenance of output definition files could be made easier if sections of definitions could be enabled by conditionals like preprocessor #if or #ifdef. The variables involved could be set via the THaTextvars interface. ("Textvars" are already expanded before processing the output definitions.) Example
#if ${replaydetail} > 5 block ${arm}.vdc.* #endif
After pre-scanning the output definition file with
replaydetail
set to "10" and arm
set to "L", the parser would see#if 10 > 5 block L.vdc.* #endif
The expression
10 > 5
would be evaluated as true
, and so all L.vdc.*
variables will be included in the output.
Expressions should support the usual comparisons (==
, >
, <
, etc.) and logicals (&&
, ||
), parentheses, etc. Maybe implement it as a temporary TFormula
?
Actions