In Smalltalk-80
In Smalltalk, everything is an object. Additionally, Smalltalk is a class based system, which means that every object has a class that defines the structure of that object (i.e. the instance variables the object has) and the messages an object understands. Together this implies that a class in Smalltalk is an object and that therefore a class needs to be an instance of a class (called metaclass).
As an example, a car object c
is an instance of the class Car
. In turn, the class Car
is again an object and as such an instance of the metaclass of Car
called Car class
. Note the blank in the name of the metaclass. The name of the metaclass is the Smalltalk expression that, when evaluated, results in the metaclass object. Thus evaluating Car class
results in the metaclass object for Car
whose name is Car class
(one can confirm this by evaluating Car class name
which returns the name of the metaclass of Car
.)
Class methods actually belong to the metaclass, just as instance methods actually belong to the class. When a message is sent to the object 2
, the search for the method starts in Integer
. If it is not found it proceeds up the superclass chain, stopping at Object whether it is found or not.
When a message is sent to Integer
the search for the method starts in Integer class
and proceeds up the superclass chain to Object class
. Note that, so far, the metaclass inheritance chain exactly follows that of the class inheritance chain. But the metaclass chain extends further because Object class
is the subclass of Class
. All metaclasses are subclasses of Class.
In early Smalltalks, there was only one metaclass called Class
. This implied that the methods all classes have were the same, in particular the method to create new objects, i.e., new
. To allow classes to have their own methods and their own instance variables (called class instance variables and should not be confused with class variables), Smalltalk-80 introduced for each class C
their own metaclass C class
. This means that each metaclass is effectively a singleton class.
Since there is no requirement that metaclasses behave differently from each other, all metaclasses are instances of only one class called Metaclass
. The metaclass of Metaclass
is called Metaclass class
which again is an instance of class Metaclass
.
In Smalltalk-80, every class (except Object
) has a superclass. The abstract superclass of all metaclasses is Class
, which describes the general nature of classes.
The superclass hierarchy for metaclasses parallels that for classes, except for class Object
. ALL metaclasses are subclasses of Class
, therefore:
Object class superclass == Class.
Like conjoined twins, classes and metaclasses are born together. Metaclass
has an instance variable thisClass
, which points to its conjoined class. Note that the usual Smalltalk class browser does not show metaclasses as separate classes. Instead the class browser allows to edit the class together with its metaclass at the same time.
The names of classes in the metaclass hierarchy are easily confused with the concepts of the same name. For instance:
Object
is the base class that provides common methods for all objects; "an object" is an integer, or a widget, or aCar
, etc.
Class
is the base metaclass that provides common methods for all classes; "a class" is something likeInteger
, orWidget
, orCar
, etc.
Metaclass
has the same relation to "a Metaclass".
Four classes provide the facilities to describe new classes. Their inheritance hierarchy (from Object), and the main facilities they provide are:
- Object - default behavior common to all objects, like class access
- Behavior - minimum state for compiling methods and creating/running objects
- ClassDescription (abstract class) - class/variable naming, comments
- Class - similar, more comprehensive, facilities to superclasses
- Metaclass - initializing class variables, instance creation messages
- ClassDescription (abstract class) - class/variable naming, comments
- Behavior - minimum state for compiling methods and creating/running objects
Read more about this topic: Metaclass