Where errors are generated

Smalltalk User Guide : Packaging, unloading, and analyzing code : Swapping objects between disks and images : Error processing : Where errors are generated

The following methods, in the current and in the obsolete API, cause the error return value to be set. You should check this value after an operation to ensure that no error occurred. In addition, the ObjectDumper returns false for failed unload operations, and the ObjectLoader returns nil for failed load operations. You can also use the method hasErrorOccurred to check if an error occurred during the last operation.

API methods that return error codes

Methods in ObjectDumper that return error codes:

•maximumLimit:

•outputBufferLimit:

•unload:

•unload:intoStream:

Methods in ObjectLoader that return error codes:

•load

•loadFromStream:

Obsolete API methods that return error codes

Obsolete methods in ObjectDumper that return error codes:

•totalSizeBeforeUnload:

•unload:intoByteObjects:offsetsIntoByteObjects:maximumLimit:errorStream:

•unload:intoFile:

•unload:intoFile:atOffset:

•unload:intoFile:atOffset:maximumLimit:

•unload:intoFile:atOffset:maximumLimit:errorStream:

•unload:intoFileHandle:atOffset:

•unload:intoFileHandle:atOffset:maximumLimit:

•unload:intoFileHandle:atOffset:maximumLimit:errorStream:

Obsolete methods in ObjectLoader that return error codes:

•loadFromByteObjects:offsetsIntoByteObjects:errorStream:

•loadFromFile:

•loadFromFile:atOffset:

•loadFromFileHandle:atOffset:

•loadFromFileHandle:atOffset:errorStream:

Last modified date: 01/29/2015