2018-02-20 02:34:54 +00:00
|
|
|
/*
|
|
|
|
|
* QObject
|
|
|
|
|
*
|
|
|
|
|
* Copyright (C) 2015 Red Hat, Inc.
|
|
|
|
|
*
|
|
|
|
|
* This work is licensed under the terms of the GNU LGPL, version 2.1
|
|
|
|
|
* or later. See the COPYING.LIB file in the top-level directory.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#include "qemu-common.h"
|
|
|
|
|
#include "qapi/qmp/qbool.h"
|
|
|
|
|
#include "qapi/qmp/qdict.h"
|
|
|
|
|
#include "qapi/qmp/qfloat.h"
|
|
|
|
|
#include "qapi/qmp/qint.h"
|
|
|
|
|
#include "qapi/qmp/qlist.h"
|
|
|
|
|
#include "qapi/qmp/qstring.h"
|
|
|
|
|
|
qapi: Convert QType into QAPI built-in enum type
What's more meta than using qapi to define qapi? :)
Convert QType into a full-fledged[*] builtin qapi enum type, so
that a subsequent patch can then use it as the discriminator
type of qapi alternate types. Fortunately, the judicious use of
'prefix' in the qapi definition avoids churn to the spelling of
the enum constants.
To avoid circular definitions, we have to flip the order of
inclusion between "qobject.h" vs. "qapi-types.h". Back in commit
28770e0, we had the latter include the former, so that we could
use 'QObject *' for our implementation of 'any'. But that usage
also works with only a forward declaration, whereas the
definition of QObject requires QType to be a complete type.
[*] The type has to be builtin, rather than declared in
qapi/common.json, because we want to use it for alternates even
when common.json is not included. But since it is the first
builtin enum type, we have to add special cases to qapi-types
and qapi-visit to only emit definitions once, even when two
qapi files are being compiled into the same binary (the way we
already handled builtin list types like 'intList'). We may
need to revisit how multiple qapi files share common types,
but that's a project for another day.
Backports commit 7264f5c50cc1be0f1406e3ebb45aedcca02f603a from qemu
2018-02-20 02:45:54 +00:00
|
|
|
static void (*qdestroy[QTYPE__MAX])(QObject *) = {
|
2018-02-20 02:34:54 +00:00
|
|
|
NULL, /* No such object exists */
|
|
|
|
|
NULL, /* qnull_ is indestructible */
|
|
|
|
|
qint_destroy_obj,
|
|
|
|
|
qstring_destroy_obj,
|
|
|
|
|
qdict_destroy_obj,
|
|
|
|
|
qlist_destroy_obj,
|
|
|
|
|
qfloat_destroy_obj,
|
|
|
|
|
qbool_destroy_obj,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
void qobject_destroy(QObject *obj)
|
|
|
|
|
{
|
|
|
|
|
assert(!obj->refcnt);
|
qapi: Convert QType into QAPI built-in enum type
What's more meta than using qapi to define qapi? :)
Convert QType into a full-fledged[*] builtin qapi enum type, so
that a subsequent patch can then use it as the discriminator
type of qapi alternate types. Fortunately, the judicious use of
'prefix' in the qapi definition avoids churn to the spelling of
the enum constants.
To avoid circular definitions, we have to flip the order of
inclusion between "qobject.h" vs. "qapi-types.h". Back in commit
28770e0, we had the latter include the former, so that we could
use 'QObject *' for our implementation of 'any'. But that usage
also works with only a forward declaration, whereas the
definition of QObject requires QType to be a complete type.
[*] The type has to be builtin, rather than declared in
qapi/common.json, because we want to use it for alternates even
when common.json is not included. But since it is the first
builtin enum type, we have to add special cases to qapi-types
and qapi-visit to only emit definitions once, even when two
qapi files are being compiled into the same binary (the way we
already handled builtin list types like 'intList'). We may
need to revisit how multiple qapi files share common types,
but that's a project for another day.
Backports commit 7264f5c50cc1be0f1406e3ebb45aedcca02f603a from qemu
2018-02-20 02:45:54 +00:00
|
|
|
assert(QTYPE_QNULL < obj->type && obj->type < QTYPE__MAX);
|
2018-02-20 02:34:54 +00:00
|
|
|
qdestroy[obj->type](obj);
|
|
|
|
|
}
|