You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
at the beginning of ClosureSite#toNative and that seems to resolve the issue.
I haven't found a way to intercept this via the public API so this will have to get fixed in JNR itself. Would be good to get confirmation from one of the JNR maintainers that passing null for callback parameters is indeed not working correctly yet.
Hello,
I am getting the following error when calling sqlite3_create_function_v2:
https://www.sqlite.org/2016/sqlite-autoconf-3120000.tar.gz
https://github.com/gwenn/sqlite-jna/blob/jnr/src/main/java/org/sqlite/SQLite.java#L769
https://github.com/gwenn/sqlite-jna/blob/jnr/src/main/java/org/sqlite/SQLite.java#L379
If I manually change the signature and force callback(s) to be null, it works:
or
It seems that JNR is passing a non-null function pointer to C even when the Java callback/delegate is null.
Regards.
The text was updated successfully, but these errors were encountered: