yuin
1dc5a40912
revert files.lua
|
před 6 roky | |
|---|---|---|
| .. | ||
| libs | před 9 roky | |
| README | před 9 roky | |
| all.lua | před 9 roky | |
| api.lua | před 9 roky | |
| attrib.lua | před 9 roky | |
| big.lua | před 9 roky | |
| calls.lua | před 9 roky | |
| checktable.lua | před 9 roky | |
| closure.lua | před 9 roky | |
| code.lua | před 9 roky | |
| constructs.lua | před 9 roky | |
| db.lua | před 9 roky | |
| errors.lua | před 9 roky | |
| events.lua | před 9 roky | |
| files.lua | před 6 roky | |
| gc.lua | před 9 roky | |
| literals.lua | před 9 roky | |
| locals.lua | před 9 roky | |
| main.lua | před 9 roky | |
| math.lua | před 7 roky | |
| nextvar.lua | před 9 roky | |
| pm.lua | před 9 roky | |
| sort.lua | před 9 roky | |
| strings.lua | před 9 roky | |
| vararg.lua | před 9 roky | |
| verybig.lua | před 9 roky | |
README
This tarball contains the official test scripts for Lua 5.1.
Unlike Lua itself, these tests do not aim portability, small footprint,
or easy of use. (Their main goal is to try to crash Lua.) They are not
intended for general use. You are wellcome to use them, but expect to
have to "dirt your hands".
The tarball should expand in the following contents:
- several .lua scripts with the tests
- a main "all.lua" Lua script that invokes all the other scripts
- a subdirectory "libs" with an empty subdirectory "libs/P1",
to be used by the scripts
- a subdirectory "etc" with some extra files
To run the tests, do as follows:
- go to the test directory
- set LUA_PATH to "?;./?.lua" (or, better yet, set LUA_PATH to "./?.lua;;"
and LUA_INIT to "package.path = '?;'..package.path")
- run "lua all.lua"
--------------------------------------------
Internal tests
--------------------------------------------
Some tests need a special library, "testC", that gives access to
several internal structures in Lua.
This library is only available when Lua is compiled in debug mode.
The scripts automatically detect its absence and skip those tests.
If you want to run these tests, move etc/ltests.c and etc/ltests.h to
the directory with the source Lua files, and recompile Lua with
the option -DLUA_USER_H='"ltests.h"' (or its equivalent to define
LUA_USER_H as the string "ltests.h", including the quotes). This
option not only adds the testC library, but it adds several other
internal tests as well. After the recompilation, run the tests
as before.
Unlike Lua itself, these tests do not aim portability, small footprint,
or easy of use. (Their main goal is to try to crash Lua.) They are not
intended for general use. You are wellcome to use them, but expect to
have to "dirt your hands".
The tarball should expand in the following contents:
- several .lua scripts with the tests
- a main "all.lua" Lua script that invokes all the other scripts
- a subdirectory "libs" with an empty subdirectory "libs/P1",
to be used by the scripts
- a subdirectory "etc" with some extra files
To run the tests, do as follows:
- go to the test directory
- set LUA_PATH to "?;./?.lua" (or, better yet, set LUA_PATH to "./?.lua;;"
and LUA_INIT to "package.path = '?;'..package.path")
- run "lua all.lua"
--------------------------------------------
Internal tests
--------------------------------------------
Some tests need a special library, "testC", that gives access to
several internal structures in Lua.
This library is only available when Lua is compiled in debug mode.
The scripts automatically detect its absence and skip those tests.
If you want to run these tests, move etc/ltests.c and etc/ltests.h to
the directory with the source Lua files, and recompile Lua with
the option -DLUA_USER_H='"ltests.h"' (or its equivalent to define
LUA_USER_H as the string "ltests.h", including the quotes). This
option not only adds the testC library, but it adds several other
internal tests as well. After the recompilation, run the tests
as before.