* Fix #693: Add Emscripten/embind bindings for get_state/set_state The Emscripten wrapper exported only the eval family, leaving JS consumers with no way to snapshot or restore the singleton ChaiScript engine. The playground in chaiscript.github.io needs that to reset between runs without reloading the WASM module. Added handle-based wrappers that hide ChaiScript::State behind an int registry so JS callers don't have to manage embind object lifetimes, exported them as saveState/restoreState/releaseState, and added a native regression test that exercises capture, restore, and release through the same wrapper functions the WASM binding uses. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * Address review: snapshot top-level locals alongside engine state ChaiScript::State captures globals, functions, and types but not the top-level scripting locals created by `var x = ...`. The previous restoreState therefore left such variables behind, breaking the playground reset use case and tripping the new test's assertion in Debug builds (where assert is enabled). Pair get_state with get_locals in the snapshot so a restore brings back a clean baseline. Requested by @lefticus in PR #699 review. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * 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> --------- Co-authored-by: leftibot <leftibot@users.noreply.github.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .github | ||
| cmake | ||
| contrib | ||
| emscripten | ||
| grammar | ||
| include/chaiscript | ||
| performance_tests | ||
| samples | ||
| src | ||
| static_libs | ||
| unittests | ||
| .buckconfig | ||
| .clang-format | ||
| .decent_ci-Linux.yaml | ||
| .decent_ci-MacOS.yaml | ||
| .decent_ci-Windows.yaml | ||
| .decent_ci.yaml | ||
| .gitignore | ||
| .travis.yml | ||
| biicode.conf | ||
| BUCK | ||
| buckaroo.json | ||
| cheatsheet.md | ||
| CMakeLists.txt | ||
| description.txt | ||
| DesignGoals.md | ||
| Doxyfile.in | ||
| LICENSE | ||
| license.txt | ||
| readme.md | ||
| releasenotes.md | ||
| supporters.md | ||
ChaiScript
(c) 2009-2012 Jonathan Turner (c) 2009-2017 Jason Turner
Release under the BSD license, see "license.txt" for details.
Introduction
ChaiScript is one of the only embedded scripting language designed from the ground up to directly target C++ and take advantage of modern C++ development techniques, working with the developer how they would expect it to work. Being a native C++ application, it has some advantages over existing embedded scripting languages:
- It uses a header-only approach, which makes it easy to integrate with existing projects.
- It maintains type safety between your C++ application and the user scripts.
- It supports a variety of C++ techniques including callbacks, overloaded functions, class methods, and stl containers.
Requirements
ChaiScript requires a C++17 compiler to build with support for variadic templates. It has been tested with gcc 7 and clang 6 (with libcxx).
Installation using vcpkg
You can download and install ChaiScript using the vcpkg dependency manager:
git clone https://github.com/Microsoft/vcpkg.git
cd vcpkg
./bootstrap-vcpkg.sh
./vcpkg integrate install
vcpkg install chaiscript
The ChaiScript port in vcpkg is kept up to date by Microsoft team members and community contributors. If the version is out of date, please create an issue or pull request on the vcpkg repository.
Usage
- Add the ChaiScript include directory to your project's header search path
- Add
#include <chaiscript/chaiscript.hpp>to your source file - Instantiate the ChaiScript engine in your application. For example, create a
new engine with the name
chailike so:chaiscript::ChaiScript chai - The default behavior is to load the ChaiScript standard library from a loadable module. A second option is to compile the library into your code, see below for an example.
Once instantiated, the engine is ready to start running ChaiScript source. You
have two main options for processing ChaiScript source: a line at a time using
chai.eval(string) and a file at a time using chai.eval_file(fname)
To make functions in your C++ code visible to scripts, they must be registered with the scripting engine. To do so, call add:
chai.add(chaiscript::fun(&my_function), "my_function_name");
Once registered the function will be visible to scripts as "my_function_name"
Examples
ChaiScript is similar to ECMAScript (aka JavaScript(tm)), but with some modifications to make it easier to use. For usage examples see the "samples" directory, and for more in-depth look at the language, the unit tests in the "unittests" directory cover the most ground.
For examples of how to register parts of your C++ application, see "example.cpp" in the "samples" directory. Example.cpp is verbose and shows every possible way of working with the library. For further documentation generate the doxygen documentation in the build folder or see the website http://www.chaiscript.com.
Grammar
A formal EBNF grammar for ChaiScript is available in grammar/chaiscript.ebnf. To view it as a railroad diagram, paste the grammar into mingodad's railroad diagram generator or bottlecaps.de/rr.
The shortest complete example possible follows:
/// main.cpp
#include <chaiscript/chaiscript.hpp>
double function(int i, double j)
{
return i * j;
}
int main()
{
chaiscript::ChaiScript chai;
chai.add(chaiscript::fun(&function), "function");
double d = chai.eval<double>("function(3, 4.75);");
}

