leftibot 19b54e1d53 Address review: make ChaiScript engine an opaque handle, drop singleton ... Replace the static ChaiScript singleton in the Emscripten wrapper with a handle-based registry symmetric to the existing State registry. JS callers now create an engine with chaiscript_create(), pass the resulting handle to the eval/state helpers, and release it with chaiscript_destroy(). Multiple independent engines are now possible, and a state snapshot can be restored onto any engine. Updated the playground HTML and the three native regression tests to exercise the new API. Requested by @lefticus in PR #699 review. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-02 10:50:17 -06:00
..
chaiscript_em.cpp	Address review: make ChaiScript engine an opaque handle, drop singleton	2026-05-02 10:50:17 -06:00
chaiscript_eval.hpp	Address review: make ChaiScript engine an opaque handle, drop singleton	2026-05-02 10:50:17 -06:00
chaiscript.html	Address review: make ChaiScript engine an opaque handle, drop singleton	2026-05-02 10:50:17 -06:00
CMakeLists.txt	Fix #678: Add WASM exception support to Emscripten build (#689)	2026-04-13 22:40:26 -06:00