From a20352a05696b0201484839afddde7629581e9fb Mon Sep 17 00:00:00 2001 From: Ulf Magnusson Date: Sat, 6 Jun 2015 06:02:03 +0200 Subject: Explain why eval() might seem sloppy. --- kconfiglib.py | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/kconfiglib.py b/kconfiglib.py index 9ed81ea..01c7823 100644 --- a/kconfiglib.py +++ b/kconfiglib.py @@ -513,7 +513,10 @@ class Config(object): conditional expressions in the configuration as well as in the C implementation. "m" and m are rewritten as '"m" && MODULES' and 'm && MODULES', respectively, and a result of "m" will get promoted to "y" if - we're running without modules.""" + we're running without modules. + + Syntax checking is somewhat lax, partly to be compatible with lax + parsing in the C implementation.""" return self._eval_expr(self._parse_expr(self._tokenize(s, True), # Feed None, # Current symbol or choice s)) # line -- cgit v1.2.3