You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to compare nodes and I noticed separate calls to children() do not return the same objects. Are they deep copies? Is there a specific reason for this implementation?
As an example, two consecutive calls return nodes with different addresses.
<AddrmapNode example32 at 0x78aa3d9a1d00> [<RegfileNode example32.tests at 0x78aa3c3d51c0>, <RegfileNode example32.uart0 at 0x78aa3c3d7590>, <RegNode example32.conf at 0x78aa3c3d6ba0>, <RegNode example32.ctrl at 0x78aa3c17d370>, <RegNode example32.stat at 0x78aa3c17c530>, <RegNode example32.ufixed at 0x78aa3c17c380>]
<AddrmapNode example32 at 0x78aa3d9a1d00> [<RegfileNode example32.tests at 0x78aa3c208f80>, <RegfileNode example32.uart0 at 0x78aa3c550ef0>, <RegNode example32.conf at 0x78aa3c3d51c0>, <RegNode example32.ctrl at 0x78aa3c3d6ba0>, <RegNode example32.stat at 0x78aa3c233ef0>, <RegNode example32.ufixed at 0x78aa3c17c920>]
The text was updated successfully, but these errors were encountered:
I had a look at the source code. Let me start by saying I do not have experience with factories so my interpretation of the code is as it is.
Apparently the component hierarchy is static while the node hierarchy is created dynamically during a call to children().
Is there a reliable (preferred) method for comparing two nodes. I would like to know if the two nodes are at the same position in the node tree. I probably could compare paths, and at least for my case, comparing the absolute address seems a good choice. Still is there a preferred way for two nodes are the same node?
I tried to compare nodes and I noticed separate calls to
children()
do not return the same objects. Are they deep copies? Is there a specific reason for this implementation?As an example, two consecutive calls return nodes with different addresses.
The text was updated successfully, but these errors were encountered: