From a347927d60c70686c995bd453bd3ca7b1e3f24c8 Mon Sep 17 00:00:00 2001 From: stephan Date: Sun, 1 Jan 2023 12:22:16 +0000 Subject: An alternative solution to mapping SQLITE_WASM_DEALLOC to the proper function pointer in JS, to account for a Safari-specific quirk reported in [forum:e5b20e1feb|forum post e5b20e1feb]. FossilOrigin-Name: 688c5c13d156f987b895df1d5a5b770616b0d9caec4726e03ba122eb8539e7b2 --- ext/wasm/api/sqlite3-wasm.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'ext/wasm/api/sqlite3-wasm.c') diff --git a/ext/wasm/api/sqlite3-wasm.c b/ext/wasm/api/sqlite3-wasm.c index b39e252b1..981fad92b 100644 --- a/ext/wasm/api/sqlite3-wasm.c +++ b/ext/wasm/api/sqlite3-wasm.c @@ -463,7 +463,9 @@ const char * sqlite3_wasm_enum_json(void){ DefGroup(blobFinalizers) { /* SQLITE_STATIC/TRANSIENT need to be handled explicitly as ** integers to avoid casting-related warnings. */ - out("\"SQLITE_STATIC\":0, \"SQLITE_TRANSIENT\":-1"); + out("\"SQLITE_STATIC\":0, \"SQLITE_TRANSIENT\":-1,"); + outf("\"SQLITE_WASM_DEALLOC\": %lld", + (sqlite3_int64)(sqlite3_free)); } _DefGroup; DefGroup(changeset){ -- cgit v1.2.3