I added rtree to my sqlite compilation for the first time and got these warnings for OSX 64bit:
/Users/Shared/src/sqlite/sqlite-3.6.4/sqlite3.c: In function ‘rtreeCreate’: /Users/Shared/src/sqlite/sqlite-3.6.4/sqlite3.c:94784: warning: cast from pointer to integer of different size /Users/Shared/src/sqlite/sqlite-3.6.4/sqlite3.c: In function ‘rtreeConnect’: /Users/Shared/src/sqlite/sqlite-3.6.4/sqlite3.c:94797: warning: cast from pointer to integer of different size These are in the rtreeCreate() and rtreeConnect() functions, calling rtreeInit(): return rtreeInit(db, pAux, argc, argv, ppVtab, pzErr, 1, (int)pAux); I thought the two pAux parameters were odd - one bare and one cast to (int), so I looked up rtreeInit(). static int rtreeInit(sqlite3 *db, void *pAux, int argc, const char *const*argv, sqlite3_vtab **ppVtab, char **pzErr, int isCreate, int eCoordType) The first pAux is a pointer, so this one looks correct. But the second is an int (eCoordType), and the only two values I found defined are 0 & 1: #define RTREE_COORD_REAL32 0 #define RTREE_COORD_INT32 1 Forget the cast warnings now - why is pAux used to set the eCoordType? My C skills are pretty basic, so maybe there is some pointer/cast magic happening? Or maybe it's simply screwed up? ----- William Kyngesburye <kyngchaos*at*kyngchaos*dot*com> http://www.kyngchaos.com/ [Trillian] What are you supposed to do WITH a maniacally depressed robot? [Marvin] You think you have problems? What are you supposed to do if you ARE a maniacally depressed robot? No, don't try and answer, I'm 50,000 times more intelligent than you and even I don't know the answer... - HitchHiker's Guide to the Galaxy _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
