On Mon, 2008-06-02 at 20:10 -0500, William A. Rowe, Jr. wrote: > apr_dbd_mysql.c(142) : warning C4244: 'function' : conversion from '__int64 > ' to 'unsigned long ', possible loss of data > apr_dbd_mysql.c(256) : warning C4018: '>=' : signed/unsigned mismatch > apr_dbd_mysql.c(416) : warning C4244: '=' : conversion from 'double ' to > 'float ', possible loss of data > apr_dbd_mysql.c(486) : warning C4244: '=' : conversion from 'double ' to > 'float ', possible loss of data > apr_dbd_mysql.c(536) : warning C4244: '=' : conversion from 'unsigned > __int64 ' to 'int ', possible loss of data > apr_dbd_mysql.c(642) : warning C4244: '=' : conversion from 'unsigned > __int64 ' to 'int ', possible loss of data
Get it - will fix. It's just a cast thingy... > apr_dbd_mysql.c(868) : error C2632: 'long' followed by 'long' is illegal > apr_dbd_mysql.c(872) : error C2632: 'long' followed by 'long' is illegal > apr_dbd_mysql.c(873) : error C2632: 'long' followed by 'long' is illegal > apr_dbd_mysql.c(873) : warning C4244: '=' : conversion from '__int64 ' to > 'long ', possible loss of data > apr_dbd_mysql.c(879) : error C2632: 'long' followed by 'long' is illegal > apr_dbd_mysql.c(883) : error C2632: 'long' followed by 'long' is illegal > apr_dbd_mysql.c(884) : error C2632: 'long' followed by 'long' is illegal > apr_dbd_mysql.c(884) : warning C4244: '=' : conversion from 'unsigned > __int64 ' to 'unsigned long ', possible loss of data Sorry, just blindly following the manual: http://dev.mysql.com/doc/refman/5.0/en/c-api-prepared-statement-datatypes.html > Bottom line, "long long" is just not portable. What's up with that? I guess we'll need to find a way to work around that. My best bet is that we can abuse my_ulonglong for that purpose. -- Bojan
