On 5/22/06, Brannon King <[EMAIL PROTECTED]> wrote:
Is the number of size conversion warnings during sqlite compile disconcerting to anyone but myself? I've attached a log of them below. I
vdbemem.c vdbemem.c(194) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data
This is pretty much a bogus warning since in windows size_t is an integer: #ifndef _SIZE_T_DEFINED typedef unsigned int size_t; #define _SIZE_T_DEFINED #endif The possible loss of data is the sign. Since sizes are almost always non negative in practice there won't be a problem. It's poor practice to not declare things correctly, but it won't make any practical difference. etc. Given that DRH maintains an extensive regression test suite with sqlite I'm not concerned. This is much more rigrourous than most any other product I've worked with.
