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

Commit Graph

Author	SHA1	Message	Date
Roberto Ierusalimschy	314c6057b7	Avoid any code before locks in the API For consistency in the C API, avoid any initializations before callling lua_lock.	4 years ago
Roberto Ierusalimschy	d39ea8b3ce	Make sure that main thread is non yieldable Main thread must be non yieldable even at "level 0" (bare API), outside the 'pcall' from 'lua.c'.	4 years ago
Roberto Ierusalimschy	a304199836	Detail in 'lua_resetthread' 'lua_resetthread' should reset the CallInfo list before calling 'luaF_close'. luaF_close can call functions, and those functions should not run with dead functions still in the CallInfo list.	4 years ago
Roberto Ierusalimschy	d49b288728	'luaE_shrinkCI' shouldn't remove first free CallInfo Due to emergency collections, 'luaE_shrinkCI' can be called while Lua is building a new CallInfo, which for a while is still a free CallInfo.	4 years ago
Roberto Ierusalimschy	17dbaa8639	Improvements in the handling of signals Added 'volatile' to 'l_signalT' variables plus some minor changes.	5 years ago
Roberto Ierusalimschy	7288528a1e	Short strings always use all bytes in the hash Collisions in short strings occurr just by their existence, when internalizing them. (Collisions in long strings is caused/controlled by the program, when adding them as keys to the same table.)	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	6e1aec7a67	Larger C-stack limits for new threads New threads were being created with very small C-stack limits. This is not a problem for coroutines, because 'lua_resume' sets a new limit, but not all threads are coroutines.	5 years ago
Roberto Ierusalimschy	03cde80b58	'setCstacklimit' renamed to 'setcstacklimit' Function names in the API use only lowercase letters.	5 years ago
Roberto Ierusalimschy	ca13be9af7	Supressed errors in '__close' generate warnings	5 years ago
Roberto Ierusalimschy	8b7cfee26b	Small changes around C-stack limit - Better documentation in 'testes/cstack.lua' about using 'debug.setCstacklimit' to find a good limit. - Constant LUAI_MAXCSTACK gets added CSTACKERR (extra stack for error handling), so that it is compatible with the argument to 'debug.setCstacklimit'.	5 years ago
Roberto Ierusalimschy	be73f72fcc	New function 'setCstacklimit' Added new functions to dynamically set the C-stack limit ('lua_setCstacklimit' in the C-API, 'debug.setCstacklimit' in Lua).	5 years ago
Roberto Ierusalimschy	3cd9b56ae6	Revamp around 'L->nCcalls' count The field 'L->nCcalls' now counts downwards, so that the C-stack limits do not depend on the stack size.	5 years ago
Roberto Ierusalimschy	969b8c1f14	Fixed bug with to-be-closed variables in base C level To-be-closed variables in C use 'ci.nresults' to code that there is a variable to be closed in that function. The intialization of the base C level (the one "running" when calling API functions outside any Lua call) did not initialize 'ci.nresults', creating (correct) warnings in valgrind.	6 years ago
Roberto Ierusalimschy	0443ad9e28	LUAI_MAXCCALLS renamed LUAI_MAXCSTACK The limit LUAI_MAXCCALLS was renamed LUAI_MAXCSTACK, which better represents its meaning. Moreover, its definition was moved to 'luaconf.h', given its importance now that Lua does not use a "stackless" implementation.	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	437a5b07d4	Added a warning system to Lua The warning system is just a way for Lua to emit warnings, messages to the programmer that do not interfere with the running program.	6 years ago
Roberto Ierusalimschy	ba7da13ec5	Changes in the control of C-stack overflow * unification of the 'nny' and 'nCcalls' counters; * external C functions ('lua_CFunction') count more "slots" in the C stack (to allow for their possible use of buffers) * added a new test script specific for C-stack overflows. (Most of those tests were already present, but concentrating them in a single script easies the task of checking whether 'LUAI_MAXCCALLS' is adequate in a system.)	6 years ago
Roberto Ierusalimschy	fdc25a1ebf	New functions 'lua_resetthread' and 'coroutine.kill' New functions to reset/kill a thread/coroutine, mainly (only?) to close any pending to-be-closed variable. ('lua_resetthread' also allows a thread to be reused...)	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	f99509581e	Removed extra information from RCS keyword strings Version numbers and dates (mostly wrong) from RCS keyword strings removed from all source files; only the file name are kept.	6 years ago
Roberto Ierusalimschy	af70905246	no need to check whether libraries and host use the same kernel; Lua should work correctly with several copies of the kernel	6 years ago
Roberto Ierusalimschy	b95e466218	new field 'nilvalue' in struct 'global_State' to avoid the use of addresses of static variables	6 years ago
Roberto Ierusalimschy	505fc91222	no more 'luaO_nilobject' to avoid comparison of global variable addresses (now uses static variables)	7 years ago
Roberto Ierusalimschy	97e394ba18	macro 'luai_makeseed' now controls the whole process of making the seed	7 years ago
Roberto Ierusalimschy	022abc301b	'gcemergency' should be zero before any memory allocation	7 years ago
Roberto Ierusalimschy	e2b15aa21d	janitor work on casts	7 years ago
Roberto Ierusalimschy	4dc0be950a	new macro 'isLuacode' (to distinguish regular Lua code from hooks, where C code can run inside a Lua function).	7 years ago
Roberto Ierusalimschy	196c87c9ce	no more 'stackless' implementation; 'luaV_execute' calls itself recursively to execute function calls. 'unroll' continues all executions suspended by an yield (through a long jump)	7 years ago
Roberto Ierusalimschy	5440b42f43	using 'trap' to stop 'luaV_execute' when necessary (tracing and to update its copy of 'base' when the stack is reallocated)	7 years ago
Roberto Ierusalimschy	ad0704e40c	back to 'CallInfo' (no gains with its removal)	7 years ago
Roberto Ierusalimschy	93fd67b793	no more 'CallInfo' structure	7 years ago
Roberto Ierusalimschy	54eb35a8aa	more fields moved out of 'CallInfo'	7 years ago
Roberto Ierusalimschy	c5482468fd	baby steps to remove 'CallInfo': keeping 'L->func' correct	7 years ago
Roberto Ierusalimschy	1d8920dd7f	some cleaning in GC parameters	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	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
Roberto Ierusalimschy	69371c4b84	'KGC_NORMAL' -> 'KGC_INC' + emergency GC signalled by flag (instead of mode)	8 years ago
Roberto Ierusalimschy	f74b87c3c2	removed initialization of 'GCestimate' (it is initialized during a GC cycle, when it start counting)	8 years ago
Roberto Ierusalimschy	0c8a7e071b	'mainthread' lives in 'allgc' list, like everybody else	8 years ago
Roberto Ierusalimschy	e4287da3a6	generational collector (still not complete)	8 years ago
Roberto Ierusalimschy	f5f3df3bd1	generational collection: new attempt (still incomplete)	8 years ago
Roberto Ierusalimschy	89e3a84344	removed field 'n' from 'CallInfo' (not being used right now)	9 years ago
Roberto Ierusalimschy	33b366ec32	added counters for total and individual CallInfo entries (to allow better syncronization between CallInfo size and stack size)	9 years ago
Roberto Ierusalimschy	75d5a8924c	macro 'addbuff' was using external variable name, instead of using its parameter name inside the macro.	9 years ago
Roberto Ierusalimschy	41964648ee	long strings are created directly in final position when possible (instead of using an auxiliar buffer to first create the string and then allocate the final string and copy result there)	9 years ago

1 2 3 4 5 ...

313 Commits (1ecfbfa1a1debd2258decdf7c1954ac6f9761699)