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

Commit Graph

Author	SHA1	Message	Date
Roberto Ierusalimschy	b4d5dff8ec	Multiple errors in '__toclose' report the first one 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.	6 years ago
Roberto Ierusalimschy	cf71a5ddc7	Details Several small improvements (code style, warnings, comments, more tests), in particular: - 'lua_topointer' extended to handle strings - raises an error in 'string.format("%10q")' ('%q' with modifiers) - in the manual for 'string.format', the term "option" replaced by "conversion specifier" (the term used by the C standard)	6 years ago
Roberto Ierusalimschy	4ace93ca65	No more to-be-closed functions To-be-closed variables must contain objects with '__toclose' metamethods (or nil). Functions were removed for several reasons: * Functions interact badly with sandboxes. If a sandbox raises an error to interrupt a script, a to-be-closed function still can hijack control and continue running arbitrary sandboxed code. * Functions interact badly with coroutines. If a coroutine yields and is never resumed again, its to-be-closed functions will never run. To-be-closed objects, on the other hand, will still be closed, provided they have appropriate finalizers. * If you really need a function, it is easy to create a dummy object to run that function in its '__toclose' metamethod. This comit also adds closing of variables in case of panic.	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	6d04537ea6	A to-be-closed variable must have a closable value (or be nil) It is an error for a to-be-closed variable to have a non-closable non-nil value when it is being closed. This situation does not seem to be useful and often hints to an error. (Particularly in the C API, it is easy to change a to-be-closed index by mistake.)	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	41c800b352	Closing methods should not interfere with returning values A closing method cannot be called in its own stack slot, as there may be returning values in the stack after that slot, and the call would corrupt those values. Instead, the closing method must be copied to the top of the stack to be called. Moreover, even when a function returns no value, its return istruction still has to have its position (which will set the stack top) after the local variables, otherwise a closing method might corrupt another not-yet-called closing method.	6 years ago
Roberto Ierusalimschy	3c7dc52909	Handling of memory errors when creating to-be-closed upvalues	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	f96497397a	new type 'StackValue' for stack elements (we may want to put extra info there in the future)	7 years ago
Roberto Ierusalimschy	b42430fd3a	'lineinfo' in prototypes saved as differences instead of absolute values, so that the array can use bytes instead of ints, reducing its size. (A new array 'abslineinfo' is used when line differences do not fit in a byte.)	7 years ago
Roberto Ierusalimschy	be0d951be8	bug: cannot reuse a dying upvalue	8 years ago
Roberto Ierusalimschy	8634b2a011	added 'cachemiss' field to prototype to avoid wasting time checking hits that fail too often	8 years ago
Roberto Ierusalimschy	a3d36fe283	Upvalues collected like everything else (with mark-sweep) instead of reference count (simpler and better for generational mode)	8 years ago
Roberto Ierusalimschy	2331e1beec	small changes in 'luaC_upvalbarrier'	8 years ago
Roberto Ierusalimschy	28fdbcf393	added include for 'lprefix.h', for stuff that must be added before any other header file	10 years ago
Roberto Ierusalimschy	bdf566a8a3	`name' in comments changed to 'name'	10 years ago
Roberto Ierusalimschy	89b56e7d84	more precision between closure types ('LClosure' x 'CClosure')	11 years ago
Roberto Ierusalimschy	14929f5764	use appropriate macros to convert GCObject to specific types	11 years ago
Roberto Ierusalimschy	d764cc5522	new list 'twups' to allow traversal of upvalues from dead threads (+ fixed some problems with cycles involving those upvalues)	11 years ago
Roberto Ierusalimschy	ffa96d988d	field 'op' renamed to 'open'	11 years ago
Roberto Ierusalimschy	733c58595b	no more local collection	11 years ago
Roberto Ierusalimschy	1150873447	'luaC_newobj' does not handle special cases; only special case now is threads, which do not use 'luaC_newobj' anymore.	11 years ago
Roberto Ierusalimschy	90972ff136	LOCALBLACK changed to LOCALMARK and used also to control whether object is in 'localgc' list + luaC_newobj by default puts object in 'localgc' list	11 years ago
Roberto Ierusalimschy	af35c7f398	upvalues collected by reference count	11 years ago
Roberto Ierusalimschy	742b7377d3	Lua closures go to local, too	11 years ago
Roberto Ierusalimschy	50955e27f5	C functions and strings now go to the local list; first version of the local collector	11 years ago
Roberto Ierusalimschy	439d74e29f	added 'local' bit (true => object is only refered by local variables)	11 years ago
Roberto Ierusalimschy	623e388bb4	double-linked list of all upvalues elliminated and changed to a traversal of all non-marked threads	11 years ago
Roberto Ierusalimschy	677d90165f	no more generational collection !!!	11 years ago
Roberto Ierusalimschy	86b39206d9	open upvalues cannot be old if thread is not old; when thread is old, their list is not traversed anymore, and therefore can contain dead elements.	12 years ago
Roberto Ierusalimschy	3cadc37f47	no more 'Proto' objects on the stack. Protos are anchored on outer Protos or on a Closure, which must be created before the Proto.	13 years ago
Roberto Ierusalimschy	fd22ccd6d0	object tag keeps variant bits too -> no need for 'isC' field in Closures + more strick typing for closure variants	13 years ago
Roberto Ierusalimschy	a71c5f6f53	typo in comments	15 years ago
Roberto Ierusalimschy	0d116c3ada	unused '#include' removed	15 years ago
Roberto Ierusalimschy	575074fd85	Lua closures are cached for reuse	15 years ago
Roberto Ierusalimschy	1c1a98e872	corrected some places where an old object could end up in front of a new one + minimal documentation about this problem	15 years ago
Roberto Ierusalimschy	23001d8607	nasty GC bug: upvalue must be turned white when not keeping invariant, but barrier was not being called when uv->v were already white.	15 years ago
Roberto Ierusalimschy	5a7a0c72d8	'luaC_linkupval' embedded into call site	15 years ago
Roberto Ierusalimschy	064e406f67	no more fenvs!	15 years ago
Roberto Ierusalimschy	25c557ec63	first version of _ENV; no more global variables	15 years ago
Roberto Ierusalimschy	0bbdddc86b	allocator function receives the tag of object being allocated in 'osize' when 'ptr' is NULL.	15 years ago
Roberto Ierusalimschy	3a9ae612a4	macro 'ngcotouv' is the same as 'gco2uv', so it was removed	15 years ago
Roberto Ierusalimschy	3c4d970a7b	comment typos	15 years ago
Roberto Ierusalimschy	0ac3d07ea6	first implementation of lexical environments	15 years ago
Roberto Ierusalimschy	5938212748	information about upvalues (where they come from) kept in Proto structure, instead of sequence of pseudo-opcodes after OP_CLOSURE	15 years ago
Roberto Ierusalimschy	c6b442bd36	'luaM_freearray' does not need array type as argument	16 years ago
Roberto Ierusalimschy	593bfc9668	should not manipulate NULL pointers (even without accessing them)	18 years ago
Roberto Ierusalimschy	c505f341d6	small changes in casts	19 years ago

1 2 3

135 Commits (758c1ef445ab27d89bace746111add04083a8e20)