A few questions regarding bones

Patrick Weemeeuw (Patrick.Weemeeuw@kulnet.KULeuven.ac.be)
Wed, 15 Feb 1995 18:44:15 +0100

I would like to verify a few statements about bones that I found out
by trial and error:
- there is only single inheritance
- each (sub)class must define at least one extra attribute (otherwise
the configuration cannot be parsed)
- superclasses that inherit from Audit must be hidden, because otherwise the
lower level objects have the attributes 'createdBy' etc. from audit
multiply defined
- What's the precise meaning of the KEYS keyword for classes: must each
combination of keys be unique (and can objects be retrieved using a
combination of keys), or is it simply a means to have a name for
objects that is more descriptive than <Class><sequence nr>?

Besides this, is there a standard method to (semi)automatically
extract say IP addresses out of bones to feed it in the tkined
configuration files? I don't like the idea to have to update several
configuration files manually each time an ip number changes.

The approach I'm thinking about is having for each tkined entity two
extra attributes (bones class name and key), and providing a method to
pull all the info regarding that item out of bones and define it as
attributes for the tkined entity.

Thanks in advance

Patrick.