In object-oriented programming, a metaclass is a class whose instances are classes. Just as an ordinary class defines the behavior of certain objects, a metaclass defines the behavior of certain classes and their instances. Not all object-oriented programming languages support metaclasses. Among those that do, the extent to which metaclasses can override any given aspect of class behavior varies. Each language has its own metaobject protocol, a set of rules that govern how objects, classes, and metaclasses interact.
In Python, the builtin class
type is a metaclass. Consider this simple Python class:
At run time,
Car itself is an instance of
type. The source code of the
Car class, shown above, does not include such details as the size in bytes of
Car objects, their binary layout in memory, how they are allocated, that the
__init__ method is automatically called each time a
Car is created, and so on. These details come into play not only when a new
Car object is created, but also each time any attribute of a
Car is accessed. In languages without metaclasses, these details are defined by the language specification and can't be overridden. In Python, the metaclass,
type, controls these details of
Car's behavior. They can be overridden by using a different metaclass instead of
The above example contains some redundant code to do with the four attributes
color. It is possible to eliminate some of this redundancy using a metaclass. In Python, a metaclass is most easily defined as a subclass of
This metaclass only overrides object creation. All other aspects of class and object behavior are still handled by
Now the class
Car can be rewritten to use this metaclass. This is done in Python 2 by assigning to
__metaclass__ within the class definition (in Python 3 you provide a named argument, metaclass=M to the class definition instead):
Car objects can then be instantiated like this:
The Smalltalk-80 metaclass hierarchy as a UML diagram
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 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
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
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
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 a
Class is the base metaclass that provides common methods for all classes; "a class" is something like
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
Ruby purifies the Smalltalk-80 concept of metaclasses by introducing eigenclasses and redefining the class-of map. In particular, there is no
Metaclass class in Ruby and the class of every non-terminal object is constantly the
The change can be schematized as follows (note that we are using terminology in which classes and metaclasses form disjoint sets) :
The Smalltalk-80 class-of map is treated as a hidden "actualclass" map  and is provided in its decomposition into the eigenclass-of map and the (real) class-of map (which are available via the
singleton_class and the
class methods, respectively). The maps can be briefly described as follows:
The eigenclass of a terminal object
x provides "singleton methods" for
x and does not have any correspondent in Smalltalk-80. In most cases, there is no need to define singleton methods, so that the eigenclass of
x exists only conceptually and is not allocated.
The eigenclass of a class
x is the metaclass for
x in the Smalltalk-80 sense (but also might exist only conceptually).
The class of a terminal object
x is equal to "the-class-of"
x in the Smalltalk-80 sense.
The class of anything else (i.e. a class or an eigenclass) is the
In this description, the eigenclass map is presented in its restriction to primary objects (classes and terminal objects). But the concept of eigenclasses is uniform: there are also eigenclasses of eigenclasses, their eigenclasses, and so on, constituting infinite chains, thus establishing infinite regress. The "higher order" eigenclasses usually exist purely conceptually – they do not contain any methods or store any (other) data in most Ruby programs.
The decomposition purifies the actualclass map in the sense that the eigenclass map is one-to-one and the (real) class map is many-to-one, without any inherent one-to-one part.
The metaclass terminology in Ruby can be summarized as follows:
There is only one real meta-class in Ruby, both in the "class of a class" sense as well as of an instantiator of classes – the
Class class. (This also means that
Class subclassing is disallowed.)
Eigenclasses of classes might be considered metaclasses in a weak sense: they are meta-objects of classes.
The following information is accurate for the Cocoa framework.
Metaclasses in Objective-C are almost the same as those in Smalltalk-80 (not surprising since Objective-C borrows a lot from Smalltalk). Like Smalltalk, in Objective-C, the instance variables and methods are defined by an object's class. A class is an object, hence it is an instance of a metaclass.
Like Smalltalk, in Objective-C, class methods are simply methods called on the class object, hence a class's class methods must be defined as instance methods in its metaclass. Because different classes can have different sets of class methods, each class must have its own separate metaclass. Classes and metaclasses are always created as a pair (the runtime has functions
objc_registerClassPair() to create and register class-metaclass pairs, respectively).
There are no names for the metaclasses; however, a pointer to any class object can be referred to with the generic type
Class (similar to the type
id being used for a pointer to any object).
Because class methods are inherited through inheritance, like Smalltalk, metaclasses must follow an inheritance scheme paralleling that of classes (e.g. if class A's parent class is class B, then A's metaclass's parent class is B's metaclass), except that of the root class.
Unlike Smalltalk, the metaclass of the root class inherits from the root class itself. (The root class is usually
NSObject in Cocoa.) This ensures that all class objects are ultimately instances of the root class, so that you can use the instance methods of the root class (usually useful utility methods for objects) on class objects themselves.
Since metaclass objects do not behave differently (you cannot add class methods for a metaclass, so metaclass objects all have the same methods), they are all instances of the same class -- the metaclass of the root class (unlike Smalltalk). (Thus, the metaclass of the root class is an instance of itself.) The reason for this is that all metaclasses inherit from root class; hence, they must inherit the class methods of the root class.
Support in languages and tools
The following are some of the most prominent programming languages that support metaclasses.
Some less widespread languages that support metaclasses include OpenJava, OpenC++, OpenAda, CorbaScript, ObjVLisp, Object-Z, MODEL-K, XOTcl, and MELDC. Several of these languages date from the early 1990s and are of academic interest.
Logtalk, an object-oriented extension of Prolog, also supports metaclasses.
Resource Description Framework (RDF) and Unified Modeling Language (UML) both support metaclasses.
de:Metaklasse es:Metaclase fr:M taclasse it:Metaclasse ja: pt:Metaclasse ru: