diff options
| author | Eric Blake <eblake@redhat.com> | 2015-10-12 22:22:27 -0600 |
|---|---|---|
| committer | Markus Armbruster <armbru@redhat.com> | 2015-10-15 08:39:08 +0200 |
| commit | 49823c4b4304a3e4aa5d67e089946b12d6a52d64 (patch) | |
| tree | b28a72ee09d0f1a635de4e8be236230f818634ba /tests/qapi-schema/qapi-schema-test.out | |
| parent | 849ab13c1657b51b89693282ddd42ca1f6255354 (diff) | |
qapi: Don't use info as witness of implicit object type
A future patch will enable error reporting from the various
QAPISchema*.check() methods. But to report an error related
to an implicit type, we'll need to associate a location with
the type (the same location as the top-level entity that is
causing the creation of the implicit type), and once we do
that, keying off of whether foo.info exists is no longer a
viable way to determine if foo is an implicit type.
Instead, add an is_implicit() method to QAPISchemaEntity, and use it.
It can be overridden later for ObjectType and EnumType, when implicit
instances of those classes gain info.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <1444710158-8723-8-git-send-email-eblake@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Diffstat (limited to 'tests/qapi-schema/qapi-schema-test.out')
0 files changed, 0 insertions, 0 deletions