duktape

Commit Graph

Author	SHA1	Message	Date
Sami Vaarala	6fc4eaf0ff	Move knownissues/specialoptions to JSON file	10 years ago
Sami Vaarala	8728a51bfe	API testcase for duk_def_prop()	10 years ago
Sami Vaarala	39311f7bc6	API tests for new vararg calls	10 years ago
Sami Vaarala	375e9adc4c	Non-leading tab fixes	10 years ago
Sami Vaarala	f1225ac56a	Test cases: 16-bit overflow test case, minor fixes	10 years ago
Sami Vaarala	5e56112176	Second round of lightfunc support improvements * Fix outstanding FIXME issues for lightfunc semantics. * Improve API and Ecmascript testcases to match. * Clarify lightfunc limitations, e.g. finalizer limitations. * Guide and API documentation changes for lightfuncs. * Fix compile warning: duk_str_not_object unused.	10 years ago
Sami Vaarala	fef0870107	First round of lightfunc changes A lot of changes to add preliminary lightfunc support: * Add LIGHTFUNC tagged type to duk_tval.h and API. * Internal changes for preliminary to support lightfuncs in call handling and other operations (FIXMEs left in obvious places where support is still missing after this commit) * Preliminary Ecmascript and API testcases for lightfuncs Detailed notes: * Because magic is signed, reading it back involves sign extension which is quite verbose to do in C. Use macros for reading the magic value and other bit fields encoded in the flags. * Function.prototype.bind(): the 'length' property of a bound function now comes out wrong. We could simply look up the virtual 'length' property even if h_target is NULL: no extra code and binding is relatively rare in hot paths. Rewrite more cleanly in any case. * The use flag DUK_USE_LIGHTFUNC_BUILTINS controls the forced lightfunc conversion of built-ins. This results in non-compliant built-ins but significant memory savings in very memory poor environments. * Reject eval(), Thread.yield/resume as lightfuncs. These functions have current assertions that they must be called as fully fledged functions. * Lightfuncs are serialized like ordinary functions for JSON, JX, and JC by this diff. * Add 'magic' to activation for lightfuncs. It will be needed for lightweight functions: we don't have the duk_tval related to the lightfunc, so we must copy the magic value to the activation when a call is made. * When lightfuncs are used as property lookup base values, continue property lookup from the Function.prototype object. This is necessary to allow e.g. ``func.call()`` and ``func.apply()`` to be used. * Call handling had to be reworked for lightfuncs, especially how bound function chains are handled. This is a relatively large change but is necessary to support lightweight functions properly in bound function resolution. The current solution is not ideal. The bytecode executor will first try an ecma-to-ecma call setup which resolves the bound function chain first. If the final, unbound function is not viable (a native function) the call setup returns with an error code. The caller will then perform a normal call. Although bound function resolution has already been done, the normal call handling code will re-do it (and detect there is nothing to do). This situation could be avoided by decoupling bound function handling and effective this binding computation from the actual call setup. The caller could then to do this prestep first, and only then decide whether to use an ecma-to-ecma call or an ordinary heavyweight call. Remove duk__find_nonbound_function as unused. * Use indirect magic to allow LIGHTFUNCs for Date. Most of the built-in functions not directly eligible as lightfuncs are the Date built-in methods, whose magic values contain too much information to fit into the 8-bit magic of a LIGHTFUNC value. To work around this, add an array (duk__date_magics[]) containing the actual control flags needed by the built-ins, and make the Date built-in magic value an index into this table. With this change Date built-ins are successfully converted to lightfuncs. Testcase fixes: - Whitespace fixes - Print error for indirect eval error to make diagnosis easier - Fix error string to match errmsg updated in this branch	11 years ago
Sami Vaarala	ffc4ec66f3	Testcase illustrating how to set C func name	10 years ago
Sami Vaarala	458d73a38b	Bug test: Function.prototype.name writability	10 years ago
Sami Vaarala	e20b318727	duk_{get,require,push}_heapptr() API tests	10 years ago
Sami Vaarala	2b73af4249	Testcases for JSON.parse() syntax error offset	10 years ago
Sami Vaarala	ef967aae7c	Update API testcase for new module convention	10 years ago
Sami Vaarala	a0e50c9961	Test for duk_get_error_code() and duk_is_error()	10 years ago
Sami Vaarala	85d4d6ed85	API testcase for C module example	10 years ago
Sami Vaarala	4468ae6e01	API testcase for duk_put_global_string() Also improve duk_get_global_string() testcase with error wrapper.	10 years ago
Sami Vaarala	e7ba3fcc5f	Fix testcases for capitalized internal keys	10 years ago
Sami Vaarala	23c328900a	API testcase fixes for buffer API rename	10 years ago
Sami Vaarala	2099e98f3f	API testcase for dll link test	10 years ago
Sami Vaarala	92d89ce35d	Bug testcase for duk_peval_file() nonexistent file	10 years ago
Sami Vaarala	14a93002ef	Fix non-ascii chars in API testcase Merge two test cases in the process.	10 years ago
Sami Vaarala	0713ecc784	Remove non-ascii chars from source	10 years ago
Sami Vaarala	439a63d004	Fix trailing newline offenders in API tests	10 years ago
Sami Vaarala	394a940578	API test case fix for memory function rename	10 years ago
Sami Vaarala	9759c74f90	API testcase for stack reserve vs. function calls This documents a value stack reserve handling bug in Duktape 0.11.0 and documents the desired behavior.	10 years ago
Sami Vaarala	d0344a6de8	Improvements to duk_set_global_object() testcase	10 years ago
Sami Vaarala	688ead0d0d	API testcase for duk_set_global_object()	10 years ago
Sami Vaarala	7fef6e8e61	API testcase policy fixes and minor improvements	10 years ago
Sami Vaarala	802e9fcb61	Fix a few API testcase whitespace issues	10 years ago
Sami Vaarala	d41230bd47	API testcase: duk_{xmove_xcopy}_top()	10 years ago
Sami Vaarala	f957db3d47	Remove mem zeroing test from memory func API test The memory allocation is not zeroed automatically.	10 years ago
Sami Vaarala	32e209f5d5	Mark two failing API test cases with knownissue This allows `make apitest` to finish with exit code 0, so that non-zero exit codes can be used to indicate an error for commit testing.	10 years ago
Sami Vaarala	92abbb2dcd	API testcase fix for changed error message	10 years ago
Sami Vaarala	19a69ec2ea	Improve C finalizer API test case	10 years ago
Sami Vaarala	7a58378ee7	API testcase for duk_{get,set}_finalizer	10 years ago
Sami Vaarala	3855d77c35	Extend get/set prototype API testcase Now covers undefined/object for set call, naked objects etc. Does not cover invalid arguments to duk_set_prototype().	10 years ago
Sami Vaarala	0722872b39	Improve prototype loop testcase Should now have full coverage over internal prototype walk sites.	10 years ago
Sami Vaarala	91df98b49b	Draft API testcase for duk_{get,set}_prototype	10 years ago
Sami Vaarala	f00ed4ca92	Add an API testcase for prototype loop and GC	10 years ago
Sami Vaarala	54e3c71227	Add a guide related magic test to API testcases	10 years ago
Sami Vaarala	aedfa691a8	Add error cases to magic API testcase	10 years ago
Sami Vaarala	8c9ef37e33	API testcase for duk_{get,set}_magic()	10 years ago
Sami Vaarala	8d20275dda	Remove outdated FIXME from testcase	10 years ago
Sami Vaarala	bf38ee992b	Fix API testcases for new strictness policy	10 years ago
Sami Vaarala	df4faff604	fixme note	11 years ago
Sami Vaarala	9f60f0c0d6	fix api strictness test case	11 years ago
Sami Vaarala	f2a2d42faf	Example of replacing print() from C code	10 years ago
Sami Vaarala	ebc530db7d	API testcase for eval code strictness handling	10 years ago
Sami Vaarala	449fd66788	API testcase for internal properties for user code	10 years ago
Sami Vaarala	f1739884e8	Testcases illustrating access to Date _value	10 years ago
Sami Vaarala	2014019e2b	Add API testcase for duk_copy()	10 years ago

1 2 3 4

199 Commits (8ef7c399382c4771316911fcb03bcf24bd2c525e)