As Lua supports duck typing through the use of metatables, the ability to create "objects" can be achieved. This is essentially objected-oriented programming. A table in Lua is an object in more than one sense. Like objects, tables have a state. Like objects, tables have an identity that is independent of their values; specifically, two objects (tables) with the same value are different objects, whereas an object can have different values at different times, but it is always the same object. Like objects, tables have a life cycle that is independent of who created them or where they were created.
Operations on Tables
Tables can have their own operations:
This definition creates a new function and stores it in field withdraw of the Account object. Then, we can call it as:
This kind of function is almost what we call a method. However, the use of the global name Account inside the function is a bad programming practice. First, this function will work only for this particular object. Second, even for this particular object the function will work only as long as the object is stored in that particular global variable; if we change the name of this object, withdraw does not work any more:
Such behavior violates the previous principle that objects have independent life cycles. A more flexible approach is to operate on the receiver of the operation. For that, we would have to define our method with an extra parameter, which tells the method on which object it has to operate. This parameter usually has the name self or this:
Now, when we call the method we have to specify on which object it has to operate:
With the use of a self parameter, we can use the same method for many objects:
This use of a self parameter is a central point in any object-oriented language. Most OO languages have this mechanism partly hidden from the programmer, so that she does not have to declare this parameter (although she still can use the name self or this inside a method). Lua can also hide this parameter, using the colon operator. We can rewrite the previous method definition as
and the method call as
The effect of the colon is to add an extra hidden parameter in a method definition and to add an extra argument in a method call. The colon is only a syntactic facility, although a convenient one; there is nothing really new here. We can define a function with the dot syntax and call it with the colon syntax, or vice-versa, as long as we handle the extra parameter correctly:
Now our objects have an identity, a state, and operations over this state.
So far, we've shown how to create a single once-use object. However, we might want to manage multiple accounts. Here's how we do it:
This creates the constructor
Account.new(balance), which returns a new account object. The
setmetatable makes it so the new account will look in the
Account table for its metamethods, and the metamethod
Account.__index = Account makes it look in the
Account table for its methods. Let's add some methods then!
To use it:
A custom object is something that you create that has properties like the other Roblox objects, such as game.Workspace.Brick.Transparency
Declaring an object
Your data type here will be a "Vector2".
Now, we can call a new object of the class as such: