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
..
__init__.py	qapi-gen: New common driver for code and doc generators	2018-03-09 08:47:12 -05:00
common.py	qapi: Clean up modular built-in code generation a bit	2019-02-21 09:56:29 -05:00
events.py	qapi: Clean up modular built-in code generation a bit	2019-02-21 09:56:29 -05:00
types.py	qapi: Clean up modular built-in code generation a bit	2019-02-21 09:56:29 -05:00
visit.py	qapi: Clean up modular built-in code generation a bit	2019-02-21 09:56:29 -05:00