Markus Armbruster 5d0966ce6b qapi: Clean up modular built-in code generation a bit ... We neglect to call .visit_module() for the special module we use for built-ins. Harmless, but clean it up anyway. The tests/qapi-schema/*.out now show the built-in module as 'module None'. Subclasses of QAPISchemaModularCVisitor need to ._add_module() this special module to enable code generation for built-ins. When this hasn't been done, QAPISchemaModularCVisitor.visit_module() does nothing for the special module. That looks like built-ins could accidentally be generated into the wrong module when a subclass neglects to call ._add_module(). Can't happen, because built-ins are all visited before any other module. But that's non-obvious. Switch off code generation explicitly. Rename QAPISchemaModularCVisitor._begin_module() to ._begin_user_module(). New QAPISchemaModularCVisitor._is_builtin_module(), for clarity. Backports commit dcac64711ea906e844ae60a5927e5580f7252c1e from qemu		2019-02-21 09:56:29 -05:00
..
qapi	qapi: Clean up modular built-in code generation a bit	2019-02-21 09:56:29 -05:00
create_config	Revert "Makefile: Rename TARGET_DIRS to TARGET_LIST"	2018-07-05 17:40:24 -04:00
decodetree.py	decodetree: re.fullmatch was added in 3.4	2019-01-25 13:47:47 -05:00
make_device_config.sh	fix file perms	2015-08-28 21:05:38 -07:00
ordereddict.py	import	2015-08-21 15:04:50 +08:00
qapi-gen.py	qapi: Lift error reporting from QAPISchema.__init__() to callers	2018-03-09 08:55:45 -05:00