autoconf-patches
[Top][All Lists]
Advanced

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

Re: Why AC_C_CHAR_UNSIGNED?


From: Bob Friesenhahn
Subject: Re: Why AC_C_CHAR_UNSIGNED?
Date: Thu, 26 Jun 2008 04:52:43 -0500 (CDT)

On Thu, 26 Jun 2008, Stepan Kasal wrote:

Or would it help to put it all to one message?

AC_C_CHAR_UNSIGNED: The macro is obsolete.  Instead of checking
__CHAR_UNSIGNED__, include limits.h and test for CHAR_MIN == 0.

If your autotools maintainer cannot do that, you shall return him for
replacement of defective parts.   ;-)

I would be truely aghast if I found that the several people who independently maintain autotools for my own package were doing this kind of surgury on it.

Some of the worlds most valuable packages are not longer actively developed yet they are individually maintained by people who care to be sufficient (or acceptable according to some standard) for use in Cygwin, many Linux distributions, *BSD, etc. These sort of "deprecation" scenarios can lead to silent undetected failure due to an over-vigilant maintainer who is not prepared to adequately test the software.

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





reply via email to

[Prev in Thread] Current Thread [Next in Thread]