Eric Blake 5e62ed79f9 qapi: Track location that created an implicit type ... A future patch will move some error checking from the parser to the various QAPISchema*.check() methods, which run only after parsing completes. It will thus be possible to create a python instance representing an implicit QAPI type that parses fine but will fail validation during check(). Since all errors have to have an associated 'info' location, we need a location to be associated with those implicit types. The intuitive info to use is the location of the enclosing entity that caused the creation of the implicit type. Note that we do not anticipate builtin types being used in an error message (as they are not part of the user's QAPI input, the user can't cause a semantic error in their behavior), so we exempt those types from requiring info, by setting a flag to track the completion of _def_predefineds(), and tracking that flag in _def_entity(). No change to the generated code. Backports commit 99df5289d8c7ebf373c3570d8fba3f3a73360281 from qemu		2018-02-19 19:04:41 -05:00
..
create_config	more cleanup qemu/configure	2017-01-19 14:11:54 +08: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-event.py	qapi: Share gen_visit_fields()	2018-02-19 18:41:41 -05:00
qapi-types.py	qapi: Don't use info as witness of implicit object type	2018-02-19 18:53:06 -05:00
qapi-visit.py	qapi: Don't use info as witness of implicit object type	2018-02-19 18:53:06 -05:00
qapi.py	qapi: Track location that created an implicit type	2018-02-19 19:04:41 -05:00