summaryrefslogtreecommitdiff
path: root/src/core/wee-eval.h
AgeCommit message (Collapse)Author
2019-01-01core: update copyright datesSébastien Helleu
2018-11-29core: use https for links to GNU GPL licenseSébastien Helleu
2018-04-17core: fix infinite loop in evaluation of strings (closes #1183)Sébastien Helleu
2018-04-17core: add an eval context structureSébastien Helleu
A pointer to this structure is given as parameter in each eval function called: - eval_replace_vars - eval_expression_condition - eval_replace_regex
2018-01-05core: update copyright datesSébastien Helleu
2017-08-10core: remove value for first #define in headers, add "PLUGIN" in plugin headersSébastien Helleu
2017-04-29core: add wildcard matching operators to eval (closes #608)Simmo Saan
2017-01-01core: update copyright datesSébastien Helleu
2016-01-01core: update copyright datesSébastien Helleu
2015-01-01core: update copyright datesSébastien Helleu
2014-10-22api: add regex replace feature in function string_eval_expressionSébastien Helleu
2014-10-12core: move default prefix/suffix for evaluation in wee-eval.hSébastien Helleu
2014-04-04core: fix evaluation of expression with regex when a comparison char is in ↵Sébastien Helleu
the regex
2014-03-19core: fix use of reserved C identifiers in headers (closes #31)Sebastien Helleu
2014-03-06core: fix recursive calls to function eval_expressionSebastien Helleu
2014-01-01core: update copyright datesSebastien Helleu
2013-08-04core: optimize creation of hashtable "pointers" in eval_expression if ↵Sebastien Helleu
argument is NULL The hashtable is created on first call to eval_expression with pointers == NULL. On next calls, the hashtable is cleared, then used again. The hashtable is freed on exit.
2013-08-04api: add argument "options" in function string_eval_expression, add option ↵Sebastien Helleu
"-c" for command /eval (to evaluate a condition)
2013-07-24core: fix priority of logical operators in evaluation of expressionSebastien Helleu
The AND ("&&") takes precedence over the OR ("||"). Before the fix: >> 1 || 1 && 0 == [0] After the fix: >> 1 || 1 && 0 == [1] Since the "&&" has higher priority, expression is evaluated as: "1 || (1 && 0)".
2013-01-10core: fix some copyright datesSebastien Helleu
2013-01-01core: update copyright datesSebastien Helleu
2012-11-02core: add command /eval, use expression in conditions for bars, add function ↵Sebastien Helleu
"string_eval_expression" in plugin API