Migration Guide
This section contains a list of features still available for
compatibility reasons, but which are now considered obsolete. It is
strongly recommended that if you have code that relies on any of these
features, it be updated as suggested below.
- A size calculation method is provided to determine the amount of disk
space the object dump will occupy without unloading it. This operation
was used primarily to compute the size of a ByteArray for this kind
of unloading. Since swapping now uses streams, there is no need to
pre-compute sizes. The operation is still provided, but is
inefficient.
- Objects may be loaded/unloaded to any OS file descriptor at a specified
file offset, or to byte objects (for example, instances of
ByteArray, instances of String). The new release
works on top of streams. This old API is implemented on top of file
streams, but may not be supported in future releases.
- Objects may be unlinked from the dump using either a class based, instance
variable based, or object identity test mechanism. Objects unlinked
using the object identity test mechanism may be re-linked to any specified
object on load. Unlinking and relinking are implemented with the new
mechanism, replacement. If unlinking is all you need, just specify a
dumping replacement being nil for that particular object.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]