GertyP

Thanks for the zstd example @CrendKing . I've checked and fixed that issue now.

Can anyone see (or failing that, help investigate) whether my changes have caused the failing 'msys2 / gccx86ninja' automation check, which seems to suggest that the unit test 'AllPlatformTests.test_long_output' is...

I was expecting someone to have a look over the changes and offer some suggested changes or other points for discussion but I'm starting to wonder if that's now unlikely...

I noticed that my recent update to this has triggered a new set of checks. One of which is "Azure Pipelines / mesonbuild.meson (vs2019 vc2019x64vs)", which appears to have been...

This is quite easy to reproduce and test. 1. Go to [tiddlywiki](https://tiddlywiki.com), navigate to the 'getting started' section, and download (gives a 'emtpy.html' file). 2. Open that file in firefox...

OK. That is going a bit further than fixing the issue and keeping the same behaviour; this initial change just keeps the exact same behaviour but fixes the TBB_USE_EXCEPTIONS==0 problem....

... Yes, the tests are understandably expecting terminate, not abort, when using the `terminate_on_exception` control 😄 . So, for consistency, all exception-related fatal error reporting (whether though use of `terminate_on_exception`...

Thanks for having a look at this @pavelkumbrasev As mentioned above, the first commit ('Fix build failure when using TBB_USE_EXCEPTIONS=0') is the lowest impact change that strictly fixes the issue...

> there was a decision that we don't support such build configuration because it would increase test scope This is a documented feature macro [here](https://spec.oneapi.io/versions/latest/elements/oneTBB/source/configuration/feature_macros.html#). I can sympathise that it...

I'd be interested to know if there's any update on this. At least a follow-up decision (with some rationale, depending on the decision) would be more satisfactory than an open,...