-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul Eggert wrote: > "Mark D. Baushke" <[EMAIL PROTECTED]> writes: > > >>but 'long long' is NOT available. > > > That's weird, since it's been part of the C standard for 7 years. Are > the Microsoft Windows C compilers that far behind the times?
PMFJI - I'm the one who originated the request. Partly that, and partly we are currently targeting an old compiler to begin with (it predates C99). > Or > perhaps they just need to set some compiler switch to make 'long long' > available? Or can you just ask them to upgrade to a recent-enough > compiler? I vaguely recall that if they use Visual C++.NET 2002 or > later, it should work. This is a reasonable suggestion, after all the compiler is 8 years old. However it requires converting the project files and possibly updating a lot of the compiler options. Not an unreasonable thing to do, but it just means someone has to find time to do it. >>This means that HAVE_LONG_LONG is not defined and intmax_t >>is indeed __int64, so sizeof(INT) is greater than sizeof (long int). > > > The patch is not reasonable by itself, since it will cause a 32-bit > strtol to be used to implement what is supposed to be a 64-bit > strtoimax. Hence you will get obscure errors at runtime if you use > that patch to defeat the compile-time checking. Hmmm, yes, I had a closer look at the function and I see what you mean. OK, let me have another kick at this and see if I can come up with a better solution. - -- Jim Hyslop Dreampossible: Better software. Simply. http://www.dreampossible.ca Consulting * Mentoring * Training in C/C++ * OOD * SW Development & Practices * Version Management -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEkh+TLdDyDwyJw+MRApegAJ4nUeochRTQknblUEfM0l+fB4hJvwCdHqpB BT695ubzNHO5ujBm2wXalvM= =nmAq -----END PGP SIGNATURE-----
