Re: AC_C_RESTRICT

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Jeff Squyres on 3/17/2009 8:27 AM:
> On Mar 16, 2009, at 7:11 PM, Eric Blake wrote:
> 
>> > - Or should there be a new AC_RESTRICT test that makes a solution for
>> > both the C and C++ compilers?
>>
>> That's the goal for autoconf 2.64.
>>
> 
> Hmm -- this seems to be different than what Ralf W. replied...?  Greping
> through a git clone of the autoconf repo, I don't see any mention of
> AC_RESTRICT...?

I guess I replied inaccurately.  The goal is to make AC_C_RESTRICT (the
existing macro) work correctly.

Ralf brought up an interesting point - how often do people mix C and C++
compilers of different origins, and expect things to work?  In other
words, it seems to me that the most common use case is that you either
stick with the vendor compiler in all cases (hence the workaround for the
Sun compiler), or you use gcc in all cases.  But if we're mistaken, and
people really DO want to mix vendor C and g++ (or vendor C++ and gcc),
then we must either entirely avoid restrict in C++, or else we must indeed
make AC_C_RESTRICT perform additional testing inside an
AC_LANG_PUSH([C++])/AC_LANG_POP block, if the configure script does
anything for C++.

- --
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

iEYEARECAAYFAkm/tPsACgkQ84KuGfSFAYBZjgCeOiZeHIVuztyRTPb0gu0j27VS
tIAAnjVlhF/n6GHFse5h/CefXp+WxHeq
=RdTd
-----END PGP SIGNATURE-----