Class: BinaryIOManager

• Inheritance
• Description
• Related information
• Class protocol
  • Signal constants
  • class initialization
• Instance protocol
  • accessing
• Examples

Inheritance:

   Object
   |
   +--BinaryIOManager
      |
      +--BinaryInputManager
      |
      +--BinaryOutputManager

Package:

stx:libboss

Category:

System-BinaryStorage

Version:

rev: 1.38 date: 2009/11/23 17:11:41

user: cg

file: BinaryIOManager.st directory: libboss

module: stx stc-classLibrary: libboss

Author:

Eliot Miranda (eliot@cs.qmc.ac.uk)

Claus Gittinger

Description:

I am a shared superclass for the binary IO classes BinaryInputManager & 
BinaryOutputManager.
I define some class variables that define the types of descriptions in binary
files, see BinaryIOManager class>>initialize

Related information:

    BinaryObjectStorage
    ObsoleteObject
    PersistencyManager
    Object
    [binary object storage]

Class protocol:

 binaryLoadErrorSignal

return the signal raised, when a binary load fails due to some reason.
This is the parent signal for all other binary load errors;
therefore, it can be used to handle all errors in a single handler.

 changedIndexedInstSignal

return the signal raised, when an instance of a class is about to be filed in,
which has different indexed instvars (i.e. byte-insts vs. pointers etc)

 changedInstLayoutSignal

return the signal raised, when an instance of a class is about to be filed in,
which has a different inst layout (i.e. the size matches, but the order of
instvars has changed)

 changedInstSizeSignal

return the signal raised, when an instance of a class is about to be filed in,
which has a different inst-size (i.e. the number of named instvars has changed)

 invalidBinaryFormatErrorSignal

return the signal raised, when a binary load fails due to format errors,
for example, if you try to fileIn a binary object from another smalltalk,
or from a stream which does not contain binary objects at all.

 invalidClassSignal

return the signal raised, when an object is about to be filed in,
for which no valid class exists in the system,
or when such a class is referenced in an instvar of a loaded object.

This is the parent signal for all class related binary load errors;
therefore, it can be used to handle these in a single handler.

 nonexistingClassSignal

return the signal raised, when an object is about to be filed in,
for which no class exists (or no-longer exists).

 requestConversionSignal

return the signal raised, when an instance of an obsolete class has
to be converted. The handler gets an instance of a dummy class (which has the
old classes structure) and the new class as parameters, and is supposed to
return an instance of the new class with the dummy-instances contents.

 initialize

Initialize the types & type table for binary i/o

Instance protocol:

 codeForByteArray

return the code-byte used to encode a byteArray with 1-byte length

 codeForByteInteger

return the code-byte used to encode a small byte valued integer

 codeForCharacter

return the code-byte used to encode a single-byte character

 codeForClass

return the code-byte used to encode a class

 codeForFalse

return the code-byte used to encode false

 codeForMinusOne

return the code-byte used to encode the small integer -1 (minus one)

 codeForNegativeByteInteger

return the code-byte used to encode a negative byte valued integer

 codeForNegativeInteger

return the code-byte used to encode a negative integer

 codeForNil

return the code-byte used to encode nil

 codeForOne

return the code-byte used to encode the small integer 1 (one)

 codeForString

return the code-byte used to encode a string with 1-byte length

 codeForSymbol

return the code-byte used to encode a symbol with 1-byte length

 codeForTrue

return the code-byte used to encode true

 codeForTwoByteCharacter

return the code-byte used to encode a two-byte character

 codeForZero

return the code-byte used to encode the small integer 0 (zero)

Examples: