Fixes for 2.6.0 release

[svaarala]

• Allow unlabelled function statement in strict mode Accept unlabelled function statements outside of top level for strict functions #2213
• Remove big endian assumption for PPC64 to support ppc64le Remove endianness assumption for PPC64 #2267
• Debugger duk_opcodes.yaml fix (TRYCATCH), add CALL flags Add JS-based bytecode dumper, duk_opcodes.yaml metadata fixes #2277
• Fix out-of-memory handling for nested errors Restore creating_error after mark-and-sweep #2290
• duk_suspend() main thread state fix Deactivate thread while suspended #2282
• Update UglifyJS version from 2.4.12 to 3.9.2 (it only affects runtests), fix test breakage due to 2.4.12 artifact paths changing Update UglifyJS dependency #2299
• CBOR.encode() assertion failure for zero-size dynamic plain buffer Fix CBOR.encode() assertion failure #2318
• Add recursion limits and native stack check to CBOR encode/decode Add CBOR recursion limits and native stack check #2340
• Fix String.prototype.startsWith/endsWith() pointer overflow Fix memcmp() pointer overflow in string builtin #2320
• Fix object hash part handling in enumeration sorting Fix hash part handling in enum sorting #2322
• Fix unstable pointer in putvar Fix unstable valstack pointer in putprop #2323
• Fix unsafe JSON.stringify() behavior if replacer is an array, and Array.prototype has index properties Fix JSON.stringify() inherited array index bug #2324
• Fix RegExp exec() result inherited index handling Fix RegExp exec() result inherited index handling #2325
• Fix Proxy 'ownKeys' postprocess handling when Array.prototype has index properties Fix Proxy ownKeys() postprocess array index bug #2326
• Fix dangling pointer in coroutine yield() Fix dangling pointer in coroutine yield() #2332
• Fix JSON.parse() assertion failure and potentially unlimited recursion for JSON.parse() Add recursion check to JSON.parse() reviver walk #2341
• duk_logging.c s(n)printf() warning fix Fix trivial duk_logging.c compile warning #2349
• Fix String.prototype.replace() pointer handling when search string longer than input string Fix pointer handling in String replace() #2358
• Better missing PyYAML warning Better missing PyYAML warning for configure.py #2361
• NaN normalization fix Fix NaN normalization bug for packed tval #2362
• Remove 64kb limit of 'duk' interactive input (when no linenoise enabled) Remove 64kb interactive line limit of 'duk' #2368

[warmwaffles]

@svaarala is this still relevant since 3.x changes are on the horizon?

[svaarala]

2.x will get maintenance for bugs and security issues probably for a long while, because the update to 3.x will not be seamless.

[warmwaffles]

@svaarala cool, was just picking through the repository trying to figure out what changed so I can prepare for it.

[svaarala]

Main changes so far (some merged, some planned):

• Rewrite of object representation and property algorithms to be faster, more ES2015+ compliant, and enable implementing data structures like Map etc
• Rewrite of Python tooling into Node.js, more dog-fooding of JS, and the tooling will also run with Duktape to improve portability of tooling
• Switch from CESU-8 string representation to WTF-8, this is not visible to ECMAScript code but C code will then see proper UTF-8 strings rather than CESU-8 surrogate pairs for non-BMP codepoints, this simplifies corner case handling in C code (although it's a bit awkward for Duktape internals which must present the surrogate pairs to script code)

With the window open to break stuff, priority is on changes that have compatibility impact but are necessary going forward.

API changes will be minimal so the changes in application code won't be difficult in this sense. But one must be aware of changes under the hood, for example the string representation change affects native code a bit.