lua/testes/nextvar.lua, branch v5.4.9 A mirror of https://github.com/lua/lua https://git.lua4.win/lua/atom?h=v5.4.9 2022-12-28T21:34:11+00:00 Avoid excessive name pollution in test files 2022-12-28T21:34:11+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2022-12-28T21:34:11+00:00 urn:sha1:314745ed8438d1276c6c928d5f9d4be018dfadb6 Test files are more polite regarding the use of globals when locals would do, and when globals are necessary deleting them after use. New test for table rehash 2022-09-16T20:05:22+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2022-09-16T20:05:22+00:00 urn:sha1:f8c4c4fcf2b2fed00b3c5b71c19cd64e539dee51 Avoid overflows when incrementing parameters in C 2021-09-22T16:10:39+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2021-09-22T16:10:39+00:00 urn:sha1:deac067ed39a44c001599c0d15de09872496b2aa Any C function can receive maxinteger as an integer argument, and therefore cannot increment it without some care (e.g., doing unsigned arithmetic as the core does). Allow yields inside '__pairs' 2021-03-29T15:57:32+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2021-03-29T15:57:32+00:00 urn:sha1:bf10593a3a912cd3cac69569c7474e687c0d0cd8 Fixed bug of keys removed from tables vs 'next' 2020-10-14T18:46:58+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2020-10-14T18:46:58+00:00 urn:sha1:52c86797608f1bf927be5bab1e9b97b7d35bdf2c Fixed the bug that a key removed from a table might not be found again by 'next'. (This is needed to allow keys to be removed during a traversal.) This bug was introduced in commit 73ec04fc. Better tests for gray lists 2020-08-07T17:45:20+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2020-08-07T17:45:20+00:00 urn:sha1:f13dc59416afa8fc93bb3d784d1a73e49e1b5b09 Test uses an extra bit in 'marked' to mark all elements in gray lists and then check against elements colored gray. Details 2020-02-27T15:59:22+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2020-02-27T15:59:22+00:00 urn:sha1:6eb53b752617fae9e1329bfe2cfecdcbb593c398 Several details in code (e.g., moving a variable to the most inner scope that encloses its uses), comments, parameter names, extra tests. Small corrections when setting 'L->top' 2019-07-25T16:55:29+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2019-07-25T16:55:29+00:00 urn:sha1:9a37dc0ce64c51fd57f5e658a5af8f3671a26b0a - OP_NEWTABLE can use 'ra + 1' to set top (instead of ci->top); - OP_CLOSE doesn't need to set top ('Protect' already does that); - OP_TFORCALL must use 'ProtectNT', to preserve the top already set. (That was a small bug, because iterators could be called with extra parameters besides the state and the control variable.) - Comments and an extra test for the bug in previous item. Unification of size representation in OP_NEWTABLE and OP_SETLIST 2019-07-15T17:59:35+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2019-07-15T17:59:35+00:00 urn:sha1:758c1ef445ab27d89bace746111add04083a8e20 Opcodes OP_NEWTABLE and OP_SETLIST use the same representation to store the size of the array part of a table. This new representation can go up to 2^33 (8 + 25 bits). OP_NEWTABLE keeps exact size of arrays 2019-07-12T19:13:50+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2019-07-12T19:13:50+00:00 urn:sha1:1fb4d539254b67e7e35ed698250c66d1edff0e08 OP_NEWTABLE is followed by an OP_EXTRAARG, so that it can keep the exact size of the array part of the table to be created. (Functions 'luaO_int2fb'/'luaO_fb2int' were removed.)