Kconfiglib.git/tests/Kstr, branch v10.38.0Fork of https://github.com/zephyrproject-rtos/Kconfiglib.githttps://git.mcdonnell.dev/Kconfiglib.git/atom?h=v10.38.02018-07-18T01:23:43ZAdd def_int, def_hex, and def_string keywords2018-07-18T01:23:43ZUlf Magnussonulfalizer@gmail.com2018-07-18T01:05:37Zurn:sha1:e08b6957ca935fc97eddd1afda933715016b9b11
Analogous to def_bool and def_tristate, setting the type and adding a
default at the same time.
This is a Kconfiglib extension. These keywords can be useful in projects
that make use of symbols defined in multiple locations, and remove some
Kconfig inconsistency.
Record which MenuNode has each property2018-05-16T17:58:22ZUlf Magnussonulfalizer@gmail.com2018-05-14T12:48:22Zurn:sha1:63a44186137e2706afec0aef278cd5d123fc98dc
This allows accurate documentation to be generated for symbols and
choices defined in multiple locations. There are now MenuNode.defaults,
MenuNode.selects, etc., lists that mirror the corresponding
Symbol/Choice lists.
Symbol/Choice.__str__() now correctly show property locations as well,
by simply concatenating the strings returned by MenuNode.__str__() for
each node.
_parse_properties() was modified to add all properties directly to the
menu node instead of adding them to the contained symbol or choice. The
properties are then copied up to symbols and choices in
_finalize_tree(). Dependency propagation is handled at the same time.
As a side effect, this cleans up the code a bit and de-bloats
_parse_properties().
Update the menuconfig implementation to use the new functionality. It
now lists the menu nodes for symbols and choices with the correct
properties for each node (previously, all defaults, selects, implies,
and ranges appeared on the first definition).
Parenthesize && expressions within || expressions2018-03-28T18:29:20ZUlf Magnussonulfalizer@gmail.com2018-03-28T18:29:20Zurn:sha1:7245bad9ebb58fc8ce5a322081fc6c39d2dc59c6
This is redundant from an evaluation perspective, as && has higher
precedence than ||, but is easier to read.
A && B || C && D is now rendered as "(A && B) || (C && D)".
Refactor expr_str() cases2018-03-26T13:15:07ZUlf Magnussonulfalizer@gmail.com2018-03-26T13:12:09Zurn:sha1:6ef362c490bc2608c971eeabd5930ea0d8893dbe
- Detect Symbol directly instead of as (not tuple) + (not choice)
- Test explicitly for a tuple (non-Symbol) in NOT
- Add some tests to get better coverage for NOT and parentheses
Include direct deps. in Symbol/Choice.__str__()2018-02-16T09:10:34ZUlf Magnussonulfalizer@gmail.com2018-02-16T09:05:16Zurn:sha1:2a88c0cc5707eb0761d87cfd2ca171ce687258fc
Direct dependencies are significant for 'imply' even if the symbol has
no properties, so they need to be included to get semantically
equivalent output.
Making the direct dependencies clear is helpful in general too, even if
you can usually infer them from the properties they get propagated to.
Get rid of separate is_optional test2017-11-02T18:46:11ZUlf Magnussonulfalizer@gmail.com2017-11-02T18:46:11Zurn:sha1:e388f85764dcc6ab87b256e4088b4be918e02c1f
The choice semantics tests already verify the behavior of optional
choices. Just print an optional choice instead to get some coverage for
querying it.
Do minor cleanup elsewhere.
Add uncommitted test files2017-10-28T03:46:25ZUlf Magnussonulfalizer@gmail.com2017-10-28T03:46:25Zurn:sha1:7bbaf7e7cf131d83931bfda2d2e8e5d6ef1b235fKconfiglib 2 backup2017-10-24T17:24:08ZUlf Magnussonulfalizer@gmail.com2017-10-09T21:05:00Zurn:sha1:dd0e227216e247d2040cdd40bf7397702880cdc4
WIP