Re: [sqlite] Allow overriding unsigned 64-bit integer

2017-01-08 Thread Kirill Müller
On 08.01.2017 12:54, Clemens Ladisch wrote: Kirill Müller wrote: ... there's no portable support for 64-bit integers. That's what SQLite looks at SQLITE_INT64_TYPE. The patch introduces SQLITE_UINT64_TYPE. I'm working around this issue by using a struct of size 8 A struct of size 8 does

Re: [sqlite] Allow overriding unsigned 64-bit integer

2017-01-08 Thread Kirill Müller
On 08.01.2017 21:24, Richard Hipp wrote: On 1/7/17, Kirill Müller wrote: I'm in a situation [1] where I compile RSQLite as part of a C++ project that still uses the C++98 standard. Can you instead compile SQLite as a library (libsqlite3.a) using gcc or clang, then link

Re: [sqlite] Allow overriding unsigned 64-bit integer

2017-01-08 Thread Kirill Müller
On 08.01.2017 17:38, Clemens Ladisch wrote: Kirill Müller wrote: ... there's no portable support for 64-bit integers. I'm working around this issue by using a struct of size 8 I'm open to alternatives. What's wrong with SQLITE_INT64_TYPE? (Even older C++ compilers should have the C .) Thanks.

Re: [sqlite] Allow overriding unsigned 64-bit integer

2017-01-08 Thread Richard Hipp
On 1/7/17, Kirill Müller wrote: > > I'm in a situation [1] where I compile RSQLite as part of a C++ project > that still uses the C++98 standard. Can you instead compile SQLite as a library (libsqlite3.a) using gcc or clang, then link the compiled *.a file into your

Re: [sqlite] Allow overriding unsigned 64-bit integer

2017-01-08 Thread Scott Hess
On Sun, Jan 8, 2017 at 6:23 AM, Kirill Müller wrote: > On 08.01.2017 14:20, Clemens Ladisch wrote: >> Kirill Müller wrote: >>> On 08.01.2017 12:54, Clemens Ladisch wrote: Kirill Müller wrote: > ... there's no portable support for 64-bit integers. > I'm working

Re: [sqlite] Allow overriding unsigned 64-bit integer

2017-01-08 Thread Clemens Ladisch
Kirill Müller wrote: > ... there's no portable support for 64-bit integers. > I'm working around this issue by using a struct of size 8 > > I'm open to alternatives. What's wrong with SQLITE_INT64_TYPE? (Even older C++ compilers should have the C .) Regards, Clemens

Re: [sqlite] Allow overriding unsigned 64-bit integer

2017-01-08 Thread Kirill Müller
On 08.01.2017 14:20, Clemens Ladisch wrote: Kirill Müller wrote: On 08.01.2017 12:54, Clemens Ladisch wrote: Kirill Müller wrote: ... there's no portable support for 64-bit integers. I'm working around this issue by using a struct of size 8 A struct of size 8 does not behave the same as an

Re: [sqlite] Allow overriding unsigned 64-bit integer

2017-01-08 Thread Clemens Ladisch
Kirill Müller wrote: > On 08.01.2017 12:54, Clemens Ladisch wrote: >> Kirill Müller wrote: >>> ... there's no portable support for 64-bit integers. >>> I'm working around this issue by using a struct of size 8 >> >> A struct of size 8 does not behave the same as an integer type. >> > For compiling

Re: [sqlite] Allow overriding unsigned 64-bit integer

2017-01-08 Thread Kirill Müller
On 08.01.2017 12:54, Clemens Ladisch wrote: Kirill Müller wrote: ... there's no portable support for 64-bit integers. That's what SQLite looks at SQLITE_INT64_TYPE. The patch introduces SQLITE_UINT64_TYPE. I'm working around this issue by using a struct of size 8 A struct of size 8 does

Re: [sqlite] Allow overriding unsigned 64-bit integer

2017-01-08 Thread Clemens Ladisch
Kirill Müller wrote: > ... there's no portable support for 64-bit integers. That's what SQLite looks at SQLITE_INT64_TYPE. > I'm working around this issue by using a struct of size 8 A struct of size 8 does not behave the same as an integer type. > Currently I'm applying the attached patch

[sqlite] Allow overriding unsigned 64-bit integer

2017-01-07 Thread Kirill Müller
Hi all I'm in a situation [1] where I compile RSQLite as part of a C++ project that still uses the C++98 standard. This means there's no portable support for 64-bit integers. I'm working around this issue by using a struct of size 8, but this means I need to override the "unsigned 64-bit