tolua++ - Reference Manual

• Support for std::string as a basic type (this can be turned off by a command line option).
• Support for class templates

As well as other features and bugfixes.

tolua is a tool that greatly simplifies the integration of C/C++ code with Lua. Based on a cleaned header file (or extracts from real header files), tolua automatically generates the binding code to access C/C++ features from Lua. Using Lua API and tag method facilities, tolua maps C/C++ constants, external variables, functions, classes, and methods to Lua.

This manual is for tolua++ version 1.0 and is implemented upon Lua 5.0 and based on tolua 5.0. See Compatibility for details on switching from older versions.

The sections below describe how to use tolua. Please contact us with bug reports, suggestions, and comments.

• Shortcuts:
• How tolua works
• How to use tolua
• Basic Concepts
• Binding constants
• Binding external variables
• Binding functions
• Binding struct fields
• Binding classes and methods
• Binding properties
• Class Templates
• Module definition
• Renaming constants, variables and functions
• Storing additional fields
• Additional features
• Exported utility functions
• Embedded Lua code
• Customizing tolua++
• Compatibility with older versions
• Changes since v3 *
• Changes since v2.*
• Changes since v1.*
• Credits
• Availability

How tolua works

Let's start with some examples. If we specify as input the following C-like header file to tolua:

#define FALSE 0
#define TRUE 1

enum { 
 POINT = 100, 
 LINE, 
 POLYGON
}

Object* createObejct (int type);
void drawObject (Object* obj, double red, double green, double blue);
int isSelected (Object* obj);

...
myLine = createObject(LINE)
...
if isSelected(myLine) == TRUE then
  drawObject(myLine, 1.0, 0.0, 0.0);
else
  drawObject(myLine, 1.0, 1.0, 1.0);
end
...

#define FALSE 0
#define TRUE 1

class Shape
{
  void draw (void);
  void draw (double red, double green, double blue);
  int isSelected (void);
};

class Line : public Shape
{
 Line (double x1, double y1, double x2, double y2);
 ~Line (void);
};

...
myLine = Line:new (0,0,1,1)
...
if myLine:isSelected() == TRUE then
 myLine:draw(1.0,0.0,0.0)
else
 myLine:draw()
end
...
myLine:delete()
...

How to use toLua

tolua -o myfile.c myfile.pkg

The generated code must be compiled and linked with the application to provide the desired access from Lua. Each parsed file represents a package being exported to Lua. By default, the package name is the input file root name (myfile in the example). The user can specify a different name for the package:

tolua -n pkgname -o myfile.c myfile.pkg

The package should also be explicitly initialized. To initialize the package from our C/C++ code, we must declare and call the initialization function. The initialization function is defined as

int tolua_pkgname_open (lua_State*);

where pkgname represents the name of the package being bound. If we are using C++, we can opt for automatic initialization:

tolua -a -n pkgname -o myfile.c myfile.pkg

In that case, the initialization function is automatically called. However, if we are planning to use multiple Lua states, automatic initialization does not work, because the order static variables are initialized in C++ is not defined.

Optionally, the prototype of the open function can be outputted to a header file, which name is given by the -H option.

The binding code generated by tolua uses a set of functions defined in the tolua library. Thus, this library also has to be linked with the application. The file tolua.h is also necessary to compile the generated code.

An application can use tolua object oriented framework (see exported utility functions) without binding any package. In that case, the application must call tolua initialization function (this function is called by any package file initialization function):

int tolua_open (void);

Basic Concepts

Including files

$pfile "include_file"

A package file may also include regular C/C++ header files, using the hfile or cfile directive:

$cfile "example.h"

In which case, tolua will extract the code enclosed between tolua_begin and tolua_end, or or tolua_export for a single line. Consider this C++ header as example:

#ifndef EXAMPLE_H
#define EXAMPLE_H

class Example { // tolua_export

private:

	string name;
	int number;

public:

	void set_number(int number);

	//tolua_begin

	string get_name();
	int get_number();
};
// tolua_end

#endif

In this case, the code that's not supported by tolua (the private part of the class), along with the function set_number is left outside of the package that includes this header.

Finally, lua files can be included on a package file, using $lfile:

$lfile "example.lua"

New on tolua++: an extra way to include source files is available since version 1.0.4 of tolua++, using ifile:

$ifile "filename"

ifile also takes extra optional parameters after the filename, for example:

$ifile "widget.h", GUI
$ifile "vector.h", math, 3d

ifile's default behaviour is to include the whole file, untouched. However, the contents of the file and the extra parameters are put through the include_file_hook function before being included into the package (see Customizing tolua++ for more details).

Basic types

Functions in C/C++ can also manipulate Lua objects explicitly. Thus lua_Object is also considered a basic type. In this case, any Lua value matches it.

New on tolua++: The C++ type string is also considered a basic type, and is passed as a value to lua (using the c_str() method). This feature can be turned off with the command line option -S.

User defined types

For user defined types, constness is preserved. Thus passing a non constant user defined type to a function that expects constant type generates an type mismatching error.

NULL and nil

Typedefs

typedef double real;

Otherwise, real would be interpreted as a user defined type and would not be mapped to Lua numbers.

Including real header files

/* specify the files to be included */

$#include "header1.h"                 // include first header
$#include "header2.h"                 // include second header

Also note that files included with $cfile or $hfile don't need to be included using this method, this is done automatically by tolua.

In the following sections, we describe how to specify the C/C++ code we want to bind to Lua. The formats are simplified valid C/C++ statements.

Binding constants

#define NAME [ VALUE ]

New on tolua++: All other preprocessor directives are ignored.

For enum's, the general format is:

enum {
  NAME1 [ = VALUE1 ] ,
  NAME2 [ = VALUE2 ] ,
  ...
  NAMEn [ = VALUEn ]
};

Binding external variables

[extern] type var;

double v[10];

New on tolua++: External variables can use the tolua_readonly modifier (see Additional Features)

Binding functions

type funcname (type1 par1[, type2 par2[,...typeN parN]]);

Arrays

The arrays must be pre dimensioned. For instance:

void func (double a[3]);

is a valid function declaration for tolua and calling this function from Lua would be done by, for instance:

p = {1.0,1.5,8.6}
func (p)

The array dimension need not be a constant expression; the dimension can also be specified by any expression that can be evaluated in run time. For instance:

void func (int n, int m, double image[n*m]);

is also valid since the expression n*m is valid in the binding function scope. However, be aware that tolua uses dynamic allocation for binding this function, what can degrade the performance.

Despite the dimension specification, it is important to know that all arrays passed to the actual C/C++ function are in the local scope of the binding function. So, if the C/C++ function being called needs to hold the array pointer for later use, the binding code will not work properly.

Overloaded functions

void func (int a);
void func (double a);

represent two different functions in C++, they are the same function for tolua, because both int and double are mapped to the same Lua type: number.

Another tricky situation occurs when expecting pointers. Suppose:

void func (char* s);
void func (void* p);
void func (Object1* ptr);
void func (Object2* prt);

func(nil)

It is important to know that tolua decides which function will be called in run-time, trying to match each provided function. tolua first tries to call the last specified function; if it fails, tolua then tries the previous one. This process is repeated until one function matches the calling code or the first function is reached. For that reason, the mismatching error message, when it occurs, is based on the first function specification. When performance is important, we can specify the most used function as the last one, because it will be tried first.

tolua allows the use of overloaded functions in C, see Renaming for details.

Default parameter values

type funcname (..., typeN-1 parN-1 [= valueN-1], typeN parN [= valueN]);

toLua implements this feature without using any C++ mechanism; so, it can be used also to bind C functions.

We can also specify default values for the elements of an array (there is no way to specify a default value for the array itself, though). For instance:

void func (int a[5]=0);

sets the default element values to zero, thus the function can be called from Lua with an uninitialized table.

For Lua object types (lua_Object), tolua defines a constant that can be used to specify nil as default value:

