Re: ac_cv_sizeof_X, et al.

2008-07-15 Thread Philip Prindeville
Bob Friesenhahn wrote: On Mon, 14 Jul 2008, Philip Prindeville wrote: And is there a autoconf-lint to check for using broken names, like ac_cv_sizeof_long_long_unsigned_int instead of whatever is preferred? I prefer ac_cv_sizeof_long_long_unsigned_int because it is my nature to be pedantic

Re: ac_cv_sizeof_X, et al.

2008-07-15 Thread Ralf Wildenhues
* Philip Prindeville wrote on Tue, Jul 15, 2008 at 01:27:17AM CEST: I'm looking at sox-12.17.9 and seeing in their configure file (which claims to be generated via Autoconf 2.59) from their configure.in file and seeing: ac_cv_sizeof_x=$ac_cv_sizeof_char:$ac_cv_sizeof_short Well, for

Re: ac_cv_sizeof_X, et al.

2008-07-15 Thread Philip Prindeville
Eric Blake wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Philip Prindeville on 7/14/2008 5:27 PM: | I'm looking at sox-12.17.9 and seeing in their configure file (which | claims to be generated via Autoconf 2.59) Newer autoconf versions are able to accurately determine

Re: ac_cv_sizeof_X, et al.

2008-07-15 Thread Tim Post
On Mon, 2008-07-14 at 19:25 -0500, Bob Friesenhahn wrote: I prefer ac_cv_sizeof_long_long_unsigned_int because it is my nature to be pedantic and it sounds bigger. Is that bad? Refreshingly honest, actually. If stdint.h and inttypes.h were available everywhere then much of this gobbly

Re: ac_cv_sizeof_X, et al.

2008-07-15 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Philip Prindeville on 7/15/2008 12:22 AM: | | Well, it kind of begs the question: if ac_sizeof_long_long_int != | ac_sizeof_long_long_unsigned_int, then what happens when you assign a | LONGLONG_MAX to a signed long long, and then copy

Re: ac_cv_sizeof_X, et al.

2008-07-15 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Philip Prindeville on 7/15/2008 1:06 AM: | | How hard would it be to parse out the type, and generate a warning for | anything other than the canonical name for a given intrinsic type? Because it is not a trivial patch, and no one has

Re: ac_cv_sizeof_X, et al.

2008-07-15 Thread Andreas Schwab
Eric Blake [EMAIL PROTECTED] writes: C allows for difference in size between unsigned and signed counterparts C99 doesn't. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B

Re: ac_cv_sizeof_X, et al.

2008-07-15 Thread Paul Eggert
Eric Blake [EMAIL PROTECTED] writes: At one point, I proposed modifying autoconf to require both types, or else claim that neither type exists, because there was an actual platform (Tandem/NSK) reported by Matthew Woehlke that actually had 32-bit unsigned long long and 64-bit long long. Paul

ac_cv_sizeof_X, et al.

2008-07-14 Thread Philip Prindeville
[ As per Ralf's suggestion, starting a new thread on a tangential issue... ] I'm looking at sox-12.17.9 and seeing in their configure file (which claims to be generated via Autoconf 2.59) from their configure.in file and seeing: ac_cv_sizeof_x=$ac_cv_sizeof_char:$ac_cv_sizeof_short

Re: ac_cv_sizeof_X, et al.

2008-07-14 Thread Bob Friesenhahn
On Mon, 14 Jul 2008, Philip Prindeville wrote: And is there a autoconf-lint to check for using broken names, like ac_cv_sizeof_long_long_unsigned_int instead of whatever is preferred? I prefer ac_cv_sizeof_long_long_unsigned_int because it is my nature to be pedantic and it sounds bigger.

Re: ac_cv_sizeof_X, et al.

2008-07-14 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Philip Prindeville on 7/14/2008 5:27 PM: | I'm looking at sox-12.17.9 and seeing in their configure file (which | claims to be generated via Autoconf 2.59) Newer autoconf versions are able to accurately determine type sizes when