[Top][All Lists]

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

Re: Enforcing strict c99 compliance

From: Ralf Wildenhues
Subject: Re: Enforcing strict c99 compliance
Date: Sun, 24 May 2009 08:22:50 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

Hello Adam,

* Adam Mercer wrote on Sat, May 23, 2009 at 11:57:35PM CEST:
> In a project I am involved with we are in the process of moving from
> ANSI C89 to C99, the first step in this transition was to use
> AC_PROG_CC_STDC to detect the compiler instead of AC_PROG_CC (we can't
> use AC_PROG_CC_C99 as there are legacy systems running autoconf-2.59
> that we need to support).

That sounds like a bad idea.  If you cannot update the Autoconf 2.59
system, then you should add required fixes to your package.  For
example, you could use m4_ifdef([AC_PROG_CC_C99], [...], [...])
to find out whether this macro is defined, and otherwise define your
own version of it, to the one that does the checks done in current
Autoconf, for example.  And then call that.

We don't really support bugs in 2.59 any more.


reply via email to

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