On Thu, Aug 11, 2016 at 4:34 AM, Paulo Roberto <betobran...@gmail.com> wrote:
> Thank you very much, it worked! Just remember that exposing a SQL function that de-references a "user"-supplied integer value as a pointer is inherently unsafe. Anyone can select remember(val, 0) or select remember(val, 101) and crash (at best) your app, or worse silently corrupt it in some way. A safer (but slower) approach would be to add a level of indirection, and not use the int as a "pointer" directly, but as a *key* in a map (a global) used to lookup the memory address of the counter, so you *can* error out (instead of crash/corrupt) on a bad input/key. My $0.02. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
