<feed xmlns='http://www.w3.org/2005/Atom'>
<title>Kconfiglib.git, branch v10.25.0</title>
<subtitle>Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git</subtitle>
<id>https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v10.25.0</id>
<link rel='self' href='https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v10.25.0'/>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/'/>
<updated>2018-11-24T01:50:12Z</updated>
<entry>
<title>Make 10.25.0 release</title>
<updated>2018-11-24T01:50:12Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-11-24T01:15:05Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=15ccb5536908202da1a672089e155cfdfa6d4722'/>
<id>urn:sha1:15ccb5536908202da1a672089e155cfdfa6d4722</id>
<content type='text'>
Adds a small missed optimization opportunity, in commit 74ce9d3
("Optimize fetching of initial token on line").
</content>
</entry>
<entry>
<title>Simplify eval_string() a bit</title>
<updated>2018-11-24T01:50:05Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-11-24T01:48:22Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=079d7352bec7294467e07071eb4dd4d1030b72a6'/>
<id>urn:sha1:079d7352bec7294467e07071eb4dd4d1030b72a6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Optimize fetching of initial token on line</title>
<updated>2018-11-24T01:28:14Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-11-24T01:03:36Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=74ce9d348dd743af805484ccdd8a722a26aff42d'/>
<id>urn:sha1:74ce9d348dd743af805484ccdd8a722a26aff42d</id>
<content type='text'>
Another possible optimization was missed in commit ab89ef6 ("Get rid of
_next_token() and _peek_token()"): The index of the initial token on a
line is known to be 0, so there's no need to check _tokens_i.

Also reads a bit clearer.
</content>
</entry>
<entry>
<title>Make 10.24.0 release</title>
<updated>2018-11-23T09:53:19Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-11-23T09:47:37Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=5be286d53aab6c8bf99549ae2eaa6bef3e84a86f'/>
<id>urn:sha1:5be286d53aab6c8bf99549ae2eaa6bef3e84a86f</id>
<content type='text'>
Tightens up syntax checking and improves a warning:

 - Commit 13a7bae ("Flag extra trailing tokens in all contexts") adds
   checking for extra trailing tokens in a few overlooked cases.

 - Commit f356ba8 ("Clarify that select/imply is a no-op for choice
   symbols") clarifies the warning when selecting/implying a choice
   symbol.

Parsing performance was improved slightly as well.
</content>
</entry>
<entry>
<title>Clarify that select/imply is a no-op for choice symbols</title>
<updated>2018-11-23T09:39:15Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-11-23T09:39:15Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=f356ba861432980c4a37279af51142b331c84aca'/>
<id>urn:sha1:f356ba861432980c4a37279af51142b331c84aca</id>
<content type='text'>
The warning for selecting/implying a choice symbol could be
misunderstood as saying that select/imply has no effect on choice
symbols in a particular case. Select/imply never has an effect on choice
symbols though.

Rephrase the warning to make it clearer.
</content>
</entry>
<entry>
<title>Flag extra trailing tokens in all contexts</title>
<updated>2018-11-23T09:33:23Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-11-23T01:11:34Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=13a7bae7719c17b43fca5e3c61ff18a225fc6422'/>
<id>urn:sha1:13a7bae7719c17b43fca5e3c61ff18a225fc6422</id>
<content type='text'>
The following cases were let through without a parse error (with the
extra tokens just being ignored):

  - endif/endmenu/enchoice &lt;extra tokens&gt;

  - default FOO &lt;extra tokens&gt;  (though 'default FOO if' flagged an
    error)

Make them generate an error.
</content>
</entry>
<entry>
<title>Get rid of _next_token() and _peek_token()</title>
<updated>2018-11-23T09:29:57Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-11-23T00:33:32Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=ab89ef6aa7b8fef0eb410949c86a25e55586a972'/>
<id>urn:sha1:ab89ef6aa7b8fef0eb410949c86a25e55586a972</id>
<content type='text'>
These are pretty hot. Inline them to save a few % of parsing time.
They're pretty simple anyway.

_tokens_i was initialized to -1 to simplify the _next_token()
implementation. With _next_token() gone, initialize it to 0 instead,
which simplifies some other code.
</content>
</entry>
<entry>
<title>Disable test dependent on dict ordering on Python 3.5 and earlier</title>
<updated>2018-11-21T10:34:32Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-11-21T10:17:28Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=01757e5ac9324948ca64a4cf512352b09956a8fa'/>
<id>urn:sha1:01757e5ac9324948ca64a4cf512352b09956a8fa</id>
<content type='text'>
The KCONFIG_WARN_UNDEF test often fails on Python 3.4 (3.5 not tested),
but the output is still correct. It just differs due to dict ordering
randomness.

Python 3.6 iterates over dicts in insertion order in practice, and
Python 3.7 made it part of the spec, so enable the test for 3.6 and
later.

Python 2.7 seems fine as well.
</content>
</entry>
<entry>
<title>Make 10.23.0 release</title>
<updated>2018-11-21T04:57:40Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-11-21T04:57:40Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=c8b867407862db914f9a4990c8c59f1a5d300106'/>
<id>urn:sha1:c8b867407862db914f9a4990c8c59f1a5d300106</id>
<content type='text'>
 - Commit ee25489 ("menuconfig: Print '----' instead of '---&gt; (empty)'")
   makes the menuconfig display empty menus (e.g. from disabled
   'menuconfig' symbols) in a less spammy way, matching the C tools.

 - Commit 6313925 ("Remove message re. Kconfiglib 10 backwards compat.
   break") removes an old message printed when the top-level Kconfig
   file can't be opened and $srctree is set. Hopefully it's been noticed
   by now.

 - Commit a1a4430 ("Use 'foo.__class__ is Bar' instead of
   'isinstance(foo, Bar)'") improves parsing and evaluation performance a
   bit.
</content>
</entry>
<entry>
<title>menuconfig: Mention that menus can be 'menuconfig' symbols</title>
<updated>2018-11-21T04:45:19Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-11-21T04:45:19Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=a5721347075f3855d17a2dc96ff9b099025c1223'/>
<id>urn:sha1:a5721347075f3855d17a2dc96ff9b099025c1223</id>
<content type='text'>
They're either proper menus, choices, or 'menuconfig' symbols.
</content>
</entry>
</feed>
