Hmmm... would you mind to assume a C99 compatible compiler ? Then there is int64_t, which IMHO is better than long long int, if your concern is the storage size.
JD. Le mercredi 12 mars 2014 20:58:31 UTC+1, Jeffrey Kegler a écrit : > > From Activestate's site, I get this report of a Microsoft compile > failure<http://ppm4.activestate.com/MSWin32-x86/5.12/1200/J/JK/JKEGL/Marpa-R2-2.082000.d/log-20140311T220808.txt>because > I require "long long int". My questions, for those more attuned to > the world of Microsoft than I, are > > 1.) Should I care? That is, does it look like the setup is broken, or > does it seem so oddball that I should ignore it? > > 2.) If I should care, what's a good workaround?. "long long int" is used > to ensure that the int is at least 64-bits. There are other ways to do > that, none 100% portable. I'd assume there is some way that this compiler > likes to be asked for a 64-bit int. > > Thanks, jeffrey > -- You received this message because you are subscribed to the Google Groups "marpa parser" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
