Documentation:Accessing objects and navigating meta-levels in code: Difference between revisions

Accessing objects and navigating meta-levels in code

Revision as of 13:35, 8 February 2023

A single link in runtime is implemented in an IObject as an IObjectReference, i.e. a link that points to another object.

Then one can write:

if ((destinationMember as IObjectReference).ObjectInstance.asObject == null)

I.e. the member as a single link - does it have an object on the other end?

Note! ObjectInstance is always non-null - it's the object holding information about the link-end. It can be a nullObjectImpl, which is an object.

This page was edited 27 days ago on 08/23/2024. What links here

@@ Line 1: / Line 1: @@
+=== Single-link ===
+A single link in runtime is implemented in an IObject as an IObjectReference, i.e. a link that points to another object.
-Single-link
+Then one can write:
-A single link in runtime is implemented in a IObject as a IObjectReference, i.e. a link which points to another object.
-Then one can write;
 if ((destinationMember as IObjectReference).ObjectInstance.asObject == null)
-I.e. the member as a single link - does it have an object in the other end?
+I.e. the member as a single link - does it have an object on the other end?
-Note! ObjectInstance is always non-null, it's the object holding information about the link-end. It can be a nullObjectImpl, which is an object
+Note! ObjectInstance is always non-null - it's the object holding information about the link-end. It can be a nullObjectImpl, which is an object.
 [[Category:Advanced]]
 [[Category:MDriven Framework]]