[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-trivial] [Qemu-devel] [PATCH] qom/object.h: remove some child/
Re: [Qemu-trivial] [Qemu-devel] [PATCH] qom/object.h: remove some child/parent doc
Fri, 4 Sep 2015 14:25:17 -0700
On Fri, Sep 4, 2015 at 2:01 PM, <address@hidden> wrote:
> From: Marc-André Lureau <address@hidden>
> It looks like this documentation is obsolete: a child object may lookup
> its parent stored in the Object struct.
Using a function wrapper or direct access to Object structure field?
The latter would indicate they are workarounds. Which legit uses of
parent identification are you referring to?
> Signed-off-by: Marc-André Lureau <address@hidden>
> include/qom/object.h | 3 ---
> 1 file changed, 3 deletions(-)
> diff --git a/include/qom/object.h b/include/qom/object.h
> index 2f95ab3..653699f 100644
> --- a/include/qom/object.h
> +++ b/include/qom/object.h
> @@ -1261,9 +1261,6 @@ Object *object_resolve_path_component(Object *parent,
> const gchar *part);
> * Child properties form the composition tree. All objects need to be a
> * of another object. Objects can only be a child of one object.
> - * There is no way for a child to determine what its parent is. It is not
> - * a bidirectional relationship. This is by design.
> - *
> * The value of a child property as a C string will be the child object's
> * canonical path. It can be retrieved using object_property_get_str().
> * The child object itself can be retrieved using object_property_get_link().