aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/LuaSL/testLua/yueliang-0.4.1/orig-5.0.3/README
diff options
context:
space:
mode:
Diffstat (limited to 'LuaSL/testLua/yueliang-0.4.1/orig-5.0.3/README')
-rw-r--r--LuaSL/testLua/yueliang-0.4.1/orig-5.0.3/README51
1 files changed, 0 insertions, 51 deletions
diff --git a/LuaSL/testLua/yueliang-0.4.1/orig-5.0.3/README b/LuaSL/testLua/yueliang-0.4.1/orig-5.0.3/README
deleted file mode 100644
index e64bf50..0000000
--- a/LuaSL/testLua/yueliang-0.4.1/orig-5.0.3/README
+++ /dev/null
@@ -1,51 +0,0 @@
1orig-5.0.3
2
3This is a straightforward port of the Lua 5.0.3 front end (lexical
4analyzer, parser, code generator, binary chunk dumper.)
5
6The front end files are:
7
8 lopcodes.lua opcode definition
9 lzio.lua input streams
10 llex.lua lexical analyzer
11 lparser.lua parser
12 lcode.lua code generator
13 ldump.lua binary chunk dumper
14
15Status: operational, passes all current tests (non-exhaustive)
16
17Major test scripts are:
18
19 test/test_llex.lua exercises test cases
20 test/test_lparser2.lua exercises test cases
21
22luac.lua is a clone of Lua 5.0.3's luac.lua, except that it generates a
23binary chunk using Yueliang's front end implementation.
24
25Note that performance is not a consideration. The code tries to stay
26faithful to its C roots, so that if you were to do anything using this
27codebase, backporting the changes to C will be easy. As such, this
28codebase is meant for learning or prototyping purposes.
29
30Many parameters are unused, because call arguments are retained as far
31as possible. Changes and deletions are described wherever possible, but
32documentation of changes is not comprehensive.
33
34These files will stay faithful to the equivalent C files or modules in
35Lua 5.0.3. For rewrites or new features, a new directory will be created
36and a different set of files maintained. For Lua 5.1, a new directory
37will be created.
38
39The test directory has several primitive test scripts. Much better
40testing is planned. Eventually, the codebase will be validated using
41automated tests, so that any changes that breaks the system can be
42caught easily.
43
44The tools directory has a call graph generator, showing what gets
45called. Specific modules and functions can be monitored, and some
46parameters and return values are shown. This is a demonstration of the
47flexibility and ease of manipulation of using a relatively inefficient
48global table scheme.
49
50For Lua 5.0.2, see Yueliang 0.1.3, which was the last release of Lua
515.0.2 material.