This has been the whole point of my emails -- I am not sufficiently
familiar with the actual code details for me to make that
determination. There are no comments to indicate whether the implicit
cast is 'safe' or not. I know that some casts are a simple fact of
life, especially in UN!X based code, where the runtime or system API
returns character data in an integer, but the conversion of a 64-bit
to an 32-bit value is a different case.
If I could have determined the context to a reasonable degree of
certainty, it would be one thing, but not being able to determine the
actual intent raises some concerns.
-ken
On 29-Oct-05, at 12:56 PM, [EMAIL PROTECTED] wrote:
Ken & Deb Allen <[EMAIL PROTECTED]> wrote:
vdbeapi.c
e:\SQLITE\327\Source\vdbeapi.c(55) : warning C4244: 'return' :
conversion from 'i64' to 'int', possible loss of data
e:\SQLITE\327\Source\vdbeapi.c(195) : warning C4244: '=' : conversion
from 'double' to 'i64', possible loss of data
e:\SQLITE\327\Source\vdbeapi.c(232) : warning C4244: '=' : conversion
from 'double' to 'u64', possible loss of data
What about these three warnings do you think is a concern?
Have you actually looked at the code in question to see
if the possibility of data loss is real and unintentional?
What makes you think that these warnings are not just a case
of the compiler blowing smoke?
--
D. Richard Hipp <[EMAIL PROTECTED]>