void func (lua_Object lo = TOLUA_NIL);

New on tolua++: C++ class constructors are valid as default parameters. For example:

void set_color(const Color& color = Color(0,0,0));

Multiple returned values

For instance, consider a C function that swaps two values:

void swap (double* x, double* y);

or

void swap (double& x, double& y);

If such a function is declared in the package file, tolua binds it as a function receiving two numbers as input and returning two numbers. So, a valid Lua code would be:

x,y = swap(x,y)

If the input values are not used, the use of default parameter value allows calling the function from Lua without specifying them:

void getBox (double* xmin=0, double* xmax=0, double* ymin=0, double* ymax=0);

In Lua:

xmin, xmax, ymin, ymax = getBox()

With user defined types, we would have for instance:

void update (Point** p);

or

void update (Point*& p);

Binding struct fields

typedef struct [name] {
   type1 fieldname1;
   type2 fieldname2;
   ...
   typeN fieldnameN;
} typename;

Fields that represent arrays of values can also be mapped:

typedef struct {
  int x[10];
  int y[10];
} Example;
 

Binding classes and methods

Specifying inheritance

class classname : public basename
{

 /* class definition */

};

In this case, the definition of basename needs to appear before classname if the inheritance properties are to be taken advantage of from lua.

Multiple inheritance

For example, consider the following class:

class Slider : public Widget, public Range {
	...
};

An object of type 'Slider' will fully retain its inheritance with Widget, and will contain a 'member' of type Range, which will return the object cast to the correct base type.

For example:

slider = Slider:new()
slider:show() -- a Widget method

slider:set_range(0, 100) -- this won't work, because
                         -- set_range is a method from Range

slider.__Range__:set_range(0, 100) -- this is the correct way

This is an experimental feature.

Specifying exported members and methods

For each bound class, tolua creates a Lua table and stores it at a variable which name is the name of the C++ class. This tables may contain other tables that represent other tables, the way C++ classes may contain other classes and structs. Static exported fields are accessed by indexing this table with the field names (similar to struct fields). Static methods are also called using this table, with a colon. Non static exported fields are accessed by indexing the variable that holds the object. Class methods follow the format of the function declaration showed above. They can be accessed from Lua code using the conventional way Lua uses to call methods, applied of course to a variable that holds the appropriate object or to the class table, for static methods.

There are a few special methods that are also supported by tolua. Constructors are called as static methods, named new, new_local (on tolua++), or calling the class name directly (also on tolua++, see below for the difference betwheen these methods). Destructors are called as a conventional method called delete.

Note that tolua does support overload. This applies even for constructors. Also note that the virtual keyword has no effect in the package file.

The following code exemplifies class definitions that can be interpreted by tolua.

class Point {
   static int n;    // represents the total number of created Points
   static int get_n();    // static method

   double x;        // represents the x coordinate
   double y;        // represents the y coordinate

   static char* className (void);   // returns the name of the class

   Point (void);                          // constructor 1
   Point (double px, double py);          // constructor 2
   ~Point (void);                         // destructor

   Point add (Point& other);              // add points, returning another one
};

class ColorPoint : public Color {
   int red;      // red color component [0 - 255]
   int green;    // green color component [0 - 255]
   int blue;     // blue color component [0 - 255]

   ColorPoint (double px, double py, int r, int g, int b);
};

p1 = Point:new(0.0,1.0)
p2 = ColorPoint:new(1.5,2.2,0,0,255)
print(Point.n)                     -- would print 2
print(Point:get_n())               -- would also print 2
p3 = p1:add(p2)
local p4 = ColorPoint()
print(p3.x,p3.y)                   -- would print 1.5 and 3.2
print(p2.red,p2.green,p2.blue)     -- would print 0, 0, and 255
p1:delete()                        -- call destructor
p2:delete()                        -- call destructor

New on tolua++: Also note that p4 is created by calling the class name directly (ColorPoint()); this has the same effect as calling new_local, which leaves the object to be deleted by the garbaje collector, and it should not be deleted using delete. For each constructor on the pkg, one new, new_local and .call callback for the class is created.

