Lines Matching refs:to

4 `sqlite3-wasm.c`. This collection of files is used to build a
17    to be loaded as JS Workers.
30   of the WASM environment, to facilitate plugging it in to arbitrary
33   A semi-third-party collection of JS/WASM utility code intended to
35   these APIs instead of their Emscripten counterparts, in order to be
36   more portable to arbitrary WASM toolchains. This API is
39   to support this tree but is standalone and maintained together
43   and C structs, such that changes to the struct state from either JS
44   or C are visible to the other end of the connection. This is also an
48   Invokes functionality exposed by the previous two files to
50   these pieces related to the `sqlite3.capi.wasm` object.
56   Provides a high-level object-oriented wrapper to the lower-level C
57   API, colloquially known as OO API #1. Its API is similar to other
59   to anyone familiar with such APIs. That said, it is not a "required
62   A Worker-thread-based API which uses OO API #1 to provide an
63   interface to a database which can be driven from the main Window
68       Is not part of the amalgamated sources and is intended to be
75       a far user-friendlier way to interface with databases running
79   Origin-Private FileSystem (OPFS) as a storage layer to provide
83       directly to the (async) OPFS API and channels those results back
84       to its synchronous counterpart. This file, because it must be
88   they add callback functions to be called during its
90   to communicate their state to the files which follow them. This file
107 to private/static `sqlite3.c` internals. `sqlite3.wasm` is compiled
116   purposes and holds no code relevant to the production deliverables.
119   file is intended as a place to override certain Emscripten behavior