aboutsummaryrefslogtreecommitdiff
path: root/doc/status.html
diff options
context:
space:
mode:
authorMike Pall <mike>2009-12-08 19:49:20 +0100
committerMike Pall <mike>2009-12-08 19:49:20 +0100
commit1d1fed48a002dfc0919135911057ebc255a53e0a (patch)
treec5c6643908374bb8f02f4c7691332d32f6645986 /doc/status.html
parent55b16959717084884fd4a0cbae6d19e3786c20c7 (diff)
downloadluajit-1d1fed48a002dfc0919135911057ebc255a53e0a.tar.gz
luajit-1d1fed48a002dfc0919135911057ebc255a53e0a.tar.bz2
luajit-1d1fed48a002dfc0919135911057ebc255a53e0a.zip
RELEASE LuaJIT-2.0.0-beta2v2.0.0-beta2
Diffstat (limited to 'doc/status.html')
-rw-r--r--doc/status.html21
1 files changed, 18 insertions, 3 deletions
diff --git a/doc/status.html b/doc/status.html
index 23c14c76..aa4a1e26 100644
--- a/doc/status.html
+++ b/doc/status.html
@@ -90,7 +90,22 @@ known incompatibilities with standard Lua:
90<ul> 90<ul>
91<li> 91<li>
92The Lua <b>debug API</b> is missing a couple of features (call/return 92The Lua <b>debug API</b> is missing a couple of features (call/return
93hooks) and shows slightly different behavior (no per-coroutine hooks). 93hooks) and shows slightly different behavior (no per-coroutine hooks,
94no tail call counting).
95</li>
96<li>
97<b>Bytecode</b> currently cannot be loaded or dumped. Note that
98the bytecode format differs from Lua&nbsp;5.1 &mdash; loading foreign
99bytecode is not supported at all.
100</li>
101<li>
102Some of the <b>configuration options</b> of Lua&nbsp;5.1 are not supported:
103<ul>
104<li>The <b>number type</b> cannot be changed (it's always a <tt>double</tt>).</li>
105<li>The stand-alone executable cannot be linked with <b>readline</b>
106to enable line editing. It's planned to add support for loading it
107on-demand.</li>
108</ul>
94</li> 109</li>
95<li> 110<li>
96Most other issues you're likely to find (e.g. with the existing test 111Most other issues you're likely to find (e.g. with the existing test
@@ -105,7 +120,7 @@ demonstrable need is shown.
105<li> 120<li>
106The <b>JIT compiler</b> is not complete (yet) and falls back to the 121The <b>JIT compiler</b> is not complete (yet) and falls back to the
107interpreter in some cases. All of this works transparently, so unless 122interpreter in some cases. All of this works transparently, so unless
108you use -jv, you'll probably never notice (the interpreter is quite 123you use <tt>-jv</tt>, you'll probably never notice (the interpreter is quite
109fast, too). Here are the known issues: 124fast, too). Here are the known issues:
110<ul> 125<ul>
111<li> 126<li>
@@ -119,7 +134,7 @@ effort.
119</li> 134</li>
120<li> 135<li>
121<b>Recursion</b> is not traced yet. Often no trace will be generated at 136<b>Recursion</b> is not traced yet. Often no trace will be generated at
122all or some unroll limit will catch it and aborts the trace. 137all or some unroll limit will catch it and abort the trace.
123</li> 138</li>
124<li> 139<li>
125The trace compiler currently does not back off specialization for 140The trace compiler currently does not back off specialization for