Il 03/03/2014 13:07, Marcel Apfelbaum ha scritto:
> ... which brings us to what is missing here: you are not adding
> current_machine as /machine in the QOM tree. :)
Is missing in purpose, I am not sure what are the consequences of changing the
/machine
from container to an actual object. I am (almost) sure that this container has
child
containers and I am looking for the rules: can an object act like a container?
Yes, it can.
"container" is a separate class than "object" only for documentation
reasons.
Paolo
So, I do intend of course to add it, once I have responded to the above issue.
