Class messages

The class Class describes the representation and behavior of objects.

Class variable accessing

addClassVarName:, allClassVarNames, classPool, classVarNames, removeClassVarName:, setClassPool:

Note:

These are all Blue Book messages except setClassPool:. The message setClassPool: is a basic accessor that works outside the source code manager.

 

Porting tip:

All supported by both Smalltalk/V and Objectworks\Smalltalk except setClassPool:.

Instance variable accessing

addInstVarName:, allInstVarNames, instVarNames, removeInstVarName:

Note:

These are all Blue Book messages. Note that it is not possible to add instance variables to variable byte classes.

 

Porting tip:

Smalltalk/V does not support addInstVarName: and removeInstVarName:.

Shared pool accessing

addSharedPoolName:, allSharedPoolNames, removeSharedPoolName:, setSharedPoolNames:, sharedPoolNames

Note:

The Blue Book defines the messages addSharedPool:, allSharedPools, removeSharedPool:, and sharedPools, but it takes an inconsistent approach to identifying the shared pool dictionary, referencing it sometimes by name and other times by value. We decided to standardize on reference by name, and appended the suffix Name to the messages to reinforce this point. The aggregate message setSharedPoolNames: is a basic accessor that works outside the source code manager. There is no Blue Book equivalent to setSharedPoolNames:.

 

Porting tip:

Not supported by Smalltalk/V or Objectworks\Smalltalk. Smalltalk/V provides instead the messages addSharedPool:, removeSharedPool:, sharedPool, and sharedPool:. Objectworks\Smalltalk provides the Blue Book messages noted above in the Rationale; however, it changes the Blue Book semantics to always use reference by value.

Tip:

Using setSharedPoolNames: will make the image inconsistent with the source code management system. This method should only be sent by experienced developers who are certain of the outcome.

Class accessing

comment, comment:, definitionString, setClassName:

Note:

The message setClassName: is a basic accessor that works outside the source code manager. No renaming messages aside from setClassName: are included in this release of CLIM. Under normal circumstances renaming should be under the control of the source code manager.

 

Porting tip:

Smalltalk/V and Objectworks\Smalltalk both support comment and comment:. Objectworks\Smalltalk has a message named definition that is the same as definitionString, while Smalltalk/V has no such message. Neither supports setClassName:. Both Smalltalk/V and Objectworks\Smalltalk provide other messages for renaming classes.

Tip:

Using setClassName: will make the image inconsistent with the source code management system. This method should only be sent by experienced developers who are certain of the outcome.

Initializing and removing

initialize, removeFromSystem

Note:

The message removeFromSystem is integrated with the source code manager, and therefore safe to use.

Superclass accessing

connectToSuper, disconnectFromSuper

Note:

These messages both operate outside the scope of the source code manager.

 

Porting tip:

Smalltalk/V and Objectworks\Smalltalk provide other messages that have the same effect.

 

Tip:

Using connectToSuper or disconnectFromSuper will make the image inconsistent with the source code management system. This method should only be sent by experienced developers who are certain of the outcome.