mirror of
https://github.com/LuaJIT/LuaJIT.git
synced 2025-02-07 15:14:08 +00:00
Misc. updates to docs.
This commit is contained in:
parent
6691e72eb8
commit
f182559069
@ -80,11 +80,10 @@ applications using the LuaJIT FFI for developers with a C or C++
|
||||
background.
|
||||
</p>
|
||||
<p class="indent" style="color: #c00000;">
|
||||
Please note: this is an early public release of the FFI library. This
|
||||
does not comprise the final specification for the FFI semantics, yet.
|
||||
Some of the semantics may need to be changed, based on feedback from
|
||||
developers. Please <a href="contact.html">report</a> any problems you
|
||||
may encounter or any improvements you'd like to see — thank you!
|
||||
Please note: this doesn't comprise the final specification for the FFI
|
||||
semantics, yet. Some semantics may need to be changed, based on your
|
||||
feedback. Please <a href="contact.html">report</a> any problems you may
|
||||
encounter or any improvements you'd like to see — thank you!
|
||||
</p>
|
||||
|
||||
<h2 id="clang">C Language Support</h2>
|
||||
@ -990,8 +989,10 @@ value.</li>
|
||||
<tt>__index</tt> tables.</li>
|
||||
<li>Accesses to external variables in C library namespaces.</li>
|
||||
<li><tt>tostring()</tt> for cdata types.</li>
|
||||
<li>The following <a href="ext_ffi_api.html">ffi.* API</a> functions:
|
||||
<tt>ffi.sizeof()</tt>, <tt>ffi.alignof()</tt>, <tt>ffi.offsetof()</tt>.
|
||||
<li>Calls to the following <a href="ext_ffi_api.html">ffi.* API</a>
|
||||
functions: <tt>cdef</tt>, <tt>load</tt>, <tt>typeof</tt>,
|
||||
<tt>metatype</tt>, <tt>gc</tt>, <tt>sizeof</tt>, <tt>alignof</tt>,
|
||||
<tt>offsetof</tt>, <tt>errno</tt>.</li>
|
||||
</ul>
|
||||
<p>
|
||||
Other missing features:
|
||||
@ -1000,7 +1001,6 @@ Other missing features:
|
||||
<li>Bit operations for 64 bit types.</li>
|
||||
<li>Arithmetic for <tt>complex</tt> numbers.</li>
|
||||
<li>Callbacks from C code to Lua functions.</li>
|
||||
<li>Atomic handling of <tt>errno</tt>.</li>
|
||||
<li>Passing structs by value to vararg C functions.</li>
|
||||
<li><a href="extensions.html#exceptions">C++ exception interoperability</a>
|
||||
does not extend to C functions called via the FFI.</li>
|
||||
|
@ -367,6 +367,13 @@ make HOST_CC="gcc -m32" CROSS=$NDKP TARGET_FLAGS="$NDKF" TARGET=arm
|
||||
You can cross-compile for <b id="ios">iOS 3.0+</b> (iPhone/iPad) using the <a href="http://developer.apple.com/devcenter/ios/index.action"><span class="ext">»</span> iOS SDK</a>.
|
||||
The environment variables need to match the iOS SDK version:
|
||||
</p>
|
||||
<p style="font-size: 8pt;">
|
||||
Note: <b>the JIT compiler is disabled for iOS</b>, because regular iOS Apps
|
||||
are not allowed to generate code at runtime. You'll only get the performance
|
||||
of the LuaJIT interpreter on iOS. This is still faster than plain Lua, but
|
||||
much slower than the JIT compiler. Please complain to Apple, not me.
|
||||
Or use Android. :-p
|
||||
</p>
|
||||
<pre class="code">
|
||||
ISDK=/Developer/Platforms/iPhoneOS.platform/Developer
|
||||
ISDKVER=iPhoneOS4.3.sdk
|
||||
|
@ -91,7 +91,7 @@ LuaJIT has been successfully used as a <b>scripting middleware</b> in
|
||||
games, 3D modellers, numerical simulations, trading platforms and many
|
||||
other specialty applications. It combines high flexibility with high
|
||||
performance and an unmatched <b>low memory footprint</b>: less than
|
||||
<b>120K</b> for the VM plus less than <b>80K</b> for the JIT compiler (on x86).
|
||||
<b>125K</b> for the VM plus less than <b>85K</b> for the JIT compiler (on x86).
|
||||
</p>
|
||||
<p>
|
||||
LuaJIT has been in continuous development since 2005. It's widely
|
||||
|
@ -81,7 +81,7 @@ This is a list of the things you should know about the LuaJIT 2.0 beta test:
|
||||
</p>
|
||||
<ul>
|
||||
<li>
|
||||
Obviously there will be many <b>bugs</b> in a VM which has been
|
||||
Obviously there will be some <b>bugs</b> in a VM which has been
|
||||
rewritten from the ground up. Please report your findings together with
|
||||
the circumstances needed to reproduce the bug. If possible, reduce the
|
||||
problem down to a simple test case.<br>
|
||||
|
Loading…
Reference in New Issue
Block a user