On Fri, Nov 29, 2013 at 9:47 PM, RSmith <rsm...@rsweb.co.za> wrote: > > The fact that the app compiles is no great precursor to its success in the > wild. The thing you are avoiding is not a dependancy - 64 bit types should > be easy in any platform and I know Windows (anything after XP anyway) uses > only 64-bit internals, much like any other OS since the dawn of the 21st > century. The fact that you can still compile 32 bit programs and run it is > pure backward compatibility on any system that still allow it, so if your > compiler does not support it natively, you need to upgrade. > > But, that is not the case... your compiler supports it just fine - it > isn't a dependancy, it's a native part of the compiler, it must be. Even > in older 32-bit compiling systems there's always a 64 bit LongLong or Int64 > or whatever flavour it went by. The reason you might not be getting the > same 32-vs-64 bit warning might be that your compiler is sneakily using 64 > bit integers in the background anyway, while the other doesn't or at least, > doesn't warn you about it. (This is a hypothesis, I'm not using MSVC so > cannot say for sure). > > Either way, you NEED to cast that return value to a proper data-type hat > can hold all of 64 bits in it... else you will get errors, especially when > some user of your program runs into the first >32bit number in his/her > database and it turns negative, or overwrite previous keys, etc. etc. > > You cannot ignore it, but it should be really easy to fix. Any MSVC buff > here knows the exact Type for a 64b-int in MSVC? >
I don't _do_ Windows, but a fast search gave me: http://msdn.microsoft.com/en-us/library/windows/desktop/aa383710%28v=vs.85%29.aspx http://msdn.microsoft.com/en-us/library/windows/desktop/aa384264%28v=vs.85%29.aspx __int64, DWORD64 (unsigned), INT64 (signed), LONG64 (signed), UINT64 (unsigned), ULONG64 (unsigned), but the MSVC documentation seems to only list "signed long int" and "unsigned long int". As best as I can find. Personally, I would use the sqlite3 supplied name and let Dr. Hipp's code resolve it to the proper declaration based on the compiler being used. -- This is clearly another case of too many mad scientists, and not enough hunchbacks. Maranatha! <>< John McKown _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
