Lua Scope and Environment Tutorials
Variables that we have access to are said to be visible. The scope of a variable is the containing block of code in which it is visible. Scopes are created and destroyed as the program executes and passes in and out of blocks. The variables contained within these blocks are created and destroyed according to the rules described on this page. When we enter a block and a new scope, we are entering an inner scope. Outer scopes are visible from inner scopes, but not vice versa.
In Lua, blocks of code can be defined using functions and the do...end keywords:
The above example defines x and why as global variables and a function called foo which contains a scope. We create the variable x in the inner function scope. When we exit the function, the scope ends, and the variable x is deleted and is no longer visible. The do...end block contains similar functionality.
Any variable not in a defined block is said to be in the global scope. Anything in the global scope is accessible by all inner scopes.
In the above example, g is in the global scope; i.e. no enclosing block is defined. The function foo is also in the global scope. We enter the foo function scope when foo() is called. We can print the value of g because we can see the outer scope from the inner foo scope.
The "local" Keyword
We use the keyword "local" to describe any variables we would like to keep local to the scope where they are defined in.
In the above example, "gbA" and "foo" are dynamically declared in the current environment (_ENV). Since foo is not in the lexical scope, Lua automatically looks up foo in the environment table _ENV. Try changing the call "foo()" on line 6 to "_ENV.foo()". Notice that it will behave just as calling foo without explicitly specifying the environment table.
In the above example, "do and end" encloses a block containing the declaration of the local variables. You can see that we can print its value, when we are in the value's scope. When we exit the scope (the end keyword) we lose visibility of the local variables in that scope. When we print the value of the variables once outside the scope, we get nil. This means "variable not found". The keyword local is placed before any variable that we want to remain visible only to that scope and its inner scopes.
In the following example, x starts with the value 1. We create a block using the "do and end" keywords. We use the local keyword to specify that we want a new variable also called x which is only visible in this block or scope.
You can see that once the do...end scope has ended, the second declaration of x disappears, and we revert back to the old one.
Global Scope and "local" Variables
The local keyword can be used in any scope, not just inner and function scopes. This may seem a little unintuitive, but even the global scope in Lua can become an inner scope if it is used as a module.
As we mentioned above, it is more efficient to use local variables ( lexical scope) whenever possible because of the implementation of Lua. The technical reason for this is that local variables in the lexical scope are referenced via a direct assigned number, whereas global variables are stored in the environment table _ENV, which is accessed with a key (the variable name). Table lookups are very fast in Lua, but still not as fast as local register lookups. Local Lua variables are similar to stack variables in C code except that they can be saved as closures. A closure is also known as an 'upvalue' in Lua terminology.
Closure (Upvalue) Example:
The Environment Table _ENV
In the Lua scripting language, everything is stored in a table, including the current environment. The environment is implicitly accessed when looking up dynamic variables, but you can also specifically reference variables in the current scope by using the _ENV table.
The _ENV is stored as a closure (a.k.a upvalue) in the current script and is, for this reason, also applied to all functions and inner functions in the script. A function can, however, change the environment as shown in the next example.
Notice how we save function "print" as a local variable "myprint" on line 1. The above script would generate an exception without this construction. Change "myprint" to "print" on line 5 and the script will still work, but the script will fail if you try the same change on line 7. Go ahead and make the changes above and you will see you get an exception when line 7 is run. The reason we get the exception is that the "print" function is not defined in the new environment we create on line 6.
The Server's Environments
So by now you should understand that the current environment is a Lua table that can be explicitly referenced by using the name '_ENV' and that the environment can be changed at any time by assigning _ENV to a Lua table. Variables can be in the lexical scope (static scope) or in the dynamic scope (_ENV). If the variable is not in the lexical scope, it will be search for in the dynamic scope. In example 9,8, we created a closure (myprint) so we could output text in the two functions (foo and bar) overriding the default _ENV. This was necessary since the new environments we created in "foo" and "bar" did not have a print function.
A new environment (a new table) can be made to inherit another table. In Lua, this is done by using metatables. The following examples introduces metatables and shows how to chain two tables -- in other words, how to make Lua search for variables by following the chain. You will learn more about metatables in the Lua Methamethods tutorial.
Running the above example prints out "Hello" and "world" on two separate lines in the iframe. Function print is not in the new environment table, but it still works since we chain the new environment to the LSP page's environment.
In the above example, change __index = _ENV to __index = _G and rerun the example. Notice that 'world' is now printed to the server's console window and not in the iframe. Recall that we have two print functions, one for the LSP page, which sends data as response to the client and the Lua global print function, which prints to the console.
As a final test, remove or comment out line 8 where we set the metatable an rerun the example. You should now get an exception since the "print" function is not found.
The server's three environments
The Mako Server provides three environments, all accessible from LSP pages as shown in the image to the right.
- The global Lua environment _G
- The LSP page's request/response environment
- The application's environment
We have already introduced you to the LSP page's environment and the Lua global environment _G. The application environment is an additional environment that can be used as a global environment for the application. As an example, the Mako Server can load multiple applications and each application has it's own application environment where you can keep common code for the application.
The following example shows the relationship between the three environments.
Notice how the address for the request/response environment (_ENV) changes each time you click the Run button, but that the app table and _G stay the same. A new request/response environment is created each time the page is run. This environment is also available to server side included pages and you can pass variables from one LSP page to another LSP page by using this environment.
The above example also prints out the app table and the global table to the server's console window on line 10 and 12. The key/value data printed for the 'app' table is generic code used by this tutorial's engine.