opensources/lua - lua - Gitea: Git with home nas server

Commit Graph

Author	SHA1	Message	Date
Roberto Ierusalimschy	9e0a8475cd	Added 'simplesect' sections to the manual 'simplesect' encloses the introductory text of sections with subsections, so that each section either is all text or is all subsections. (This commit also corrects a small brace error in the manual and extra spaces/tabs in some other files.)	5 years ago
Roberto Ierusalimschy	46c3587a6f	Clearer distinction between types and tags LUA_T* represents only types; tags (types + Variants) are represented by LUA_V* constants.	5 years ago
Roberto Ierusalimschy	e592f94a64	Details (mostly comments)	5 years ago
Roberto Ierusalimschy	7bd1e53753	Fixed a warning and other minor issues Fixed some minor issues from the feedback for 5.4-beta rc1.	5 years ago
Roberto Ierusalimschy	ca13be9af7	Supressed errors in '__close' generate warnings	5 years ago
Roberto Ierusalimschy	f64a1b175a	Small optimization in 'convergeephemerons' When converging marks on ephemeron tables, change the direction the tables are traversed at each iteration, to try to avoid bad-case scenarios with linked lists of entries in a table.	5 years ago
Roberto Ierusalimschy	9e6807c3c9	Do not collect open upvalues Open upvalues are kept alive together with their corresponding stack. This change makes a simpler and safer fix to the issue in commit `440a5ee78c`, about upvalues in the list of open upvalues being collected while others are being created. (That previous fix may not be correct.)	5 years ago
Roberto Ierusalimschy	dc07719b0d	Tag LUA_TUPVALTBC replaced by a flag It is simpler to signal a to-be-closed upvalue with a boolean flag, instead of using a different tag.	5 years ago
Roberto Ierusalimschy	9cdf6b7082	Some details in 'lmem.c' and 'lgc.c' - Several new comments in 'lmem.c'. - Both 'luaM_growaux_' and 'luaM_shrinkvector_' use 'luaM_saferealloc_' to check for errors. Moreover, the use of 'luaM_saferealloc_' makes 'luaM_shrinkvector_' try again if shrink fails (which can happen now). - In 'checkSizes', save old debt only when needed.	5 years ago
Roberto Ierusalimschy	e888976bc6	Details (typos in comments)	5 years ago
Roberto Ierusalimschy	1d70708a78	Fixed bug [5.4 alpha] for errors in finalizers Fixes the bug related in [1] (Lua can crash after raising an error in a finalizer), following the lead in [2]. [1] http://lua-users.org/lists/lua-l/2019-06/msg00448.html [2] http://lua-users.org/lists/lua-l/2019-06/msg00450.html	5 years ago
Roberto Ierusalimschy	2c68e66570	Details Several small changes from feedback on 5.4 alhpa rc1 (warnings, typos in the manual, and the like)	6 years ago
Roberto Ierusalimschy	38425e0692	Avoid moving the collector while in 'GCSenteratomic' state The 'GCSenteratomic' is just an auxiliary state for transitioning to 'GCSatomic'. All GC traversals should be done either on the 'GCSpropagate' state or the 'GCSatomic' state.	6 years ago
Roberto Ierusalimschy	8fa4f1380b	Finalizers must be callable Non-function __gc metamethods are not ignored; if present, the metamethod will be called even if it is not a function.	6 years ago
Roberto Ierusalimschy	b56d4e570a	Changes in the warning system - The warning functions get an extra parameter that tells whether message is to be continued (instead of using end-of-lines as a signal). - The user data for the warning function is a regular value, instead of a writable slot inside the Lua state.	6 years ago
Roberto Ierusalimschy	2c32bff609	After a "bad collections", avoid switching back back to generational After a major bad collection (one that collects too few objects), next collection will be major again. In that case, avoid switching back to generational mode (as it will have to switch again to incremental to do next major collection).	6 years ago
Roberto Ierusalimschy	c6f7181e91	No more LUA_ERRGCMM errors Errors in finalizers (__gc metamethods) are never propagated. Instead, they generate a warning.	6 years ago
Roberto Ierusalimschy	e8c779736f	Removed internal cache for closures The mechanism of "caching the last closure created for a prototype to try to reuse it the next time a closure for that prototype is created" was removed. There are several reasons: - It is hard to find a natural example where this cache has a measurable impact on performance. - Programmers already perceive closure creation as something slow, so they tend to avoid it inside hot paths. (Any case where the cache could reuse a closure can be rewritten predefining the closure in some variable and using that variable.) - The implementation was somewhat complex, due to a bad interaction with the generational collector. (Typically, new closures are new, while prototypes are old. So, the cache breaks the invariant that old objects should not point to new ones.)	6 years ago
Roberto Ierusalimschy	bd96330d03	First "complete" implementation of to-be-closed variables Still missing: - handling of memory errors when creating upvalue (must run closing method all the same) - interaction with coroutines	6 years ago
Roberto Ierusalimschy	4cd1f4aac0	Towards "to closed" local variables Start of the implementation of "scoped variables" or "to be closed" variables, local variables whose '__close' (or themselves) are called when they go out of scope. This commit implements the syntax, the opcode, and the creation of the corresponding upvalue, but it still does not call the finalizations when the variable goes out of scope (the most important part). Currently, the syntax is 'local scoped name = exp', but that will probably change.	6 years ago
Roberto Ierusalimschy	ccae0f5aad	Comments about OLD0/OLD1 ages Improved the comments in file 'lgc.c' explaining the roles of "ages" OLD0 and OLD1 in the generacional collector.	6 years ago
Roberto Ierusalimschy	2e297d6ab3	Fixed bug in generational collection of userdata During generational collection, a userdatum must become gray and go to a gray list after being traversed (like tables), so that 'correctgraylist' can handle it to its next stage. This commit also added minimum tests for the generational collector, including one that would detect this bug.	6 years ago
Roberto Ierusalimschy	626cf0581b	Generational mode may wait longer after a major collection When Lua is building large long-duration structures, frequent small minor collections just waste time. Trying to avoid this, the collector will do a larger pause after a major collection when it does not collect enough garbage (which is a hint that memory is being used for long-lasting objects).	6 years ago
Roberto Ierusalimschy	6e600695f8	field 'sizearray' in struct 'Table' changed to 'alimit', which can be used as a hint for '#t'	6 years ago
Roberto Ierusalimschy	0c7738240e	FALLTHROUGH comment must be last "statement" (so it does not work when inside a block)	7 years ago
Roberto Ierusalimschy	2952bc5fc9	special compact representation for userdata with no user values (a common case)	7 years ago
Roberto Ierusalimschy	4a7fe61806	in 'clearbykeys', clear keys of just-removed entries too	7 years ago
Roberto Ierusalimschy	9243c414d9	first version of empty entries in tables (so that, in the future, tables can contain regular nil entries)	7 years ago
Roberto Ierusalimschy	477ca2fe8c	some reorganization in 'lobject.h' (just moving stuff around)	7 years ago
Roberto Ierusalimschy	ca6fe7449a	userdata can have multiple user values	7 years ago
Roberto Ierusalimschy	1afd5a152d	more generic way to handle 'gclist'	7 years ago
Roberto Ierusalimschy	daff7c3b4d	small corrections in generational mode (cannot call finalizers in emergency collections + should set everything before calling finalizers)	7 years ago
Roberto Ierusalimschy	e2b15aa21d	janitor work on casts	7 years ago
Roberto Ierusalimschy	cf7eff45f3	keep control of stack top in Lua functions concentrated in 'luaV_execute'	7 years ago
Roberto Ierusalimschy	1d5b885437	when running Lua code, there is no need to keep 'L->top' "correct"; set it only when needed.	7 years ago
Roberto Ierusalimschy	e663a24ab0	more freedom in handling memory-allocation errors (not all allocations automatically raise an error), which allows fixing a bug when resizing a table.	7 years ago
Roberto Ierusalimschy	421e459684	'luaS_resize' can raise memory errors	7 years ago
Roberto Ierusalimschy	ac78b914b6	warnings from Visual Studio /W3	7 years ago
Roberto Ierusalimschy	599f1742c6	detail (typo in comments)	7 years ago
Roberto Ierusalimschy	ad0704e40c	back to 'CallInfo' (no gains with its removal)	7 years ago
Roberto Ierusalimschy	54eb35a8aa	more fields moved out of 'CallInfo'	7 years ago
Roberto Ierusalimschy	de9128d09d	do not mess up the debt when the collector is not running	7 years ago
Roberto Ierusalimschy	1d8920dd7f	some cleaning in GC parameters	7 years ago
Roberto Ierusalimschy	029d269f4d	bug: dead keys with nil values can stay in weak tables	7 years ago
Roberto Ierusalimschy	f96497397a	new type 'StackValue' for stack elements (we may want to put extra info there in the future)	7 years ago
Roberto Ierusalimschy	73ec04fcf3	no more 'DEADKEY'. Table traversals do not need to consider dead keys; if the key is dead, it cannot be given to 'next'. Instead, we now use a 'table' tag without the collectable bit, which makes it a unique tag good enough to reserve space.	8 years ago
Roberto Ierusalimschy	b6f87491af	in hash nodes, keys are stored in separate pieces to avoid wasting space with alignments	8 years ago
Roberto Ierusalimschy	4bc33d64de	avoid overflows in computation of step size	8 years ago
Roberto Ierusalimschy	72d82a296c	revamping the incremental collector Some simplifications (not counting bytes, couting only slots visited; no more 'gcfinnum'); more GC parameters; using vararg in 'lua_gc' to set parameters in different GC modes	8 years ago
Roberto Ierusalimschy	2376eb6347	barrier for prototype's cache (with new gray list 'protogray' to keep prototypes to have their caches visited again) + constant 'MAXMISS'	8 years ago

1 2 3 4 5 ...

464 Commits (6f5bd5072dff07679c390eecfeaa9d20cc45a9ef)