When "undumping" a long string, the function 'LoadVector' can call the
reader function, which can run the garbage collector, which can collect
the string being read. So, the string must be anchored during the call
to 'LoadVector'. (This commit also fixes the identation in 'l_alloc'.)

This directory is used for some tests. As standard Lua has no command
to create directories, it must be present before running the tests.

According to ISO C, 'realloc' can fail when shrinking a block. If that
happens, 'l_alloc' simply ignores the fail and returns the original
block.

While building a new prototype, the GC needs barriers for every object
(strings and nested prototypes) that is attached to the new prototype.

The file 'bugs' reports bugs in several different versions
(corresponding to different branches in the repository), without
a clear division of "this bugs belongs to this version". So, it
doesn't make sense to track it along with one (or many) versions.

The result of 'string.format("%a", 0.0)' can have multiple zeros
after the dot.

Bug-fix: joining an upvalue with itself could cause a use-after-free
crash.

A long bracket with too many equal signs can overflow the 'int' used for
the counting and some arithmetic done on the value. Changing the counter
to 'size_t' avoids that. (Because what is counted goes to a buffer, an
overflow in the counter will first raise a buffer-overflow error.)

This is the first commit for the branch Lua 5.3. All source files
were copied from the official distribution of 5.3.5 in the Lua site.
The test files are the same of 5.3.4. The manual came from the
previous RCS repository, revision 1.167.1.2.

to avoid incompatibilites with previous releases

definition of LUA_INITVARVERSION, too.

node for its hash part + new macro 'allocsizenode'

it can do some mess (and break C assertions) before detecting the error.

comments + some instructions can call functions in unespected ways
(e.g., finalizers)

as a finalizer

test "inuse <= LUAI_MAXSTACK" for stack overflow is not correct,
as the real maximum usable size is "LUAI_MAXSTACK - EXTRA_STACK")

an __index; so, 'pairsmeta' should not check for tables. ('pairs'
already checks for tables through 'next'.)

(confuses the debug lib and gains very little in performance)

it coud do some mess (and break C assertions) before detecting the error.
Now it tests for those errors before anything else.

go through registers)

go through registers)