Re: Why AC_C_CHAR_UNSIGNED?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 23 Jun 2008, Ralf Wildenhues wrote:
That assumes you have a correct limits.h on the system, which is an
assumption you can't necessarily make on an old enough system.

Do you have any specific examples here, found outside of a museum?
Current Autoconf more or less tells users to assume C89 for new
programs, and limits.h exists in a free-standing implementation, too.

My own software does not currently depend on limits.h but tests I did separately on many types of systems (including several 12 year old ones) with a program which specifically exercises limits.h (including 'char') did not encounter any problems.

Bob
======================================
Bob Friesenhahn
bfriesen@xxxxxxxxxxxxxxxxxxx, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/



_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux