HP Integrity NonStop J-Series - Manual (Page 177)

return 0;
}
Because this example uses simple persistence, which does not maintain pointer relationships, the
restored team has different pointer relationships than the original team. Figure 1 shows what the
created and restored teams look like in memory if you run the program.
Figure 1. Simple Persistence
As you can see in Figure 1, when objects that refer to each other are saved and then are restored
with simple persistence, the morphology among the objects can change. This is because simple
persistence assumes that every pointer reference to an object in memory refers to a unique object.
Thus, when such objects are saved, two references to the same memory location will cause two
copies of the contents of that memory location to be saved, and later restored.