The destructor of a
This is of most use:
in stores which do not support commit and revert, for example, the non-persistent in-memory store
where the streams, whose IDs are in the store map, do not contain pointers to other streams.
This behaviour allows a partially complete set of streams to be deleted if a leave occurs part of the way through the building of the set.
Note that this behaviour cannot be exploited by stores which do not support the deletion of streams, for example, the direct file store
Stores such as the permanent file store,
Given the example class,
the
Once the store map has been created, a cleanup item for it is placed onto the cleanupstack. This means that if, for example, the call to either:
or
were to fail, then the streams containing the
Once all three components have been successfully externalised and the
The destructor of a
This is of most use:
+in stores which do not
+support commit and revert, for example, the non-persistent in-memory store
where the streams, whose +IDs are in the store map, do not contain pointers to other streams.
This behaviour allows a partially complete set of streams to be deleted +if a leave occurs part of the way through the building of the set.
+Note that this behaviour cannot be exploited by stores which do not support
+the deletion of streams, for example, the direct file store
Stores such as the permanent file store,
Given the example class,
the
Once the store map has been created, a cleanup item for it is placed onto +the cleanupstack. This means that if, for example, the call to either:
+or
+were to fail, then the streams containing the
Once all three components have been successfully externalised and the