[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AC_PROG_CC_C99 macro description is too vague / ambiguous
From: |
Eric Blake |
Subject: |
Re: AC_PROG_CC_C99 macro description is too vague / ambiguous |
Date: |
Tue, 21 Apr 2009 23:12:50 -0600 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.21) Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.6.666 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Ralf Wildenhues on 4/21/2009 3:04 PM:
>> It is not clear whether GNU extensions are allowed or not. Even though
>> one may think that it is natural to keep the GNU extensions, gcc has
>> -std=c99 for strict ISO C99 (as opposed to gnu99 for the GNU dialect),
>> so that one can easily mix up "C99 mode" above and "c99 language" from
>> gcc. The macro description should avoid this possible confusion.
>
> OK?
>
> Thanks,
> Ralf
>
> Improve description of AC_PROG_CC_C89 and AC_PROG_CC_C99.
>
> * doc/autoconf.texi (C Compiler): Document that AC_PROG_CC_C89
> and AC_PROG_CC_C99 prefer extended over strict conformance modes.
> Report by Vincent Lefevre.
Okay, except spell Vincent's surname correctly (Lefèvre) in ChangeLog and
your commit message, since both of those support UTF-8.
- --
Don't work too hard, make some time for fun as well!
Eric Blake address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknup1IACgkQ84KuGfSFAYCTpwCgqjyPD2j2/Xz9FwUwFNg50Ch6
NYQAoNBjKnaXBRJ+edES/DsXQuXWO7Hn
=OMVF
-----END PGP SIGNATURE-----