[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[MIT-Scheme-devel] sqlite3
From: |
Matt Birkholz |
Subject: |
[MIT-Scheme-devel] sqlite3 |
Date: |
Sat, 18 May 2013 14:31:12 -0700 |
> From: Taylor R Campbell <address@hidden>
> Date: Thu, 16 May 2013 20:58:54 +0000
>
> This morning I threw together a binding to sqlite3. [...] it needs
> to integrate with the thread system using sqlite3_interrupt and
> sqlite3_progress_handler
That is somewhat the opposite of the GIO interface, whose _async
functions return immediately. A callback signals when the requested
operation is finished. Thus the main thread is free to do its thing.
The callback is short, just collects results. There is no need to run
the whole system, thread-switching, inside another mainloop's
_progress_handler... ick.
- [MIT-Scheme-devel] sqlite3, Taylor R Campbell, 2013/05/16
- Re: [MIT-Scheme-devel] sqlite3, Taylor R Campbell, 2013/05/16
- [MIT-Scheme-devel] sqlite3,
Matt Birkholz <=
- Re: [MIT-Scheme-devel] sqlite3, Taylor R Campbell, 2013/05/18
- Re: [MIT-Scheme-devel] sqlite3, Matt Birkholz, 2013/05/19
- Re: [MIT-Scheme-devel] sqlite3, Taylor R Campbell, 2013/05/19
- Re: [MIT-Scheme-devel] sqlite3, Matt Birkholz, 2013/05/19
- Re: [MIT-Scheme-devel] sqlite3, Taylor R Campbell, 2013/05/19
- Re: [MIT-Scheme-devel] sqlite3, Matt Birkholz, 2013/05/27
- [MIT-Scheme-devel] floating-point environment in threads, Taylor R Campbell, 2013/05/28