lua/manual, branch v5.4-betaA mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.4-beta2019-10-08T13:34:43+00:00Improvements in the manual around metamethods2019-10-08T13:34:43+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-10-08T13:34:43+00:00urn:sha1:6c0e44464b9eef4be42e2c8181aabfb3301617ad'setCstacklimit' renamed to 'setcstacklimit'2019-09-24T17:31:06+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-09-24T17:31:06+00:00urn:sha1:03cde80b58ea7f112f1b7a35c037893093b59f2e
Function names in the API use only lowercase letters.
Default for warnings changed to "off"2019-08-20T16:42:26+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-08-20T16:42:26+00:00urn:sha1:be78aeae4c429d7d68af3a3e1b0cf8e52fcff160
Warnings are mostly a tool to help developers (e.g., by showing hidden
error messages); regular users usually don't need to see them.
Manual corrected with the new syntax for attributes2019-08-16T19:11:21+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-08-16T19:11:21+00:00urn:sha1:45948e7e55c753cf0e370b251ac1d4e7f3aabedd
Commit 0d529138042, with the change in the syntax of attributes,
did not update the manual accordingly.
Added macro 'luaL_pushfail'2019-08-16T17:58:02+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-08-16T17:58:02+00:00urn:sha1:b96b0b5abbf40cbdbed7952bf35a5a27ddf75928
The macro 'luaL_pushfail' documents all places in the standard libraries
that return nil to signal some kind of failure. It is defined as
'lua_pushnil'. The manual also got a notation (@fail) to document those
returns. The tests were changed to be agnostic regarding whether 'fail'
is 'nil' or 'false'.
Supressed errors in '__close' generate warnings2019-08-16T12:51:54+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-08-16T12:51:54+00:00urn:sha1:ca13be9af784b7288d3a07d9b5bccb329086e885Added control messages to warnings2019-08-15T16:44:36+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-08-15T16:44:36+00:00urn:sha1:a1d8eb27431c02c4529be1efd92143ad65434f3a
Added the concept of control messages to the warning system, plus the
implementation of the controls "@on"/"@off" to turn warnings on/off.
Moreover, the warning system in the test library adds some other
controls to ease the test of warnings.
Detail in the manual (method 'file:setvbuf')2019-08-12T14:26:08+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-08-12T14:26:08+00:00urn:sha1:09b4e527a008687a2fd90202b5e7b2f175d8ebed
ANSI C is vague about 'setvbuf'; most details are implementation
defined. So, the manual cannot give any guaranties, either.
Correction in the documentation of 'io.lines'2019-07-31T14:41:59+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-07-31T14:41:59+00:00urn:sha1:223bb04090344b1972dc2a7910a54b46210f0d40
The loop does not end on end of file, but when the iterator function
fails to read a value. (In particular, the format "a" never fails,
so a loop with 'io.lines(fname, "a")' never ends.)
To-be-closed variables must be closed on initialization2019-07-31T13:43:51+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-07-31T13:43:51+00:00urn:sha1:f645d3157372c73573dff221c5b26691cb0e7d56
When initializing a to-be-closed variable, check whether it has a
'__close' metamethod (or is a false value) and raise an error if
if it hasn't. This produces more accurate error messages. (The
check before closing still need to be done: in the C API, the value
is not constant; and the object may lose its '__close' metamethod
during the block.)