Of course, we need to specify only the methods and members we want to access from Lua. Sometimes, it will be necessary to declare a class with no member or method just for the sake of not breaking a chain of inheritances.

Using Regular functions as class methods

tolua++ (starting from version 1.0.5) uses the keyword tolua_outside to specify regular functions as methods and static methods of a class or struct. For example:

/////////////// position.h:

typedef struct {

	int x;
	int y;
} Position;

Position* position_create();
void position_set(Position* pos, int x, int y);

/////////////// position.pkg:

struct Position {

	int x;
	int y;

	static tolua_outside Position* position_create @ create();
	tolua_outside void position_set @ set(int x, int y);
};

--------------- position.lua

local pos = Position:create()

pos:set(10, 10)

Overloaded operators

operator+   operator-   operator*   operator/ 
operator<   operator>=  operator==  operator[]

As an example, suppose that in the code above, instead of having:

   Point add (Point& other);              // add points, returning another one

   Point operator+ (Point& other);        // add points, returning another one

p3 = p1 + p2

   double& operator[] (int index);

   double operator[] (int index);

Free functions (i.e., not class members) that overload operators are not supported.

Cast operators

/////////////// node.h

// a class that holds a value that can be of type int, double, string or Object*
class Node { // tolua_export

private:
	union {
		int int_value;
		double double_value;
		string string_value;
		Object* object_value;
	};

// tolua_begin
public:

	enum Type {
		T_INT,
		T_DOUBLE,
		T_STRING,
		T_OBJECT,
		T_MAX,
	};

	Type get_type();

	operator int();
	operator double();
	operator string();
	operator Object*();
};
// tolua_end

-- node.lua

local node = list.get_node("some_node") -- returns a Node object

if node.get_type() == Node.T_STRING then

	print("node is "..node[".string"]())

elseif node.get_type() == Node.T_OBJECT then

	local object = node[".Object*"]()
	object:method()
end

Binding Properties

/////////////// label.h

class Label {

public:

	string get_name();
	void set_name(string p_name);

	Widget* get_parent();
};

/////////////// label.pkg
class Label {

	tolua_property string name;

	tolua_readonly tolua_property Widget* parent;
};

--------------- label.lua

local label = Label()

label.name = "hello"
print(label.name)

label.parent:show()

Property types

A property can have differt types, which determine how it's value will be set and retrieved. tolua++ comes with 3 different built-in types:

TOLUA_PROPERTY_TYPE(default); // default type for the 'global' scope

namespace GUI {

	class Point {

		tolua_property int x; // will use get_x/set_x
		tolua_property int y; // will use get_y/set_y
	};

	TOLUA_PROPERTY_TYPE(qt); // changes default type to 'qt' for the rest of the 'GUI' namespace

	class Label {

		tolua_property string name; // will use name/setName
	};
};

class Sprite {

	tolua_property GUI::Point position; // will use get_position/set_position

	tolua_property__overload string name; // will use name/name
};

/////////////// custom.lua

function get_property_methods_hook(ptype, name)

	if ptype == "hungarian_string" then

		return "sGet"..name, "Set"..name
	end

	if ptype == "hungarian_int" then

		return "iGet"..name, "Set"..name
	end
	-- etc
end

/////////////// label.pkg
class Label {

	tolua_property__hungarian_string string Name; // uses 'sGetName' and 'SetName'

	tolua_property__hungarian_int string Type; // uses 'iGetType' and 'SetType'
};

class vector {

	TOLUA_TEMPLATE_BIND(T, int, string, Vector3D, double)

	void clear();
	int size() const;

	const T& operator[](int index) const;
	T& operator[](int index);
	void push_back(T val);

	vector();
	~vector();
};

string_vector = vector_string_:new_local()
string_vector:push_back("hello")
string_vector:push_back("world")
print(string_vector[0].." "..string_vector[1])

class hash_map : public map<K,V> {

	TOLUA_TEMPLATE_BIND(K V, int string, string vector<double>)

