QuickJS, the Next Generation: a mighty JavaScript engine
5a7e578482
- output more informative error messages in `js_parse_expect`.
The previous code was bogus:
```
return js_parse_error(s, "expecting '%c'", tok);
```
this was causing a bug on `eval("do;")` where `tok` is `TOK_WHILE` (-70, 0xBA)
creating an invalid UTF-8 encoding (lone trailing byte).
This would ultimately have caused a failure in `JS_ThrowError2` if `JS_NewString`
failed when converting the error message to a string if the conversion detected the invalid
UTF-8 encoding and throwed an error (it currently does not, but should).
- test for `JS_NewString` failure in `JS_ThrowError2`
- test for `JS_FreeCString` failure in run-test262.c
- add more test cases
|
||
|---|---|---|
| .github/workflows | ||
| doc | ||
| examples | ||
| gen | ||
| test262@c1281dba45 | ||
| tests | ||
| .gitignore | ||
| .gitmodules | ||
| CMakeLists.txt | ||
| cutils.c | ||
| cutils.h | ||
| dirent_compat.h | ||
| getopt_compat.h | ||
| libbf.c | ||
| libbf.h | ||
| libregexp-opcode.h | ||
| libregexp.c | ||
| libregexp.h | ||
| libunicode-table.h | ||
| libunicode.c | ||
| libunicode.h | ||
| LICENSE | ||
| list.h | ||
| Makefile | ||
| qjs.c | ||
| qjsc.c | ||
| quickjs-atom.h | ||
| quickjs-c-atomics.h | ||
| quickjs-libc.c | ||
| quickjs-libc.h | ||
| quickjs-opcode.h | ||
| quickjs.c | ||
| quickjs.h | ||
| README.md | ||
| repl.js | ||
| run-test262.c | ||
| test262-fast.conf | ||
| test262.conf | ||
| test262_errors.txt | ||
| unicode_download.sh | ||
| unicode_gen.c | ||
| unicode_gen_def.h | ||
| v8-tweak.js | ||
| v8.js | ||
| v8.sh | ||
| v8.txt | ||
⚡️ QuickJS - A mighty JavaScript engine
Friendly QuickJS fork focused on reigniting the project.
Overview
In October 2023 @bnoordhuis and @saghul decided to fork the QuickJS project with the aim of reigniting it. They reached out to the original authors (@bellard and @chqrlie) about their intentions.
As of December 2023 the initial goal was somewhat accomplished. @bellard resumed working on the project and both parties have been pulling patches from each other since.
As of early 2024 both projects agree the proper path forward involves merging both projects and combining the efforts. While that may take a while, since both projects diverged in certain areas, there is willingness to go in this direction from both sides.