Re: Migrating from UFFI to CFFI

On Oct 21, 2013, at 7:31 AM, Victor <[email protected]> wrote:
> What if the modifications are refactored to rely on the .dll/.so/.lib
> just as a fallback in case when 64 bit FFI ints are not supported? It
> can cause some bit rust (since the native library will not be used in
> the most cases) but at the same time it will prevent newcomers from
> experiencing problems due to lack of required libraries on some
> platforms (like that Windows 7).

I think it would be more difficult to maintain two reader-based compilation
paths depending upon the underlying environment than the current system.
We can keep the patch in the mail list until a time when backward compatibility
to 32-bit systems lacking 64-bit integer support will be formally dropped by
CLSQL.

Your patch will stay in the mail list archive and can be used by someone
who also has trouble with the Windows environment that can't be solved
by compiling the C file and who also has a 64-bit supported environment.

> It looks like I've generated some dirty patches over the past month, I
> would like to polish them so that they can be eventually merged into
> the mainline (especially the Sqlite3 autoincrement).

That would be optimal and I'd like it as well. Unfortunately, my
schedule is such that I won't be able to provide much help. Nathan,
Ryan, and Russ from acceleration.net have been providing most of the
improvements to CLSQL lately so perhaps they will be able to assist
when you think your changes are ready to be deployed in
in the wide range of production platforms where CLSQL is used.

Kevin