	V get_element(K key);
	void set_element(K key, V value);

	hash_map();
	~hash_map();
};

typedef vector VectorInt;

VectorInt variable;

TOLUA_TEMPLATE_BIND((T, int, float)) // to be used inside a real header file
TOLUA_TEMPLATE_BIND("K V", "string string", int double)

$renaming ^_+ @
$renaming hash_map<string,vector<double> > @ StringHash

obj = ClassName:new()

obj.myfield = 1  -- even though "myfield" does not represent a field of ClassName

class Widget {

	tolua_readonly string name;
};

$hfile "node.h"
$#define __operator_arrow operator->()
$#define __get_name get_name()

template class<T>
class Node { // tolua_export

private:
	string name;
	T* value;

public:

	T* operator->() {return value;};
	string get_name() {return name;};

	// tolua_begin

	#if 0
	TOLUA_TEMPLATE_BIND(T, Vector3D)

	tolua_readonly __operator_arrow @ p;
	tolua_readonly __get_name @ name;
	#endif


	Node* next;
	Node* prev;

	void set_name(string p_name) {name = p_name;};

	Node();
};
// tolua_end

node = Node_Vector3D_:new_local()
-- do something with the node here --
print("node name is "..node.name)
print("node value is ".. node.p.x ..", ".. node.p.y ..", ".. node.p.z)

The ability to rename functions as variables might be expanded on future versions.

Defining values on command line

$ tolua++ -E VERSION=5.1 -E HAVE_ZLIB package.pkg > package_bind.cpp

This will add 2 fields to the global table _extra_parameters: "VERSION", with the string value "5.1", and "HAVE_ZLIB" with the boolean value true. For the moment, there is no way to 'use' these values, except in custom scripts defined by the user (see customizing tolua++ for details).

Using C++ typeid

#ifndef Mtolua_typeid
#define Mtolua_typeid(L,TI,T)
#endif
 Mtolua_typeid(tolua_S,typeid(Foo), "Foo");
 Mtolua_typeid(tolua_S,typeid(Bar), "Bar");

Exported utility functions

module tolua
{
 char* tolua_bnd_type @ type (lua_Object lo);
 void tolua_bnd_takeownership @ takeownership (lua_Object lo);
 void tolua_bnd_releaseownership @ releaseownership (lua_Object lo);
 lua_Object tolua_bnd_cast @ cast (lua_Object lo, char* type);
 void tolua_bnd_inherit @ inherit (lua_Object table, lua_Object instance);

/* for lua 5.1 */
 void tolua_bnd_setpeer @ setpeer (lua_Object object, lua_Object peer_table);
 void tolua_bnd_getpeer @ getpeer (lua_Object object);
}

tolua.type (var)

tolua.takeownership (var)

tolua.releaseownership (var)

tolua.cast (var, type)

tolua.inherit (table, var)

void set_parent(Widget* p_parent);

A lua object could be used like this:

local w = Widget()
local lua_widget = {}
tolua.inherit(lua_widget, w)

set_parent(lua_widget);

lua_widget.show = Widget.show

lua_widget:show() -- this will call the 'show' method from 'Widget', using the lua
                  -- table as 'self'. Since lua_widget inherits from a widget instance,
                  -- tolua++ will recognise 'self' as a 'Widget', and call the method

Of course a better way would be to add a __index metamethod for the lua object.

Similarily, to implement virtual functions, you'll need to create a c++ object that inherits from the desired type, implement its virtual functions, and use that to inherit from lua. The object would have a reference to the lua table, and call its methods from the c++ virtual methods.

Note: the current implementation (as of version 1.0.6) stores the C instance inside the lua table on the field ".c_instance", and looks that up when necesary. This might change in the future, so it is recommended to use an alternative way to store the C instance to use with your own object system.

tolua.setpeer (object, peer_table) (lua 5.1 only)

-- a 'LuaWidget' class
LuaWidget = {}
LuaWidget.__index = LuaWidget

