Dynamic behavior

The abstract behavior table of each object is not fixed, the behavior reference registration can be dynamically moved among objects, classes, and parent classes. When a behavior is not found in an object, it will jump to its class to find; if it is not found in a class, it will jump to its parent class to find. The behavior references placed in the object spend the most memory space, placed in the parent class spend the most travel time, and the ability to evaluate and adjust the placement according to the situation during runtime is a way of dynamic balance. In this way, the dynamic abstract behavior table can also directly implement dynamic addition and deletion of behaviors. The old static object system lacked a dynamic addition and deletion mechanism, so an extra Component Object Model was defined on it. The new dynamic object system has a more direct and better way.