Class init: support initializing interfaces #546
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Walk the
qcc_typeid_array[typeid].interfaceBits
to find all the interfaces that are implemented by the current class. This finds the full set of interfaces that a class implements. Only interfaces thatObjectModel.declares_default_methods(type_id)
actually need to be initialized. This initializes the right interfaces but the ordering doesn't match the spec yet.TypeType is now a WordType so it can be created at runtime from an integer.
Added some helper methods to print numbers to allow tracing class initialization. They should be removed when we have a better way to trace runtime actions (JFR?).
Stubbed out
Object.notifyAll()
so the initialization state machine can use it before locks are fully supported.