function LuaWidget:add_button(caption)

	-- add a button to our widget here. 'self' will be the userdata Widget
end


local w = Widget()
local t = {}
setmetatable(t, LuaWidget) -- make 't' an instance of LuaWidget

tolua.setpeer(w, t) -- make 't' the peer table of 'w'

set_parent(w) -- we use 'w' as the object now

w:show() -- a method from 'Widget'
w:add_button("Quit") -- a method from LuaWidget (but we still use 'w' to call it)

tolua.getpeer (object) (lua 5.1 only)

Embedded Lua code

$[

embedded Lua code
...

$]

As an example consider the following .pkg excerpt:

/* Bind a Point class */
class Point
{
 Point (int x, int y);
 ~Point ();
 void print ();
 ...
} CPoint;

$[

-- Create a Point constructor
function Point (self)
 local cobj = CPoint:new(self.x or 0, self.y or 0)
 tolua.takeownership(cobj)
 return cobj
end

$]

Binding such a code would allow us to write the following Lua code:

p = Point{ x=2, y=3 }
p:print()
...
 

Customizing tolua++

tolua++ calls empty functions at specific points of its execution. This functions can be redefined on a separate lua file (and included using the -L command line option) and be used to control the way tolua++ behaves. This is the list of functions (taken from basic.lua on the tolua++ source):

-- called right after processing the $[ichl]file directives,
-- right before processing anything else
-- takes the package object as the parameter
function preprocess_hook(p)
	-- p.code has all the input code from the pkg
end


-- called for every $ifile directive
-- takes a table with a string called 'code' inside, the filename, and any extra arguments
-- passed to $ifile. no return value
function include_file_hook(t, filename, ...)

end

-- called after processing anything that's not code (like '$renaming', comments, etc)
-- and right before parsing the actual code.
-- takes the Package object with all the code on the 'code' key. no return value
function preparse_hook(package)

end


-- called after writing all the output.
-- takes the Package object
function post_output_hook(package)

end

-- called at the beginning of the main parser function, with the code being parsed as a parameter
-- it can return nil if nothing was foind, or the contents of 'code', modified by the function
-- Usually a parser hook will search the beginning of the string for a token, and if it finds
-- anything, return the string without that token (after doing whatever it has to do with the token).
function parser_hook(code)

end


-- called from classFunction:supcode, before the call to the function is output
-- the classFunction object is passed.
function pre_call_hook(f)

end

-- called from classFunction:supcode, after the call to the function is output
-- the classFunction object is passed.
function post_call_hook(f)

end

-- called before the register code is output
function pre_register_hook(package)

end

-- called to output an error message
function output_error_hook(...)
	return string.format(...)
end

Handling custom types

A number of arrays found in basic.lua are used to specify these functions:

-- for specific types
_push_functions = {}
_is_functions = {}
_to_functions = {}

-- for base types
_base_push_functions = {}
_base_is_functions = {}
_base_to_functions = {}

_is_functions['Vector3'] = 'custom_is_vector3' -- checks for a 3d vector
                                               -- (either userdata, or a table with 3 values)
_to_functions['Vector3'] = 'custom_to_vector3' -- convertes the eventual table to a Vector3

_base_push_functions['Widget'] = 'custom_push_widget' -- pushes anything that inherits from Widget

Access

Another 'interesting' function is extract_code, defined on basic.lua, which extracs the code from files included with $cfile and $hfile (by looking for tolua_begin/end and tolua_export).

Compatibility with older versions.

tolua++ <1.0.90

Version 1.0.90 of tolua++ introduces 2 small API changes the might be incompatible with older versions on some cases:

TEMPLATE_BIND

TEMPLATE_BIND is deprecated. Use TOLUA_TEMPLATE_BIND instead. Also, when declaring a template, the TOLUA_TEMPLATE_BIND statement has to be the first thing inside the class declaration, otherwise it will be ignored. This fixes a possible problem with nested template declarations.

Retrieving Objects

When passing a full userdata to a function that accepts light userdata parameters (void*), the tolua++ library function tolua_touserdata will detect the full userdata and dereference the void** pointer if necesary. This is a change on the function's behaviour (which used to return the pointer as-is). This allows us to pass pointers to objects to a function that accepts void* pointers. Note that this was a problem when switching from toLua version 4 to version 5 (and tolua++ versions < 1.0.90).

toLua 4

Retrieving Objects

Users switching from tolua v4 should know that tolua++ stores the objects as void** on Lua, so when retrieving an object from the luastate using lua_touserdata, the pointer should be dereferenced. The library function tolua_tousertype should work as expected. Example:

lua_pushglobal(lua_state, "get_Object");
lua_call(lua_state, 0, 1);  // calling a function that returns an Object

Object *new_object = (Object*)(*lua_touserdata(lua_state, -1));
or
Object *new_object = (Object*)tolua_tousertype(lua_state, -1, NULL);

tolua++ binds the c++ type std::string as a basic type, passing it to Lua as a regular string (using the method c_str()). This feature can be turned off with the command line option -S.

Operators

The list of supported operators has changed, see Binding classes and methods for more information.

toLua 5

Class destructors.

With every class constructor, tolua++ exports a 'local' constructor, to create an instance of the class that is owned by the lua state. To implement this, tolua++ will also export a function that will delete the class. There are 2 options to prevent this:

Using the -D command line option will turn this off completely. Destructor functions will only be exported when a destructor for the class is explicitly declared, or when there is a function or method that returns an object of the type by value (this is compatible with tolua's behaviour).

Using the TOLUA_PROTECTED_DESTRUCTOR directive inside the class declaration, to specify that the class has a private or protected destructor. In this case, no destructor will be exported for that class.

operator[] index

Users switching from tolua v5 should know that tolua 5 substracts 1 from the index on operator[] functions, for compatibility with lua's method for indexing arrays (1 is the first element). This feature is turned off by default on tolua++ (making it compatible with tolua 4). It can be turned back on with the command line option -1

C++ Strings

(see c++ strings on tolua 4 below)

Changes since v. 3.0

• Support for binding arrays as variables and struct/class fields;
• Support for embedding Lua code into the generated binding code;
• New utility functions: cast and takeownership;
• Option to create the corresponding header file of the binding code;
• New "close" package function;
• Fixed bug on cloning objects in C++;
• Fixed bug on enum and struct parsing;

Changes since v. 2.0

• There is a new executable parser;
• Support for multiple Lua states is provided;
• Support for module definition is provided;
• Global variables is now directly bound to Lua global variables;
• Constness of user defined types is preserved in Lua;
• Support for multiple returned values from C/C++ is provided (simulating parameters passed by reference);
• Constants, variables, and functions bound to Lua can have different names from their C/C++ counterparts;
• Object-oriented framework (and other utility functions) used in tolua is now exported for Lua programmers;

Incompatibilities

Lua code based on tolua v2.* should run with no change on tolua v3.0. Although, it may be necessary to change the .pkg file in order to get the same behavior. The following incompatibilities exist:
• Parameters defined as pointer to basic types are no longer converted to arrays of dimension one; they are now considered parameters passed by reference.
• Automatic initialization for C++ code must be explicitly requested when using the new parser;
• Global variables are no longer mapped to a table; the definition of a module including the global variables may be used to simulate the old behavior;
• The initialization function is no longer toLua_package_open but tolua_package_open, without the capital letter (sorry!).

Changes since v. 1.*

• The binding code should run much faster;
• The cleaned header file extension should now be .pkg instead of .L;
• Type modifiers is now accepted (though the current version ignores const's);
• Returning object by value is accepted and memory allocation is controlled by Lua garbage collection;
• Overloaded functions/methods are accepted;
• Parameters with default values are accepted;
• Some overloaded operators are automatically bound.

Credits

While working at NGD Studios, Ariel Manzur made some changes to tolua4 for their game engine. After the release of tolua5, having left NGD, enough changes were made to tolua to justify a separate release (with Waldemar's blessing :-)
 

Availability