4 – The Application Program Interface

This section describes the C API for Lua, that is, the set of C functions available to the host program to communicate with Lua. All API functions and related types and constants are declared in the header file lua.h.

Even when we use the term "function", any facility in the API may be provided as a macro instead. Except where stated otherwise, all such macros use each of their arguments exactly once (except for the first argument, which is always a Lua state), and so do not generate any hidden side-effects.

As in most C libraries, the Lua API functions do not check their arguments for validity or consistency. However, you can change this behavior by compiling Lua with the macro LUA_USE_APICHECK defined.

The Lua library is fully reentrant: it has no global variables. It keeps all information it needs in a dynamic structure, called the Lua state.

Each Lua state has one or more threads, which correspond to independent, cooperative lines of execution. The type lua_State (despite its name) refers to a thread. (Indirectly, through the thread, it also refers to the Lua state associated to the thread.)

A pointer to a thread must be passed as the first argument to every function in the library, except to lua_newstate, which creates a Lua state from scratch and returns a pointer to the main thread in the new state.

lua_pcall
  • References/Lua/Lua/API/Functions and Types

lua_pcall[-(nargs + 1), +(nresults|1), –] int lua_pcall (lua_State *L, int nargs, int nresults, int msgh);

2025-01-10 15:47:30
lua_tonumberx
  • References/Lua/Lua/API/Functions and Types

lua_tonumberx[-0, +0, –] lua_Number lua_tonumberx (lua_State *L, int index, int *isnum); Converts the Lua

2025-01-10 15:47:30
lua_callk
  • References/Lua/Lua/API/Functions and Types

lua_callk[-(nargs + 1), +nresults, e] void lua_callk (lua_State *L, int nargs,

2025-01-10 15:47:30
lua_CFunction
  • References/Lua/Lua/API/Functions and Types

lua_CFunction typedef int (*lua_CFunction) (lua_State *L); Type for C functions. In order to communicate properly with Lua

2025-01-10 15:47:30
lua_getlocal
  • References/Lua/Lua/API/The Debug Interface

lua_getlocal[-0, +(0|1), –] const char *lua_getlocal (lua_State *L, const lua_Debug *ar, int n); Gets information

2025-01-10 15:47:30
lua_Alloc
  • References/Lua/Lua/API/Functions and Types

lua_Alloc typedef void * (*lua_Alloc) (void *ud, void *ptr, size_t osize,

2025-01-10 15:47:30
lua_getfield
  • References/Lua/Lua/API/Functions and Types

lua_getfield[-0, +1, e] int lua_getfield (lua_State *L, int index, const char *k); Pushes onto

2025-01-10 15:47:30
lua_isuserdata
  • References/Lua/Lua/API/Functions and Types

lua_isuserdata[-0, +0, –] int lua_isuserdata (lua_State *L, int index); Returns 1 if the value at the given

2025-01-10 15:47:30
lua_Debug
  • References/Lua/Lua/API/The Debug Interface

lua_Debug typedef struct lua_Debug { int event; const char *name; /* (n) */ const char *namewhat; /* (n) */ const char

2025-01-10 15:47:30
lua_load
  • References/Lua/Lua/API/Functions and Types

lua_load[-0, +1, –] int lua_load (lua_State *L, lua_Reader reader, void *data,

2025-01-10 15:47:30