lua/testes, branch v5.4-alpha

Multiple errors in '__toclose' report the first one

2019-06-05T16:16:25+00:00

When there are multiple errors when closing objects, the error reported by the protected call is the first one, for two reasons: First, other errors may be caused by this one; second, the first error is handled in the original execution context, and therefore has the full traceback.

Function 'warn' is vararg

2019-06-04T14:22:21+00:00

Instead of a 'tocont' flag, the function 'warn' in Lua now receives all message pieces as multiple arguments in a single call. Besides being simpler to use, this implementation ensures that Lua code cannot create unfinished warnings.

'coroutine.kill' renamed 'coroutine.close'

2019-06-03T16:11:20+00:00

bug in 5.4 alpha rc1: to-be-closed x vararg functions

2019-06-03T15:13:13+00:00

Closing methods must be run before correcting 'ci->func' when exiting a vararg function, to get correct debug information (e.g., in case of errors).

Improvements in 'testes/cstack.lua'

2019-06-03T14:34:32+00:00

- tests show progress in real time, so that we can see maximum stack levels even if test crashes. - new test for recursion continuing into message handler.

Details

2019-05-28T18:46:49+00:00

- new error message for "attempt to assign to const variable" - note in the manual about compatibility options - comments - small changes in 'read_line' and 'pushstr'

First implementation for 'const' variables

2019-05-17T14:11:44+00:00

A variable can be declared const, which means it cannot be assigned to, with the syntax 'local name = exp'.

Flag for to-be-closed variables changed to ''

2019-05-09T15:10:31+00:00

The flag for to-be-closed variables was changed from '*toclose' to ''. Several people found confusing the old syntax and the new one has a clear terminator, making it more flexible for future changes.

Coroutines do not unwind the stack in case of errors

2019-05-09T14:13:45+00:00

Back to how it was, a coroutine does not unwind its stack in case of errors (and therefore do not close its to-be-closed variables). This allows the stack to be examined after the error. The program can use 'coroutine.kill' to close the variables. The function created by 'coroutine.wrap', however, closes the coroutine's variables in case of errors, as it is impossible to examine the stack any way.

File 'lib2-v2.so' generated from its own source

2019-05-03T13:36:19+00:00

Instead of being a copy of 'lib2.so', 'lib2-v2.so' has its own source file ('lib22.c'), so that the test can distinguish both libraries.