SQLITE – Destructor Definitions?

[scurtyParticipant]

Alright so SQLITE3 has these #Defines SQLITE_STATIC/SQLITE_TRANSIENT used in “Binding” values like Text and BLOBS(Basically a Buffer) for calling a “Destructor.” From what I can tell they’re just Callbacks. But binding Text to a SQL Statement is like:

Monkey

sqlite3_bind_text( sqlite3_stmt*, int, const char*, int, void(*)(void*) ); // That void(*)(void*) is for either SQLITE_STATIC/TRANSIENT // Setting it to NULL causes a NULL FUNCTION ERROR

1 2 3

sqlite3_bind_text( sqlite3_stmt*, int, const char*, int, void(*)(void*) ); // That void(*)(void*) is for either SQLITE_STATIC/TRANSIENT // Setting it to NULL causes a NULL FUNCTION ERROR

I’ve tried wrapping the defines to monkey myself but no luck yet. Any thoughts?
Traced them to SQLITE3.h at line 5,036.

Monkey

typedef void (*sqlite3_destructor_type)(void*); #define SQLITE_STATIC ((sqlite3_destructor_type)0) #define SQLITE_TRANSIENT ((sqlite3_destructor_type)-1)

1 2 3

typedef void (*sqlite3_destructor_type)(void*); #define SQLITE_STATIC      ((sqlite3_destructor_type)0) #define SQLITE_TRANSIENT   ((sqlite3_destructor_type)-1)

Is it possible to call these in Monkey? Or do we have to write another function in C?
Cheers.

[Mark SiblyKeymaster]

Currently, you’ll need to write a c handler for these as mx2 functions are not compatible with c++’s so they’ll need to be ‘converted’.

[scurtyParticipant]

Ahh, makes sense. Just checking. Thanks for the reply! Hope things are well. 1.1.08 is looking flyyy.

[Author]

Posts