Dominik Seichter wrote: > Hmm, does this help? Making it explicitly a long? > > #define PODOFO_MAX_OBJ_NUMBER 9999999999L > > AFAIK Craig is working on x86_64, too, as I am. So our 64bit longs should be > definitely large enough, maybe we have to check MAX_INT or MAX_LONG on other > platforms.
That should never exceed max long, but does exceed max int. It should've been explicitly `long', because it's used with `long' data types. gcc 4.1 handles it silently, but newer versions appear to be stricter (good!). My bad. It should be fixed in SVN now. -- Craig Ringer ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Podofo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/podofo-users
