Lua is an extension programming language designed to support general procedural programming with data description facilities. It is intended to be used as a light-weight, but powerful, configuration language for any program that needs one. Lua has been designed and implemented by W. Celes, R. Ierusalimschy and L. H. de Figueiredo.
Lua is implemented as a library, written in C. Being an extension language, Lua has no notion of a ``main'' program: it only works embedded in a host client, called the embedding program. This host program can invoke functions to execute a piece of code in Lua, can write and read Lua variables, and can register C functions to be called by Lua code. Through the use of C functions, Lua can be augmented to cope with a wide range of different domains, thus creating customized programming languages sharing a syntactical framework.
Lua is free-distribution software, and provided as usual with no guarantees, as stated in the copyright notice in the front page of this manual. The implementation described in this manual is available at the following URL's:
All statements in Lua are executed in a global environment. This environment, which keeps all global variables and functions, is initialized at the beginning of the embedding program and persists until its end.
The global environment can be manipulated by Lua code or by the embedding program, which can read and write global variables using functions in the library that implements Lua.
Global variables do not need declaration. Any variable is assumed to be global unless explicitly declared local (see Section 4.5.5). Before the first assignment, the value of a global variable is nil; this default can be changed (see Section 4.8).
The unit of execution of Lua is called a chunk. The syntax for chunks is:
A chunk may contain statements and function definitions,
and may be in a file or in a string inside the host program.
A chunk may optionally end with a return statement (see Section 4.5.3).
When a chunk is executed, first all its functions and statements are compiled,
then the statements are executed in sequential order.
All modifications a chunk effects on the global environment persist
after its end.
Those include modifications to global variables and definitions
of new functions.
(Actually, a function definition is an
assignment to a global variable; see Section 3.)
Chunks may be pre-compiled into binary form; see program luac for details. Text files with chunks and their binary pre-compiled forms are interchangeable. Lua automatically detects the file type and acts accordingly.
Lua is a dynamically typed language. Variables do not have types; only values do. Therefore, there are no type definitions in the language. All values carry their own type. Besides a type, all values also have a tag.
There are six basic types in Lua: nil, number,
string, function, userdata, and table.
Nil is the type of the value nil,
whose main property is to be different from any other value.
Number represents real (floating-point) numbers,
while string has the usual meaning.
The function type returns a string describing the type
of a given value (see Section 6.1).
Functions are considered first-class values in Lua. This means that functions can be stored in variables, passed as arguments to other functions and returned as results. When a function is defined in Lua, its body is compiled and stored in a given variable. Lua can call (and manipulate) functions written in Lua and functions written in C. They can be distinguished by their tags: all Lua functions have the same tag, and all C functions have the same tag, which is different from the tag of a Lua function.
The type userdata is provided to allow
arbitrary C pointers to be stored in Lua variables.
It corresponds to a void* and has no pre-defined operations in Lua,
besides assignment and equality test.
However, by using tag methods,
the programmer may define operations for userdata values
(see Section 4.8).
The type table implements associative arrays,
that is, arrays that can be indexed not only with numbers,
but with any value (except nil).
Therefore, this type may be used not only to represent ordinary arrays,
but also symbol tables, sets, records, etc.
To represent records, Lua uses the field name as an index.
The language supports this representation by
providing a.name as syntactic sugar for a["name"].
Tables may also carry methods.
Because functions are first class values,
table fields may contain functions.
The form t:f(x) is syntactic sugar for t.f(t,x),
which calls the method f from the table t passing
itself as the first parameter (see Section 4.7).
It is important to notice that tables are objects, and not values. Variables cannot contain tables, only references to them. Assignment, parameter passing and returns always manipulate references to tables, and do not imply any kind of copy. Moreover, tables must be explicitly created before used (see Section 4.6.7).
Tags are mainly used to select tag methods when
some events occur (see Section 4.8).
Each of the types nil, number and string has a different tag.
All values of each of these types have this same pre-defined tag.
Values of type function can have two different tags,
depending on whether they are Lua or C functions.
Finally,
values of type userdata and table can have
as many different tags as needed (see Section 4.8).
Tags are created with the function newtag,
and the function tag returns the tag of a given value.
To change the tag of a given table,
there is the function settag (see Section 6.1).
This section describes the lexis, the syntax and the semantics of Lua.
Lua is a case-sensitive language. Identifiers can be any string of letters, digits, and underscores, not beginning with a digit. The following words are reserved, and cannot be used as identifiers:
The following strings denote other tokens:
Literal strings can be delimited by matching single or double quotes,
and can contain the C-like escape sequences
'\n', '\t' and '\r'.
Literal strings can also be delimited by matching [[ ... ]].
Literals in this bracketed form may run for several lines,
may contain nested [[ ... ]] pairs,
and do not interpret escape sequences.
This form is specially convenient for
handling strings that contain program pieces or
other quoted strings.
Comments start anywhere outside a string with a
double hyphen (--) and run until the end of the line.
Moreover,
the first line of a chunk file is skipped if it starts with #.
This facility allows the use of Lua as a script interpreter
in Unix systems (see Section 8).
Numerical constants may be written with an optional decimal part, and an optional decimal exponent. Examples of valid numerical constants are:
All lines that start with a $ are handled by a pre-processor.
The $ can be followed by any of the following directives:
Directives can be freely nested.
Particularly, a $endinput may occur inside a $if;
in that case, even the matching $end is not parsed.
A cond part may be:
Lua provides some automatic conversions between values.
Any arithmetic operation applied to a string tries to convert
that string to a number, following the usual rules.
Conversely, whenever a number is used when a string is expected,
that number is converted to a string, according to the following rule:
if the number is an integer, it is written without exponent or decimal point;
otherwise, it is formatted following the %g
conversion specification of the printf function in the
standard C library.
For complete control on how numbers are converted to strings,
use the format function (see Section 6.2).
Functions in Lua can return many values. Because there are no type declarations, the system does not know how many values a function will return, or how many parameters it needs. Therefore, sometimes, a list of values must be adjusted, at run time, to a given length. If there are more values than are needed, then the last values are thrown away. If there are more needs than values, then the list is extended with as many nil's as needed. Adjustment occurs in multiple assignment and function calls.
Lua supports an almost conventional set of statements, similar to those in Pascal or C. The conventional commands include assignment, control structures and procedure calls. Non-conventional commands include table constructors (see Section 4.6.7), and local variable declarations (see Section 4.5.5).
A single name can denote a global or a local variable, or a formal parameter:
var should result in a table value,
where the field indexed by the expression value gets the assigned value.
The meaning of assignments and evaluations of global variables and
indexed variables can be changed by tag methods (see Section 4.8).
Actually,
an assignment x = val, where x is a global variable,
is equivalent to a call setglobal('x', val);
an assignment t[i] = val is equivalent to
settable_event(t, i, val).
See Section 4.8 for a description of these functions.
(Function setglobal is pre-defined in Lua.
Function settable_event is used only for explanation purposes.)
The syntax var.NAME is just syntactic sugar for
var["NAME"]:
A return is used to return values from a function or a chunk. Because they may return more than one value, the syntax for a return statement is:
An access to a global variable x is equivalent to a
call getglobal('x');
an access to an indexed variable t[i] is equivalent to
a call gettable_event(t, i).
See Section 4.8 for a description of these functions.
(Function getglobal is pre-defined in Lua.
Function gettable_event is used only for explanation purposes.)
The non-terminal exp1 is used to indicate that the values returned by an expression must be adjusted to one single value:
+ (addition),
- (subtraction), * (multiplication),
/ (division) and ^ (exponentiation),
and unary - (negation).
If the operands are numbers, or strings that can be converted to
numbers, according to the rules given in Section 4.3,
then all operations except exponentiation have the usual meaning.
Otherwise, an appropriate tag method is called (see Section 4.8).
An exponentiation always calls a tag method.
The standard mathematical library redefines this method for numbers,
giving the expected meaning to exponentiation
(see Section 6.3).
Equality first compares the types of its operands.
If they are different, then the result is nil.
Otherwise, their values are compared.
Numbers and strings are compared in the usual way.
Tables, userdata and functions are compared by reference,
that is, two tables are considered equal only if they are the same table.
The operator ~= is exactly the negation of equality (==).
Note that the conversion rules of Section 4.3
do not apply to equality comparisons.
Thus, "0"==0 evaluates to false.
The other operators work as follows. If both arguments are numbers, then they are compared as such. Otherwise, if both arguments are strings, their values are compared using lexicographical order. Otherwise, the ``order'' tag method is called (see Section 4.8).
and returns nil if its first argument is nil;
otherwise, it returns its second argument.
The operator or returns its first argument
if it is different from nil;
otherwise, it returns its second argument.
Both and and or use short-cut evaluation,
that is,
the second operand is evaluated only when necessary.
^ (exponentiation),
which is right associative.
The general syntax for constructors is:
The form lfieldlist1 is used to initialize lists.
The form ffieldlist1 initializes other fields in a table:
{x = 1, y = 4} is
in fact syntactic sugar for {["x"] = 1, ["y"] = 4}.
The form:
var:name(...)
is syntactic sugar for
var is evaluated only once.
f{...} is syntactic sugar for
f({...}), that is,
the parameter list is a single new table.
Because a function can return any number of results (see Section 4.5.3), the number of results must be adjusted before used. If the function is called as a statement (see Section 4.5.4), then its return list is adjusted to 0, thus discarding all returned values. If the function is called in a place that needs a single value (syntactically denoted by the non-terminal exp1), then its return list is adjusted to 1, thus discarding all returned values but the first one. If the function is called in a place that can hold many values (syntactically denoted by the non-terminal exp), then no adjustment is made.
Functions in Lua can be defined anywhere in the global level of a chunk. The syntax for function definition is:
When Lua pre-compiles a chunk,
all its function bodies are pre-compiled, too.
Then, when Lua ``executes'' the function definition,
its body is stored, with type function,
into the variable var.
It is in this sense that
a function definition is an assignment to a global variable.
Parameters act as local variables, initialized with the argument values.
n with the number of extra arguments,
and the extra arguments at positions 1, 2, ...
As an example, suppose definitions like:
f(3) a=3, b=nil f(3, 4) a=3, b=4 f(3, 4, 5) a=3, b=4
g(3) a=3, b=nil, arg={n=0} g(3, 4) a=3, b=4, arg={n=0} g(3, 4, 5, 8) a=3, b=4, arg={5, 8; n=2}
Results are returned using the return statement (see Section 4.5.3).
If control reaches the end of a function without a return instruction,
then the function returns with no results.
There is a special syntax for defining methods, that is, functions that have an extra parameter self.
self.
Notice that
the variable v must have been
previously initialized with a table value.
Lua provides a powerful mechanism to extend its semantics, called Tag Methods. A tag method (TM) is a programmer-defined function that can be called at many key points of the evaluation of a program, allowing a programmer to change the standard Lua behavior at these points. Each of these points is called an event.
The tag method called for any specific event is selected according to the tag of the values involved in the event (see Section 3). The function settagmethod changes the tag method associated with a given pair <tag, event>. Its first parameter is the tag, the second the event name (a string, see below), and the third parameter is the new method (a function), or nil to restore the default behavior. The function returns the previous tag method. Another function, gettagmethod, receives a tag and an event name and returns the current method associated with the pair.
Tag methods are called in the following events,
identified by the given names.
The semantics of tag methods is better explained by a Lua function
describing the behavior of the interpreter at each event.
The function not only shows when a tag method is called,
but also its arguments, its results and the default behavior.
Please notice that the code shown here 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
(rawgetglobal, tonumber, call, etc)
are described in Section 6.1.
+ operation is applied to non numerical operands.
The function getbinmethod defines how Lua chooses a tag method
for a binary operation.
First Lua tries the first operand.
If its tag does not define a tag method for the operation,
then Lua tries the second operand.
If it also fails, then it gets a tag method from tag 0:
- operation is applied to non numerical operands.
Behavior similar to "add" event.
* operation is applied to non numerical operands.
Behavior similar to "add" event.
/ operation is applied to non numerical operands.
Behavior similar to "add" event.
^ operation is applied.
- operation is applied to a non numerical operand.
< operation is applied to non numerical
or non string operands.
> operation is applied to non numerical
or non string operands.
Behavior similar to "lt" event.
<= operation is applied to non numerical
or non string operands.
Behavior similar to "lt" event.
>= operation is applied to non numerical
or non string operands.
Behavior similar to "lt" event.
"gettable" for its semantics.
newtag.
getglobal is pre-defined in Lua (see Section 6.1).
setglobal is pre-defined in Lua (see Section 6.1).
gc_event(nil).
Because Lua is an extension language,
all Lua actions start from C code calling a function from the Lua library.
Whenever an error occurs during Lua compilation or execution,
the error method is called,
and then the corresponding function from the library
(lua_dofile, lua_dostring, or lua_callfunction)
is terminated returning an error condition.
The only argument to the error method is a string
describing the error.
The default method prints this message in stderr.
If needed, it is possible to change the error method with the
function seterrormethod,
which gets the new error handler as its only parameter
(see Section 6.1).
The standard I/O library uses this facility to redefine the error method,
using the debug facilities (see Section 7),
in order to print some extra information,
like the call stack.
To provide more information about errors,
Lua programs should include the compilation pragma $debug.
When an error occurs in a program compiled with this option,
the I/O error routine is able to print the number of the
lines where the calls (and the error) were made.
Lua code can explicitly generate an error by calling the built-in
function error (see Section 6.1).
This section describes the API for Lua, that is, the set of C functions available to the host program to communicate with the Lua library. The API functions can be classified in the following categories:
lua.h.
lua_Object,
which works like an abstract type in C that can hold any Lua value.
Values of type lua_Object have no meaning outside Lua;
for instance,
the comparison of two lua_Object's is undefined.
To check the type of a lua_Object,
the following functions are available:
lua_isnumber accepts numbers and numerical strings,
whereas
lua_isstring accepts strings and numbers (see Section 4.3),
and lua_isfunction accepts Lua and C functions.
To check the tag of a lua_Object,
the following function is available:
To translate a value from type lua_Object to a specific C type,
the programmer can use:
lua_getnumber converts a lua_Object to a floating-point number.
This lua_Object must be a number or a string convertible to number
(see Section 4.3); otherwise, the function returns 0.
lua_getstring converts a lua_Object to a string (char*).
This lua_Object must be a string or a number;
otherwise, the function returns 0 (the NULL pointer).
This function does not create a new string,
but returns a pointer to a string inside the Lua environment.
Because Lua has garbage collection,
there is no guarantee that such pointer will be valid after the block ends
(see below).
lua_getcfunction converts a lua_Object to a C function.
This lua_Object must have type CFunction;
otherwise, the function returns 0 (the NULL pointer).
The type lua_CFunction is explained in Section 5.5.
lua_getuserdata converts a lua_Object to void*.
This lua_Object must have type userdata;
otherwise, the function returns 0 (the NULL pointer).
Because Lua has automatic memory management and garbage collection,
a lua_Object has a limited scope,
and is only valid inside the block where it was created.
A C function called from Lua is a block,
and its parameters are valid only until its end.
It is good programming practice to convert Lua objects to C values
as soon as they are available,
and never to store lua_Objects in C global variables.
A garbage collection cycle can be forced by:
limit makes the next cycle occur only
when that number of new objects have been created.
If limit=0, then Lua uses an adaptable heuristics to set this limit.
All communication between Lua and C is done through two abstract data types, called lua2C and C2lua. The first one, as the name implies, is used to pass values from Lua to C: parameters when Lua calls C and results when C calls Lua. The structure C2lua is used in the reverse direction: parameters when C calls Lua and results when Lua calls C.
The structure lua2C is an abstract array, which can be indexed with the function:
number starts with 1.
When called with a number larger than the array size,
this function returns LUA_NOOBJECT.
In this way, it is possible to write C functions that receive
a variable number of parameters,
and to call Lua functions that return a variable number of results.
Notice that the structure lua2C cannot be directly modified by C code.
The second structure, C2lua, is a stack. Pushing elements into this stack is done with the following functions:
lua_Object,
and leave the result on the top of C2lua.
The function
As a general rule, all API functions pop from the stack all elements that they use.
Because userdata are objects,
the function lua_pushusertag may create a new userdata.
If Lua has a userdata with the given value (void*) and tag,
that userdata is pushed.
Otherwise, a new userdata is created, with the given value and tag.
If this function is called with
tag=LUA_ANYTAG,
then Lua will try to find any userdata with the given value,
no matter its tag.
If there is no userdata with that value, then a new one is created,
with tag=0.
Userdata can have different tags, whose semantics are only known to the host program. Tags are created with the function:
lua_settag changes the tag of
the object on the top of C2lua (and pops it);
the object must be a userdata or a table.
tag must be a value created with lua_newtag.
When C code calls Lua repeatedly, as in a loop, objects returned by these calls can accumulate, and may cause a stack overflow. To avoid this, nested blocks can be defined with the functions:
lua_Object's created inside it are released.
The use of explicit nested blocks is strongly encouraged.
lua_dofile returns 2 if for any reason
it could not open the file.
The function lua_dofile, if called with argument NULL,
executes the stdin stream.
Function lua_dofile is also able to execute pre-compiled chunks.
It automatically detects whether the file is text or binary,
and loads it accordingly (see program luac).
These functions return, in structure lua2C, any values eventually returned by the chunks. They also empty the stack C2lua.
To store a value previously pushed onto C2lua in a global variable, there is the function:
Tables can also be manipulated via the API. The function
To store a value in an index, the program must push the table, the index, and the value onto C2lua, and then call the function:
dofile or dostring can be called from the host program.
This is done using the following protocol:
first, the arguments to the function are pushed onto C2lua
(see Section 5.1), in direct order, i.e., the first argument is pushed first.
Then, the function is called using
lua_getresult,
which is just another name to the function lua_lua2C.
Notice that the function lua_callfunction
pops all elements from the C2lua stack.
The following example shows how a C program may do the equivalent to the Lua code:
Some special Lua functions have exclusive interfaces. A C function can generate a Lua error calling the function
exit(1).
The error handler method (see Section 4.9) can be changed with:
Tag methods can be changed with:
lua_Object,
which is the old tag method value.
To get just the current value of a tag method,
there is the function
lua_CFunction,
which is defined as
In order to communicate properly with Lua, a C function must follow a protocol, which defines the way parameters and results are passed.
A C function receives its arguments in structure lua2C;
to access them, it uses the macro lua_getparam,
again just another name to lua_lua2C.
To return values, a C function just pushes them onto the stack C2lua,
in direct order (see Section 5.1).
Like a Lua function, a C function called by Lua can also return
many results.
For some examples, see files strlib.c,
iolib.c and mathlib.c in Lua distribution.
As noted in Section 5.5, lua_Objects are volatile.
If the C code needs to keep a lua_Object
outside block boundaries,
then it must create a reference to the object.
The routines to manipulate references are the following:
lua_ref creates a reference
to the object that is on the top of the stack,
and returns this reference.
If lock is true, the object is locked:
this means the object will not be garbage collected.
Notice that an unlocked reference may be garbage collected.
Whenever the referenced object is needed,
a call to lua_getref
returns a handle to it;
if the object has been collected,
lua_getref returns LUA_NOOBJECT.
When a reference is no longer needed,
it can be freed with a call to lua_unref.
The set of predefined functions in Lua is small but powerful. Most of them provide features that allow some degree of reflexivity in the language. Some of these features cannot be simulated with the rest of the language nor with the standard Lua API. Others are just convenient interfaces to common API functions.
The libraries, on the other hand, provide useful routines that are implemented directly through the standard API. Therefore, they are not necessary to the language, and are provided as separate C modules. Currently there are three standard libraries:
strlib_open, mathlib_open, and iolib_open,
declared in lualib.h.
func with
the arguments given by the table arg.
The call is equivalent to
arg.n is not defined,
then Lua stops getting arguments at the first nil value.
If retmode is absent,
all results from func are just returned by the call.
If retmode is equal to "pack",
the results are packed in a single table.
That is, call returns just one table;
at index n, the table has the total number of results
from the call;
the first result is at index 1, etc.
For instance, the following calls produce the following results:
limit, is a number that
makes the next cycle occur when that number of new
objects have been created.
If absent, Lua uses an adaptable algorithm to set
this limit.
collectgarbage is equivalent to
the API function lua_collectgarbage.
stdin).
If there is any error executing the file,
then dofile returns nil.
Otherwise, it returns the values returned by the chunk,
or a non nil value if the chunk returns no values.
It issues an error when called with a non string argument.
dofile is equivalent to the API function lua_dofile.
errmethod is temporarily set as the error method,
while string runs.
As a particular case, if errmethod is nil,
no error messages will be issued during the execution of the string.
newtag is equivalent to the API function lua_newtag.
In Lua there is no declaration of fields;
semantically, there is no difference between a
field not present in a table or a field with value nil.
Therefore, the function only considers fields with non nil values.
The order in which the indices are enumerated is not specified,
not even for numeric indices
(to traverse a table in numeric order,
use a counter).
If the table is modified in any way during a traversal,
the semantics of next is undefined.
This function cannot be written with the standard API.
next,
but iterates over the global variables.
Its single argument is the name of a global variable,
or nil to get a first name.
Similarly to next, it returns the name of another variable
and its value,
or nil if there are no more variables.
There can be no assignments to global variables during the traversal;
otherwise the semantics of nextvar is undefined.
This function cannot be written with the standard API.
"nil" (a string, not the value nil),
"number",
"string",
"table",
"function",
and "userdata".
type is equivalent to the API function lua_type.
tag is equivalent to the API function lua_tag.
tag must be a value created with newtag
(see Section 6.1).
For security reasons,
it is impossible to change the tag of a userdata from Lua.
lua_dofile, lua_dostring, or lua_callfunction).
It never returns.
error is equivalent to the API function lua_error.
table[index],
without invoking any tag method.
table must be a table,
and index is any value different from nil.
table[index]=value,
without invoking any tag method.
table must be a table,
index is any value different from nil,
and value is any Lua value.
name does not need to be a syntactically valid variable name.
Therefore, this function can set global variables with strange names like
"m v 1" or 34.
It returns the value of its second argument.
name does not need to be a
syntactically valid variable name.
newmethod must be a function or nil,
in which case the error handler does nothing.
Returns the old error handler.
newmethod is nil,
it restores the default behavior for the given event.
pattern in str.
If it finds one, then it returns the indices on str
where this occurrence starts and ends;
otherwise, it returns nil.
If the pattern specifies captures,
the captured strings are returned as extra results.
A third optional numerical argument specifies where to start the search;
its default value is 1.
A value of 1 as a fourth optional argument
turns off the pattern matching facilities,
so the function does a plain ``find substring'' operation,
with no characters in pattern being considered ``magic''.
s,
starting at i and running until j.
If i or j are negative,
they are replaced by the length of the string minus their
absolute value plus 1.
Therefore, -1 points to the last character of s
and -2 to the previous one.
If j is absent, it is assumed to be equal to -1
(which is the same as the string length).
In particular,
the call strsub(s,1,j) returns a prefix of s
with length j,
and the call strsub(s, -i) returns a suffix of s
with length i.
n copies of
the string s.
s[i].
If i is absent, then it is assumed to be 1.
printf family of
standard C functions.
The only differences are that the options/modifiers
*, l, L, n, p,
and h are not supported,
and there is an extra option, q.
This option formats a string in a form suitable to be safely read
back by the Lua interpreter;
that is,
the string is written between double quotes,
and all double quotes, returns and backslashes in the string
are correctly escaped when written.
For instance, the call
The options c, d, E, e, f,
g i, o, u, X, and x all
expect a number as argument,
whereas q and s expect a string.
Note that the * modifier can be simulated by building
the appropriate format string.
For example, "%*g" can be simulated with
"%"..width.."g".
s,
where all occurrences of the pattern pat have been
replaced by a replacement string specified by repl.
This function also returns, as a second value,
the total number of substitutions made.
If repl is a string, then its value is used for replacement.
Any sequence in repl of the form %n
with n between 1 and 9
stands for the value of the n-th captured substring.
If repl is a function, then this function is called every time a
match occurs, with the following arguments:
If table is present, then the first argument is this table
and the second one is a match counter (1 for the first call).
Independently of these two optional arguments,
all captured substrings are passed as arguments,
in order (see below);
If the value returned by this function is a string,
then it is used as the replacement string;
otherwise, the replacement string is the empty string.
A last optional parameter n limits
the maximum number of substitutions to occur.
For instance, when n is 1 only the first occurrence of
pat is replaced.
See some examples below:
x = gsub("home = $HOME, user = $USER", "$(%w%w*)", getenv) --> x="home = /home/roberto, user = roberto" (for instance)
x = gsub("4+5 = $return 4+5$", "$(.-)%$", dostring) --> x="4+5 = 9"
function f(t, i, v) return t[v] end t = {name="lua", version="3.0"} x = gsub("$name - $version", "$(%w%w*)", f, t) --> x="lua - 3.0"
t = {"apple", "orange", "lime"} x = gsub("x and x and x", "x", rawgettable, t) --> x="apple and orange and lime"
t = {} dummy, t.n = gsub("first second word", "(%w%w*)", rawsettable, t) --> t={"first", "second", "word"; n=3}
()%.[*-?)
- represents the character x itself.
()%.[*-?.
] in char-set, it must be the first character.
A range of characters may be specified by
separating the end characters of the range with a -;
e.g., A-Z specifies the upper case characters.
If - appears as the first or last character of char-set,
then it represents itself.
All classes %x described above can also be used as
components in a char-set.
All other characters in char-set represent themselves.
*,
which matches 0 or more repetitions of characters in the class.
These repetition items will always match the longest possible sequence.
-,
which also matches 0 or more repetitions of characters in the class.
Unlike *,
these repetition items will always match the shortest possible sequence.
?,
which matches 0 or 1 occurrence of a character in the class;
%b() matches expressions with
balanced parentheses.
^ at the beginning of a pattern anchors the match at the
beginning of the subject string.
A $ at the end of a pattern anchors the match at the
end of the subject string.
"(a*(.)%w(%s*))",
the part of the string matching "a*(.)%w(%s*)" is
stored as the first capture (and therefore has number 1);
the character matching . is captured with number 2,
and the part matching %s* has number 3.
This library is an interface to some functions of the standard C math library.
In addition, it registers a tag method for the binary operator ^ that
returns x^y when applied to numbers x^y.
The library provides the following functions:
The function max returns the maximum
value of its numeric arguments.
Similarly, min computes the minimum.
Both can be used with an unlimited number of arguments.
The functions random and randomseed are interfaces to
the simple random generator functions rand and srand,
provided by ANSI C.
The function random returns pseudo-random numbers in the
range [0,1).
All input and output operations in Lua are done over two
file handles, one for reading and one for writing.
These handles are stored in two Lua global variables,
called _INPUT and _OUTPUT.
The global variables
_STDIN, _STDOUT and _STDERR
are initialized with file descriptors for
stdin, stdout and stderr.
Initially, _INPUT=_STDIN and _OUTPUT=_STDOUT.
A file handle is a userdata containing the file stream FILE*,
and with a distinctive tag created by the I/O library.
Unless otherwise stated, all I/O functions return nil on failure and some value different from nil on success.
This function may be called in two ways.
When called with a file name, it opens the named file,
sets its handle as the value of _INPUT,
and returns this value.
It does not close the current input file.
When called without parameters,
it closes the _INPUT file,
and restores stdin as the value of _INPUT.
If this function fails, it returns nil, plus a string describing the error.
System dependent: if filename starts with a |,
then a piped input is open, via function popen.
Not all systems implement pipes.
Moreover,
the number of files that can be open at the same time is
usually limited and depends on the system.
This function may be called in two ways.
When called with a file name,
it opens the named file,
sets its handle as the value of _OUTPUT,
and returns this value.
It does not close the current output file.
Notice that, if the file already exists,
then it will be completely erased with this operation.
When called without parameters,
this function closes the _OUTPUT file,
and restores stdout as the value of _OUTPUT.
If this function fails, it returns nil, plus a string describing the error.
System dependent: if filename starts with a |,
then a piped output is open, via function popen.
Not all systems implement pipes.
Moreover,
the number of files that can be open at the same time is
usually limited and depends on the system.
This function opens a file named filename and sets it as the
value of _OUTPUT.
Unlike the writeto operation,
this function does not erase any previous content of the file.
If this function fails, it returns nil,
plus a string describing the error.
Notice that function writeto is available to close an output file.
This function deletes the file with the given name. If this function fails, it returns nil, plus a string describing the error.
This function renames file named name1 to name2.
If this function fails, it returns nil,
plus a string describing the error.
This function returns a string with a file name that can safely be used for a temporary file. The file must be explicitly removed when no longer needed.
This function reads the file _INPUT
according to a read pattern, that specifies how much to read;
characters are read from the current input file until
the read pattern fails or ends.
The function read returns a string with the characters read,
even if the pattern succeeds only partially,
or nil if the read pattern fails and
the result string would be empty.
When called without parameters,
it uses a default pattern that reads the next line
(see below).
A read pattern is a sequence of read pattern items.
An item may be a single character class
or a character class followed by ? or by *.
A single character class reads the next character from the input
if it belongs to the class, otherwise it fails.
A character class followed by ? reads the next character
from the input if it belongs to the class;
it never fails.
A character class followed by * reads until a character that
does not belong to the class, or end of file;
since it can match a sequence of zero characters, it never fails.
Notice that the behavior of read patterns is different from
the regular pattern matching behavior,
where a * expands to the maximum length such that
the rest of the pattern does not fail.
With the read pattern behavior
there is no need for backtracking the reading.
A pattern item may contain sub-patterns enclosed in curly brackets, that describe skips. Characters matching a skip are read, but are not included in the resulting string.
Following are some examples of read patterns and their meanings:
"." returns the next character, or nil on end of file.
".*" reads the whole file.
"[^\n]*{\n}" returns the next line
(skipping the end of line), or nil on end of file.
This is the default pattern.
"{%s*}%S%S*" returns the next word
(maximal sequence of non white-space characters),
skipping spaces if necessary,
or nil on end of file.
"{%s*}[+-]?%d%d*" returns the next integer
or nil if the next characters do not conform to an integer format.
This function writes the value of each of its arguments to the
file _OUTPUT.
The arguments must be strings or numbers.
To write other values,
use tostring or format before write.
If this function fails, it returns nil,
plus a string describing the error.
This function returns a string containing date and time
formatted according to the given string format,
following the same rules of the ANSI C function strftime.
When called without arguments,
it returns a reasonable date and time representation that depends on
the host system.
This function calls the C function exit,
with an optional code,
to terminate the program.
The default value for code is 1.
Returns the value of the environment variable varname,
or nil if the variable is not defined.
This function is equivalent to the C function system.
It passes command to be executed by an operating system shell.
It returns an error code, which is system-dependent.
Lua has no built-in debugging facilities.
Instead, it offers a special interface,
by means of functions and hooks,
which allows the construction of different
kinds of debuggers, profilers, and other tools
that need ``inside information'' from the interpreter.
This interface is declared in the header file luadebug.h.
The main function to get information about the interpreter stack is
lua_Function) to the activation record
of the function executing at a given level.
Level 0 is the current running function,
while level n+1 is the function that has called level n.
When called with a level greater than the stack depth,
lua_stackedfunction returns LUA_NOOBJECT.
The type lua_Function is just another name
to lua_Object.
Although, in this library,
a lua_Function can be used wherever a lua_Object is required,
when a parameter has type lua_Function
it accepts only a handle returned by
lua_stackedfunction.
Three other functions produce extra information about a function:
lua_funcinfo gives the file name and the line where the
given function has been defined.
If the ``function'' is in fact the main code of a chunk,
then linedefined is 0.
If the function is a C function,
then linedefined is -1, and filename is "(C)".
The function lua_currentline gives the current line where
a given function is executing.
It only works if the function has been compiled with debug
information (see Section 4.9).
When no line information is available, it returns -1.
Function lua_getobjname tries to find a reasonable name for
a given function.
Because functions in Lua are first class values,
they do not have a fixed name:
Some functions may be the value of many global variables,
while others may be stored only in a table field.
Function lua_getobjname first checks whether the given
function is a tag method.
If so, it returns the string "tag-method",
and name is set to point to the event name.
Otherwise, if the given function is the value of a global variable,
then lua_getobjname returns the string "global",
and name points to the variable name.
If the given function is neither a tag method nor a global variable,
then lua_getobjname returns the empty string,
and name is set to NULL.
The following functions allow the manipulation of the local variables of a given activation record. They only work if the function has been compiled with debug information (see Section 4.9).
lua_getlocal returns the value of a local variable,
and sets name to point to the variable name.
local_number is an index for local variables.
The first parameter has index 1, and so on, until the
last active local variable.
When called with a local_number greater than the
number of active local variables,
or if the activation record has no debug information,
lua_getlocal returns LUA_NOOBJECT.
Formal parameters are the first local variables.
The function lua_setlocal sets the local variable
local_number to the value previously pushed on the stack
(see Section 5.1).
If the function succeeds, then it returns 1.
If local_number is greater than the number
of active local variables,
or if the activation record has no debug information,
then this function fails and returns 0.
The Lua interpreter offers two hooks for debugging purposes:
typedef void (*lua_LHFunction) (int line); extern lua_LHFunction lua_linehook;
lua_funcinfo);
when leaving a function, func is LUA_NOOBJECT,
file is "(return)", and line is 0.
The other hook is called every time the interpreter changes
the line of code it is executing.
Its only parameter is the line number
(the same information which is provided by the call
lua_currentline(lua_stackedfunction(0))).
This second hook is only called if the active function
has been compiled with debug information (see Section 4.9).
A hook is disabled when its value is NULL,
which is the initial value of both hooks.
Although Lua has been designed as an extension language,
the language can also be used as a stand-alone interpreter.
An implementation of such an interpreter,
called simply lua,
is provided with the standard distribution.
This program can be called with any sequence of the following arguments:
EOF.
stat as a Lua chunk.
var=exp as a Lua chunk.
filename as a Lua chunk.
EOF,
then will set a to 1,
and finally will run file prog.lua.
Please notice that the interaction with the shell may lead to unintended results. For instance, a call like
a to the string "name".
Instead, the quotes will be handled by the shell,
lua will get only a=name to run,
and a will finish with nil,
because the global variable name has not been initialized.
Instead, one should write
The authors would like to thank CENPES/PETROBRAS which, jointly with TeCGraf, used extensively early versions of this system and gave valuable comments. The authors would also like to thank Carlos Henrique Levy, who found the name of the game. Lua means moon in Portuguese.
Although great care has been taken to avoid incompatibilities with the previous public versions of Lua, some differences had to be introduced. Here is a list of all these incompatibilities.
setfallback has been rewritten in
a way that uses tag methods to fully emulate the old behavior
of fallbacks.
newtag.
Nevertheless, old user defined tags are still accepted
(user defined tags must be positive;
newtag uses negative numbers).
Tag methods cannot be set for such user defined tags,
and fallbacks do not affect tags created by newtag.
2<"12", giving weird results.
Now this is an error.
"-" (hyphen) now is ``magic'' in pattern matching.
write has been supersed by
function format;
therefore this facility has been dropped.
read now uses read patterns to specify
what to read;
this is incompatible with the old format options.
strfind now accepts patterns,
so it may have a different behavior when the pattern includes
special characters.
date and time (from iolib)
have been superseded by the new, more powerful version of function date.
append (from iolib) now returns 1 whenever it succeeds,
whether the file is new or not.
int2str (from strlib) has been superseded by new
function format, with parameter "%c".
lua.h provides compatibility macros,
so there is no need to change programs.
lua_pushliteral now is just a macro to
lua_pushstring.
type now returns the string "function"
both for C and Lua functions.
Because Lua functions and C functions are compatible,
this behavior is usually more useful.
When needed, the second result of function type may be used
to distinguish between Lua and C functions.
==,
instead of =.
@(size) has been substituted by {}.
The list constructor (formerly @[...]) and the record
constructor (formerly @{...}) now are both coded like
{...}.
When the construction involves a function call,
like in @func{...},
the new syntax does not use the @.
More important, {\em a construction function must now
explicitly return the constructed table}.
lua_call no longer has the parameter nparam.
lua_pop is no longer available,
since it could lead to strange behavior.
In particular,
to access results returned from a Lua function,
the new macro lua_getresult should be used.
lua_storefield and lua_storeindexed
have been replaced by
lua_errorfunction has been
replaced by the fallback mechanism (see Section 4.9).
lua_getindexed and lua_getfield.