- Test:
- basic behaviour of the index mechanism used to keep track of individual Placements as added to the current Session.
- See also
- mobject::Placement
-
mobject::MObject::create
-
mobject::Placement::addPlacement
-
mobject::Placement::resolve
Definition at line 68 of file placement-index-test.cpp.
|
void | checkContentsEnumeration (Idx index) |
|
void | checkInvalidRef (Idx index) |
|
void | checkScopeHandling (Idx index) |
|
PMO::ID | checkSimpleAccess (Idx index) |
|
void | checkSimpleInsertRemove (Idx index) |
|
void | checkTypedAccess (Idx index, PMO::ID elmID) |
|
void | discover (Idx index, Iter iter, uint level) |
|
void | has_size (uint siz, Idx index) |
|
virtual void | run (Arg) |
|
|
static string | indent (uint level) |
|
◆ checkContentsEnumeration()
void checkContentsEnumeration |
( |
Idx |
index | ) |
|
|
inlineprivate |
- Test:
- drill down into the tree-like structure and enumerate the contents of each element, if any
- Note
- at this point, our test index holds 9 Placements, which actually refer to 3 distinct TestClip objects
- two where installed into root scope in
checkSimpleAccess()
- one was installed below one of the above in
checkTypedAccess()
checkScopeHandling()
left back 6 instances, all pointing to the same TestClip. This can be verified in the test output (look at the use-cnt
and the actual address of the pointee
Definition at line 302 of file placement-index-test.cpp.
References Placement< MO, B >::getID(), PlacementIndex::getReferrers(), and PlacementIndex::getRoot().
The documentation for this class was generated from the following file: