[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: 5.2-beta changes as an annotated reference manual
- From: HyperHacker <hyperhacker@...>
- Date: Sat, 25 Jun 2011 17:48:31 -0600
On Sat, Jun 25, 2011 at 16:47, Farmbuyer <farmbuyer@gmail.com> wrote:
> On Sat, Jun 25, 2011 at 11:38 AM, Peter Cawley <lua@corsix.org> wrote:
>>
>> http://www.corsix.org/lua/5.2-beta-annotated/manual.html
>
> That is incredibly useful, thank you!
>
>
Yes, very helpful for understanding all the changes from 5.1 to 5.2.
I found some errors, that are probably in the original document as well:
luaL_checkversion
Checks whether the core running the call, the core that created the
Lua state, and the *code* making the call are all using the same
version of Lua.
-Should be "core"?
luaL_fileresult has an extra line break in its prototype.
luaL_getsubtable
Ensures that the value t[fname], where t is the value at the valid
index idx, is a table, and pushes that table onto the stack. Returns
true if it finds a previous table there and false if it creates a new
table.
-Does that mean it overwrites the existing value of fname?
Can L and L1 be the same state in luaL_traceback?
Section 6.5 states: Currently, all functions in the table library,
except table.pack, work on lists. A list here means a proper sequence
or a table with a __len metamethod (see §3.4.6). In particular, all
functions ignore non-numeric keys in lists given as arguments.
-Does this mean table.unpack({'a', 'b', nil, 'd'}, 1, 4) won't work as expected?
io.lines: "...works like file:lines(···) over the oppened file..."
should be "opened".
--
Sent from my toaster.