I hit a similar problem with ODBC on 64 bit systems. One caution though: we can't completely lose control of the size when fixing this. One might need to read something written by a 32 bit system on a 64 bit one. Just as with int and DWORD, there needs to be a way to ask for the proper size for the platform or for a specific width. I once saw a system (then thinking 16/32 bit) where they had the platform and fixed types backwards, but that's another story ~:(
Bill Saludos, Fernando Il giorno Sep 16, 2009, alle ore 8:37 PM, Ken Treis ha scritto: > * I'm creating a partial Alien library for GemStone so that I can use > the CairoGraphics package in both Pharo and GLASS. But on x86-64, > there there's a size difference between a pointer/long and an integer. > It'd be nice to have some more explicit APIs on Alien, so I could say > "Alien newCInteger" or "Alien newCLong" and have the platform return > me the proper size Alien. Even without the platform size differences, > it seems awkward to use "Alien newC: 4" everywhere I want an integer, > "Alien newC: 8" where I want a double, etc. > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
