| commit | 2e8a843d19fb563b0a4cc7e8a8df8e60df3e97d5 | |
| author | Markus Armbruster <armbru@redhat.com> | |
| Tue, 17 Mar 2020 11:54:39 +0000 (17 12:54 +0100) | ||
| committer | Markus Armbruster <armbru@redhat.com> | |
| Tue, 17 Mar 2020 18:58:34 +0000 (17 19:58 +0100) | ||
| tree | 657f1b201f46ff229e4202a1bb03d49f8c20f849 | treesnapshot (tar.gz zip) |
| parent | 7b3bc9e28f366e591ae6da0d0c58d05d9f487ced | commitdiff |
qapi/introspect: Rename *qlit* to reduce confusion
We generate the value of qmp_schema_qlit from an expression tree. The
function doing that is named to_qlit(), and its inputs are accumulated
in QAPISchemaGenIntrospectVisitor._qlits. We call both its input and
its output "qlit". This is confusing.
Use "tree" for input, and "qlit" only for output: rename to_qlit() to
_tree_to_qlit(), ._qlits to ._trees, ._gen_qlit() to ._gen_tree().
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <20200317115459.31821-15-armbru@redhat.com>
We generate the value of qmp_schema_qlit from an expression tree. The
function doing that is named to_qlit(), and its inputs are accumulated
in QAPISchemaGenIntrospectVisitor._qlits. We call both its input and
its output "qlit". This is confusing.
Use "tree" for input, and "qlit" only for output: rename to_qlit() to
_tree_to_qlit(), ._qlits to ._trees, ._gen_qlit() to ._gen_tree().
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <20200317115459.31821-15-armbru@redhat.com>
| scripts/qapi/introspect.py | diffblobblamehistory |