[EMAIL PROTECTED] wrote:
"Ian Frosst" <[EMAIL PROTECTED]> wrote:
Looking at the code, there are pointer to int truncations
everywhere,
Where, specifically, are you seeing pointer to int truncations
in the SQLite code base? This is something that needs to be
fixed.
I've compiled 3.3.10
"Ian Frosst" <[EMAIL PROTECTED]> wrote:
> the two suspects I see in the warnings are:
>
> static int winFileHandle(OsFile *id)
> {
>return (int)((winFile*)id)->h;
> }
>
> The HANDLE will be64 bit, then get trunc'd when cast (unless there is some
> compiler magic afoot that I'm not aware of.)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
SQLite works fine on 64 bit platforms. In my case I am using Linux
64bit. The warnings are about pointers being cast to int.
> Looking at the code, there are pointer to int truncations
> everywhere,
Pointers are used as placeholders in callbacks.
--- [EMAIL PROTECTED] wrote:
> "Ian Frosst" <[EMAIL PROTECTED]> wrote:
> > Looking at the code, there are pointer to int truncations
> > everywhere,
>
> Where, specifically, are you seeing pointer to int truncations
> in the SQLite code base?
I haven't seen any. I suspect there aren't any.
As
"Ian Frosst" <[EMAIL PROTECTED]> wrote:
> Looking at the code, there are pointer to int truncations
> everywhere,
Where, specifically, are you seeing pointer to int truncations
in the SQLite code base? This is something that needs to be
fixed.
--
D. Richard Hipp <[EMAIL PROTECTED]>
Has anyone here gotten 3.3.10 (or any subsequent version) to compile and run
successfully through Visual C++ (I'm using 2005, but again, any version
would do.) Looking at the code, there are pointer to int truncations
everywhere, and I've found no magic bullet for declalring int's as 64 bit
6 matches
Mail list logo
