From 6dfc4d6a3ef281b96890db3ece152a9b8bb4d19b Mon Sep 17 00:00:00 2001 From: Ulf Magnusson Date: Fri, 14 Dec 2012 11:52:17 +0100 Subject: Clarify comment on the value of undefined symbols. --- kconfiglib.py | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'kconfiglib.py') diff --git a/kconfiglib.py b/kconfiglib.py index fa98855..dd81d7f 100644 --- a/kconfiglib.py +++ b/kconfiglib.py @@ -2262,9 +2262,9 @@ class Symbol(Item, _HasVisibility): self.write_to_conf = False - # The following means that what to the user looks like a reference to - # an undefined symbol will actually get treated like a string whose - # value is the symbol name, which can be a bit unexpected. + # As a quirk of Kconfig, undefined symbols get their name as their + # value. This is why things like "FOO = bar" work for seeing if FOO has + # the value "bar". if self.type == UNKNOWN: self.cached_value = self.name return self.name @@ -2586,7 +2586,7 @@ class Symbol(Item, _HasVisibility): def get_parent(self): """Returns the menu or choice statement that contains the symbol, or None if the symbol is at the top level. Note that if statements are - treated as syntactic sugar and do not have an explicit class + treated as syntactic and do not have an explicit class representation.""" return self.parent -- cgit v1.2.3