2.8 – Metatables
Every table and userdata object in Lua may have a metatable. This metatable is an ordinary Lua table that defines the behavior of the original table and userdata under certain special operations. You can change several aspects of the behavior of an object by setting specific fields in its metatable. For instance, when an object is the operand of an addition, Lua checks for a function in the field "__add"
in its metatable. If it finds one, Lua calls that function to perform the addition.
We call the keys in a metatable events and the values metamethods. In the previous example, the event is "add"
and the metamethod is the function that performs the addition.
You can query and change the metatable of an object through the set/getmetatable
functions (see 5.1).
A metatable may control how an object behaves in arithmetic operations, order comparisons, concatenation, and indexing. A metatable can also define a function to be called when a userdata is garbage collected. For each of those operations Lua associates a specific key called an event. When Lua performs one of those operations over a table or a userdata, it checks whether that object has a metatable with the corresponding event. If so, the value associated with that key (the metamethod) controls how Lua will perform the operation.
Metatables control the operations listed next. Each operation is identified by its corresponding name. The key for each operation is a string with its name prefixed by two underscores; for instance, the key for operation “add” is the string "__add"
. The semantics of these operations is better explained by a Lua function describing how the interpreter executes that operation.
The code shown here in Lua is only illustrative; the real behavior is hard coded in the interpreter and it is much more efficient than this simulation. All functions used in these descriptions (rawget
, tonumber
, etc.) are described in 5.1. In particular, to retrieve the metamethod of a given object, we use the expression
- metatable(obj)[event]
This should be read as
- rawget(metatable(obj) or {}, event)
That is, the access to a metamethod does not invoke other metamethods, and the access to objects with no metatables does not fail (it simply results in nil).
“add”: the
+
operation.The function
getbinhandler
below defines how Lua chooses a handler for a binary operation. First, Lua tries the first operand. If its type does not define a handler for the operation, then Lua tries the second operand.- function getbinhandler (op1, op2, event)
- return metatable(op1)[event] or metatable(op2)[event]
- end
Using that function, the behavior of the
op1 + op2
is- function add_event (op1, op2)
- local o1, o2 = tonumber(op1), tonumber(op2)
- if o1 and o2 then -- both operands are numeric?
- return o1 + o2 -- `+' here is the primitive `add'
- else -- at least one of the operands is not numeric
- local h = getbinhandler(op1, op2, "__add")
- if h then
- -- call the handler with both operands
- return h(op1, op2)
- else -- no handler available: default behavior
- error("...")
- end
- end
- end
“sub”: the
-
operation. Behavior similar to the “add” operation.“mul”: the
*
operation. Behavior similar to the “add” operation.“div”: the
/
operation. Behavior similar to the “add” operation.“pow”: the
^
(exponentiation) operation.- function pow_event (op1, op2)
- local o1, o2 = tonumber(op1), tonumber(op2)
- if o1 and o2 then -- both operands are numeric?
- return __pow(o1, o2) -- call global `__pow'
- else -- at least one of the operands is not numeric
- local h = getbinhandler(op1, op2, "__pow")
- if h then
- -- call the handler with both operands
- return h(op1, op2)
- else -- no handler available: default behavior
- error("...")
- end
- end
- end
“unm”: the unary
-
operation.- function unm_event (op)
- local o = tonumber(op)
- if o then -- operand is numeric?
- return -o -- `-' here is the primitive `unm'
- else -- the operand is not numeric.
- -- Try to get a handler from the operand
- local h = metatable(op).__unm
- if h then
- -- call the handler with the operand and nil
- return h(op, nil)
- else -- no handler available: default behavior
- error("...")
- end
- end
- end
“concat”: the
..
(concatenation) operation.- function concat_event (op1, op2)
- if (type(op1) == "string" or type(op1) == "number") and
- (type(op2) == "string" or type(op2) == "number") then
- return op1 .. op2 -- primitive string concatenation
- else
- local h = getbinhandler(op1, op2, "__concat")
- if h then
- return h(op1, op2)
- else
- error("...")
- end
- end
- end
“eq”: the
==
operation. The functiongetcomphandler
defines how Lua chooses a metamethod for comparison operators. A metamethod only is selected when both objects being compared have the same type and the same metamethod for the selected operation.- function getcomphandler (op1, op2, event)
- if type(op1) ~= type(op2) then return nil end
- local mm1 = metatable(op1)[event]
- local mm2 = metatable(op2)[event]
- if mm1 == mm2 then return mm1 else return nil end
- end
The “eq” event is defined as follows:
- function eq_event (op1, op2)
- if type(op1) ~= type(op2) then -- different types?
- return false -- different objects
- end
- if op1 == op2 then -- primitive equal?
- return true -- objects are equal
- end
- -- try metamethod
- local h = getcomphandler(op1, op2, "__eq")
- if h then
- return h(op1, op2)
- else
- return false
- end
- end
a ~= b
is equivalent tonot (a == b)
.“lt”: the
<
operation.- function lt_event (op1, op2)
- if type(op1) == "number" and type(op2) == "number" then
- return op1 < op2 -- numeric comparison
- elseif type(op1) == "string" and type(op2) == "string" then
- return op1 < op2 -- lexicographic comparison
- else
- local h = getcomphandler(op1, op2, "__lt")
- if h then
- return h(op1, op2)
- else
- error("...");
- end
- end
- end
a > b
is equivalent tob < a
.“le”: the
<=
operation.- function le_event (op1, op2)
- if type(op1) == "number" and type(op2) == "number" then
- return op1 <= op2 -- numeric comparison
- elseif type(op1) == "string" and type(op2) == "string" then
- return op1 <= op2 -- lexicographic comparison
- else
- local h = getcomphandler(op1, op2, "__le")
- if h then
- return h(op1, op2)
- else
- h = getcomphandler(op1, op2, "__lt")
- if h then
- return not h(op2, op1)
- else
- error("...");
- end
- end
- end
- end
a >= b
is equivalent tob <= a
. Note that, in the absence of a “le” metamethod, Lua tries the “lt”, assuming thata <= b
is equivalent tonot (b < a)
.“index”: The indexing access
table[key]
.- function gettable_event (table, key)
- local h
- if type(table) == "table" then
- local v = rawget(table, key)
- if v ~= nil then return v end
- h = metatable(table).__index
- if h == nil then return nil end
- else
- h = metatable(table).__index
- if h == nil then
- error("...");
- end
- end
- if type(h) == "function" then
- return h(table, key) -- call the handler
- else return h[key] -- or repeat operation on it
- end
“newindex”: The indexing assignment
table[key] = value
.- function settable_event (table, key, value)
- local h
- if type(table) == "table" then
- local v = rawget(table, key)
- if v ~= nil then rawset(table, key, value); return end
- h = metatable(table).__newindex
- if h == nil then rawset(table, key, value); return end
- else
- h = metatable(table).__newindex
- if h == nil then
- error("...");
- end
- end
- if type(h) == "function" then
- return h(table, key,value) -- call the handler
- else h[key] = value -- or repeat operation on it
- end
“call”: called when Lua calls a value.
- function function_event (func, ...)
- if type(func) == "function" then
- return func(unpack(arg)) -- primitive call
- else
- local h = metatable(func).__call
- if h then
- return h(func, unpack(arg))
- else
- error("...")
- end
- end
- end