Hello Noah,
> As Ralf said, `AC_C_RESTRICT' supports your compiler precisely as
intended:
> it
> defines away the `restrict' keyword, which your compiler implements
> incorrectly
No, I'm not so sure about that. Indeed, I'm convinced the compiler
implements the keyword exactly as intended. Furthermore, it has the
__declspec(restrict) and __declspec(noalias) function attributes. The
feature is not new, related with e.g. old and now obsolete -Oa and -Ow
compiler switches. The problem is more that the autoconf test require
modification of a custom type, which is not allowed - but as Ralf pointed
out, is allowed in C99. This limitation have little to do with the restrict
keyword.
My point is: Why not lighten up the strict C99 requirement for better
portability? The change is very simple:
autoconf.m4f(11786)
[[typedef int * int_ptr;
int foo (int_ptr $ac_kw ip) {
change to:
[[typedef int * $ac_kw int_ptr;
int foo (int_ptr ip) {
regards Jerker
