diff --git a/README.html b/README.html index 0fdd7949..1b6398c4 100644 --- a/README.html +++ b/README.html @@ -17,7 +17,7 @@ Getting Started with LuaJ -James Roseborough, Ian Farmer, Version 2.0-alpha1 +James Roseborough, Ian Farmer, Version 2.0-beta1
Copyright © 2009-2010 Luaj.org. @@ -44,17 +44,17 @@ Freely available under the terms of the
-This is an alpha release for a luaj 2.0. The most recent stable release is 1.0.3 +This is a beta release for a luaj 2.0. The most recent stable release is 1.0.3
- java -cp lib/luaj-jse-2.0-alpha1.jar lua examples/lua/hello.lua + java -cp lib/luaj-jse-2.0-beta1.jar lua examples/lua/hello.lua
@@ -92,8 +93,8 @@ You should see the following output: From the main distribution directory line type:
- java -cp lib/luaj-jse-2.0-alpha1.jar luac examples/lua/hello.lua - java -cp lib/luaj-jse-2.0-alpha1.jar lua luac.out + java -cp lib/luaj-jse-2.0-beta1.jar luac examples/lua/hello.lua + java -cp lib/luaj-jse-2.0-beta1.jar lua luac.out
@@ -106,13 +107,14 @@ Luaj can compile to lua bytecode if the bcel library is on the class path. From
ant bcel-lib - java -cp lib/luaj-jse-2.0-alpha1.jar;lib/bcel-5.2.jar luajc -s examples/lua -d . hello.lua - java -cp lib/luaj-jse-2.0-alpha1.jar;. lua -l hello + java -cp "lib/luaj-jse-2.0-beta1.jar;lib/bcel-5.2.jar" luajc -s examples/lua -d . hello.lua + java -cp "lib/luaj-jse-2.0-beta1.jar;." lua -l hello
The output hello.class is Java bytecode, should run and produce the same result. -There is no runtime dependency on the bcel library, but the compiled classes must be in the class path. +There is no runtime dependency on the bcel library, +but the compiled classes must be in the class path at runtime.
@@ -138,7 +140,7 @@ A simple example may be found in
-You must include the library lib/luaj-jse-2.0-alpha1.jar in your class path. +You must include the library lib/luaj-jse-2.0-beta1.jar in your class path.
-You must include the library lib/luaj-jme-2.0-alpha1.jar in your midlet jar. +You must include the library lib/luaj-jme-2.0-beta1.jar in your midlet jar.
An ant script to build and run the midlet is in @@ -226,7 +228,7 @@ The standard use of JSR-233 scripting engines may be used: All standard aspects of script engines including compiled statements should be supported.
-You must include the library lib/luaj-jse-2.0-alpha1.jar in your class path. +You must include the library lib/luaj-jse-2.0-beta1.jar in your class path.
A working example may be found in @@ -264,9 +266,8 @@ Libraries are coded to closely match the behavior specified in See standard lua documentation for details on the library API's
-The following libraries are loaded in py both JsePlatform.standardGlobals() and JmePlatform.standardGlobals(): -
- base +The following libraries are loaded by both JsePlatform.standardGlobals() and JmePlatform.standardGlobals(): +base coroutine io math @@ -278,14 +279,12 @@ The following libraries are loaded in py both JsePlatform.standardGlobals()<The JsePlatform.standardGlobals() globals also include: -
- luajava +luajavaThe JsePlatform.debugGlobals() and JsePlatform.debugGlobals() functions produce globals that include: -
- debug +debugI/O Library
@@ -352,7 +351,7 @@ The following lua script will open a swiing frame on Java SE:See a longer sample in src/test/res/swingapp.lua for details, or try running it using:
- java -cp lib/luaj-jse-2.0-alpha1.jar lua src/test/res/swingapp.lua + java -cp lib/luaj-jse-2.0-beta1.jar lua src/test/res/swingapp.lua@@ -418,17 +417,23 @@ and LuaForge:
Main Changes by Version
-
2.0-alpha1 -
- All basic bunit tests pass. +
2.0-beta1 +
- All basic unit tests pass.
- Initial port of all libraries has been done. -
- Compile-to-Java based on bcel 5.2. +
- Compile-to-Java based on bcel 5.2 working for unit tests.
Known Issues
-
diff --git a/version.properties b/version.properties index 6e50d45e..f0f9840a 100644 --- a/version.properties +++ b/version.properties @@ -1,2 +1,2 @@ # on the way to version 2.0 -version: 2.0-alpha1 +version: 2.0-beta1- module() and setfenv() don't work with compiled code +
- module() and setfenv() don't work with closures in compiled chunks
- debug code may not be removed by obfuscators -
- not all luajava bugfixes have been ported over +
- lua-to-java bytecode generation can produce incorrect results +
- weak tables may not release items in all cases +
- tail calls may not work as expected in some cases +
- tail calls are not tracked in debug information +
- using both version 1 and version 2 libraries together in the same java vm has not been tested. +
- design of default file loading behavior may change. +
- likely to make changes to support the lua 5.2 API once it is finalized.