duktape

Commit Graph

Author	SHA1	Message	Date
Sami Vaarala	1e483a52af	Update copyright year range to cover 2016	9 years ago
Sami Vaarala	fc9b704063	Fix genconfig DUK_F_UCLIBC handling DUK_F_UCLIBC checks for __UCLIBC__ which comes from #include files rather than being built into the compiler, so it must be placed after platform includes instead of being automatically inserted to top of file.	9 years ago
Sami Vaarala	aabad65ce0	Add 1.4.0 API calls to API testcase	9 years ago
Sami Vaarala	3f3de555fc	Bump DUK_VERSION for 1.4.0 release	9 years ago
Sami Vaarala	8c9bb71ff8	Merge pull request #519 from svaarala/fix-noline-singlefile-define Fix src-noline DUK_SINGLE_FILE define	9 years ago
Sami Vaarala	1088aee80c	Fix src-noline DUK_SINGLE_FILE define	9 years ago
Sami Vaarala	5c863edb9d	Merge pull request #514 from svaarala/fix-cl-w4-cast-warnings Fix some MSVC /W4 cast warnings	9 years ago
Sami Vaarala	94c9a96006	Releases: trivial reorganization	9 years ago
Sami Vaarala	f7fae15545	API testcase for lightfunc ToObject() coercion	9 years ago
Sami Vaarala	3fc88286dd	Fix type cast warnings	9 years ago
Sami Vaarala	2aba292559	Fix lightfunc ToObject() nargs handling If the lightfunc had varargs, the coerced normal function object would also get a vararg argument count, but the 'nargs' variable went through fragile casts in the process.	9 years ago
Sami Vaarala	9eb8c17c57	Merge pull request #512 from svaarala/add-140-relnotes Add release notes for 1.4.0 release	9 years ago
Sami Vaarala	11fdd53bf5	Known issues update	9 years ago
Sami Vaarala	3749def895	Add release notes for 1.4 release	9 years ago
Sami Vaarala	21b114dbe1	Merge pull request #510 from lzubiaur/patch-1 Missing parameter in the API doc example	9 years ago
lzubiaur	5946db38b6	Add myself in AUTHORS.rst	9 years ago
Laurent Zubiaur	da74df28a0	Fix missing parameter in the example Fix missing `err_code` parameter to `duk_push_error_object_va` in the example. Use `DUK_ERR_TYPE_ERROR` like in the `duk_push_error_object()` example.	9 years ago
Sami Vaarala	792cfa37a1	Merge pull request #509 from svaarala/remove-call-handling-volatile Remove unnecessary volatile attributes in call handling	9 years ago
Sami Vaarala	e1ca7d53be	Releases: remove idx_func volatile	9 years ago
Sami Vaarala	47f2081a67	Remove unnecessary volatile attributes These have been unnecessary even before, but they caused seemingly bogus warnings with some compilers. Now that the setjmp() functions are much smaller, these are hopefully no longer an issue.	9 years ago
Sami Vaarala	2e11acc220	Merge pull request #499 from svaarala/cpp-exception-support Support C++ exceptions instead of setjmp/longjmp to allow automatic destructors etc	9 years ago
Sami Vaarala	a67bdac558	Releases: C++ exception support	9 years ago
Sami Vaarala	860af39844	Website changes for C++ exception support	9 years ago
Sami Vaarala	12181634a3	Add a C++ exception example	9 years ago
Sami Vaarala	08e8763ee8	Add support for C++ exception long ctrl transfers * Define duk_internal_exception, a plain exception class, wihch is used as the value thrown for Duktape internal long control transfers. The value intentionally does not inherit from std::exception so that it'd be as unlikely as possible that user code would catch the internal exception type; only a "catch (...)" would catch it. * Replace DUK_SETJMP() if clauses with "try", and SETJMP() error handling blocks with "catch (duk_internal_exception &exc)" blocks. * Also add clauses for "catch (std::exception &exc)" and "catch (...)" to catch C++ exceptions thrown by user code which are propagated to Duktape try-catch blocks. Such exceptions are converted to API errors. For now it's not supported for user code to propagate a C++ exception "through" Duktape, as that would require some semantics changes to (native) protected calls. Catching and converting such exceptions to API errors makes the user code error apparent and easier to fix.	9 years ago
Sami Vaarala	bb57c7ea13	Add commented out feature opt for c++ exceptions	9 years ago
Sami Vaarala	9f97e8160a	Add DUK_USE_CPP_EXCEPTIONS option, <exception> * Add DUK_USE_CPP_EXCEPTIONS (DUK_OPT_CPP_EXCEPTIONS) which causes Duktape to use C++ try/catch instead of longjmp/setjmp for internal long control transfers. When try/catch is used scope-based resource management (SBRM, a special case of RAII) works as expected, e.g. C++ automatic destructors in Duktape/C functions will be executed. * Add <exception> header to shared headers when compiling in C++ mode. The header is needed to provide std::exception. * Add a sanity check: if DUK_USE_CPP_EXCEPTIONS is enabled and not compiling with a C++ compiler, fail the compile with an explicit #error.	9 years ago
Sami Vaarala	c295c0e759	Merge pull request #498 from svaarala/native-call-outer-setjmp Use an outer setjmp wrapper for duk_handle_call() and duk_handle_safe_call()	9 years ago
Sami Vaarala	3a5275eab2	Releases: native call outer setjmp	9 years ago
Sami Vaarala	0e982cd2e0	Executor document updates for call handling	9 years ago
Sami Vaarala	09676a682a	Use outer setjmp wrapper for call handling Separate call handling into three functions: unprotected call wrapper, protected call wrapper, and a shared inner call handler. Having setjmp only in a smaller wrapper reduces problems with compiler, including: * Spurious volatile warnings * Performance impact on compilers where optimizations must be disabled for any function involving a setjmp Also make every DUK_SETJMP() call site compatible with a later refactoring to supporting C++ exceptions by handling the success case in the then-block and the error in the else-block. This allows a try-catch structure to trivially replace the setjmp construct. Split call error handling to separate function which makes it easier to share for C++ exception handling which may need a catch (xxx) for Duktape errors and a separate catch (...) for other errors accidentally thrown by user code. Other minor cleanups in call handling.	9 years ago
Sami Vaarala	6e13b6ab4c	Merge pull request #507 from ReneHollander/fix-website-broken-ref Fixed a broken website anchor that should redirect to duk_free_raw	9 years ago
ReneHollander	083e548542	Added myself to AUTHORS.rst	9 years ago
ReneHollander	21b4ec9357	Fixed a broken website anchor that should redirect to duk_free_raw	9 years ago
Sami Vaarala	562c7fcdeb	Merge pull request #506 from svaarala/clearer-utf8-decode-message Use clearer error message for source decode error	9 years ago
Sami Vaarala	06a6a980a3	Releases: source decode error	9 years ago
Sami Vaarala	c0f5c1da06	Clearer error for source decode error (GH-504)	9 years ago
Sami Vaarala	74f0d2578f	Merge pull request #501 from svaarala/fix-push-buffer-semicolon Fix push buffer semicolon	9 years ago
Sami Vaarala	ecf467bd18	Releases: duk_push_buffer() macro semicolon	9 years ago
Sami Vaarala	60ee485660	Fix bogus semicolon in duk_push_buffer() macro	9 years ago
Sami Vaarala	16eb18433e	Bug testcase for duk_push_buffer() semicolon	9 years ago
Sami Vaarala	3b9b48b948	Merge pull request #497 from svaarala/fix-idx-func-volatility Add volatile to 'idx_func' to fix NetSurf issue	9 years ago
Sami Vaarala	54fd98b4ef	Releases: idx_func volatility	9 years ago
Sami Vaarala	bf3ebaa6c8	Add volatile to 'idx_func' to fix NetSurf issue Technically the volatile shouldn't be needed: idx_func is written before setjmp() and only read afterwards so its value should be well defined.	9 years ago
Sami Vaarala	1e66f8bc60	Merge pull request #495 from svaarala/fix-string-replace-assert-gh492 Fix assert failure / segfault in String.prototype.replace()	9 years ago
Sami Vaarala	c1a95a6557	Add 0th capture to RegExp.prototype bytecode The bytecode was missing DUK_REOP_SAVE for indices 0 and 1, i.e. the zeroth capture, which caused the RegExp.prototype to match an empty input but without providing the zeroth capture which is assumed in other parts of Duktape internals. This caused the GH-492 assert failure and, with asserts disabled, a segfault.	9 years ago
Sami Vaarala	6d2a164ddc	Testcase for string replace() bug (GH-492)	9 years ago
Sami Vaarala	ed58fe9c4e	Merge pull request #494 from svaarala/debugger-throw-notify-default Don't "require" debugger support for debugger opts	9 years ago
Sami Vaarala	94476dbeb5	Don't "require" debugger support for debugger opts DUK_USE_DEBUGGER_THROW_NOTIFY default is "true". If the option "requires" DUK_USE_DEBUGGER_SUPPORT (which defaults to "false") the option configuraiton would be inconsistent and rejected by default. Remove the "required" metadata for debugger options: the options don't really require debugger support. Instead, if debugger support is disabled, the debugger config options are just ignored without causing a build error.	9 years ago
Sami Vaarala	3f249cdbd4	Merge pull request #486 from svaarala/duk-config-improvements Genconfig modular duk_config.h generation	9 years ago

... 2 3 4 5 6 ...

6103 Commits (b02f994003fce4c35d5b36d17660916161b810ce) All Branches Search

6103 Commits (b02f994003fce4c35d5b36d17660916161b810ce)

All Branches