[GR-34476] Add member interop objects and declared member APIs. #9783
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.
Introducing member objects and declared members.
A member is not a String name, but an interop object. Members can still be read/written/invoked/... using a string (interop string) name. Object members provide better member identification in case of overloaded members.
getMembers()
is deprecated and replaced withgetMemberObjects()
. No internal objects any more. We'll have a "tools view" instead in the future.Declared members are members declared by a meta-object. They allow an interop reflection.
Static members are provided via
getStaticReceiver()
, static members are independent on a particular instance.Interop Changes
New interop messages:
Replacement of
getMembers()
and read/write/invoke/remove messages take a , or an :Static receiver (provides static members):
New Declared Members (on a meta-object only):
New Member namespace:
New signature element namespace:
Exceptions
Deprecate
Value Changes
Replacement for String identifieds
New methods that take a member
Declared Members
New member methods
Signature
DebugValue Changes
New Methods:
Deprecated:
Adoption